[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y8/rx6PQ4z9Tk8qQ@nvidia.com>
Date: Tue, 24 Jan 2023 10:31:35 -0400
From: Jason Gunthorpe <jgg@...dia.com>
To: David Howells <dhowells@...hat.com>
Cc: John Hubbard <jhubbard@...dia.com>,
Al Viro <viro@...iv.linux.org.uk>,
Christoph Hellwig <hch@...radead.org>,
Matthew Wilcox <willy@...radead.org>,
Jens Axboe <axboe@...nel.dk>, Jan Kara <jack@...e.cz>,
Jeff Layton <jlayton@...nel.org>,
Logan Gunthorpe <logang@...tatee.com>,
linux-fsdevel@...r.kernel.org, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, Christoph Hellwig <hch@....de>,
linux-mm@...ck.org
Subject: Re: [PATCH v8 10/10] mm: Renumber FOLL_PIN and FOLL_GET down
On Tue, Jan 24, 2023 at 02:27:53PM +0000, David Howells wrote:
> Jason Gunthorpe <jgg@...dia.com> wrote:
>
> > My point was to change that to take a 'bool unpin' because FOLL_PIN is
> > not to be used outside gup.c
>
> I need a 3-state wrapper. But if I can't do it in gup.c, then I'll have to do
> it elsewhere. As Christoph says, most of the places will only be pinned or
> not-pinned. The whole point was to avoid generating new constants when
> existing constants would do.
What is the 3rd state?
Jason
Powered by blists - more mailing lists