[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20211012204410.GR24307@magnolia>
Date: Tue, 12 Oct 2021 13:44:10 -0700
From: "Darrick J. Wong" <djwong@...nel.org>
To: Felix Kuehling <felix.kuehling@....com>
Cc: Matthew Wilcox <willy@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Alex Sierra <alex.sierra@....com>, linux-mm@...ck.org,
rcampbell@...dia.com, linux-ext4@...r.kernel.org,
linux-xfs@...r.kernel.org, amd-gfx@...ts.freedesktop.org,
dri-devel@...ts.freedesktop.org, hch@....de, jgg@...dia.com,
jglisse@...hat.com, apopple@...dia.com
Subject: Re: [PATCH v1 00/12] MEMORY_DEVICE_COHERENT for CPU-accessible
coherent device memory
On Tue, Oct 12, 2021 at 04:24:25PM -0400, Felix Kuehling wrote:
>
> Am 2021-10-12 um 3:11 p.m. schrieb Matthew Wilcox:
> > On Tue, Oct 12, 2021 at 11:39:57AM -0700, Andrew Morton wrote:
> >> Because I must ask: if this feature is for one single computer which
> >> presumably has a custom kernel, why add it to mainline Linux?
> > I think in particular patch 2 deserves to be merged because it removes
> > a ton of cruft from every call to put_page() (at least if you're using
> > a distro config). It makes me nervous, but I think it's the right
> > thing to do. It may well need more fixups after it has been merged,
> > but that's life.
>
> Maybe we should split the first two patches into a separate series, and
> get it merged first, while the more controversial stuff is still under
> review?
Yes, please. I've seen that first patch several times already. :)
--D
> Thanks,
> Felix
>
>
Powered by blists - more mailing lists