[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAH9NwWf_S-PyY5X_cJGSW-8YDk4-C0VvnPCX8iVuo0FhTqsy2Q@mail.gmail.com>
Date: Fri, 19 Jul 2024 08:41:04 +0200
From: Christian Gmeiner <christian.gmeiner@...il.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Matthew Wilcox <willy@...radead.org>, Mary Strodl <mstrodl@...edom.csh.rit.edu>,
Christoph Hellwig <hch@...radead.org>, Mary Strodl <mstrodl@....rit.edu>, linux-kernel@...r.kernel.org,
urezki@...il.com, linux-mm@...ck.org, lee@...nel.org, andi.shyti@...nel.org,
linux-i2c@...r.kernel.org, s.hauer@...gutronix.de
Subject: Re: [PATCH 1/3] mm: vmalloc: export __vmalloc_node_range
>
> On Thu, 18 Jul 2024 22:35:02 +0100 Matthew Wilcox <willy@...radead.org> wrote:
>
> > On Thu, Jul 18, 2024 at 02:31:03PM -0700, Andrew Morton wrote:
> > > The hardware is weird, but we should try to support it in some fashion.
> >
> > Why? It's been around since 2005, and Linux has done perfectly well
> > without support for it.
>
> Oh. I was assuming it was some new thing. This does weaken the case
> a lot.
This wonderful interface is used in recent products from them too.
Adding support for it
in an upstream-able way could be still a benefit, as these products
are used in different
industrial environments running on Linux.
--
greets
--
Christian Gmeiner, MSc
https://christian-gmeiner.info/privacypolicy
Powered by blists - more mailing lists