[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1753989.1676283061@warthog.procyon.org.uk>
Date: Mon, 13 Feb 2023 10:11:01 +0000
From: David Howells <dhowells@...hat.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: dhowells@...hat.com, Jens Axboe <axboe@...nel.dk>,
Al Viro <viro@...iv.linux.org.uk>,
Matthew Wilcox <willy@...radead.org>, Jan Kara <jack@...e.cz>,
Jeff Layton <jlayton@...nel.org>,
David Hildenbrand <david@...hat.com>,
Jason Gunthorpe <jgg@...dia.com>,
Logan Gunthorpe <logang@...tatee.com>,
Hillf Danton <hdanton@...a.com>, linux-fsdevel@...r.kernel.org,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, Christoph Hellwig <hch@....de>,
John Hubbard <jhubbard@...dia.com>
Subject: Re: [PATCH v13 03/12] splice: Do splice read from a buffered file without using ITER_PIPE
Christoph Hellwig <hch@...radead.org> wrote:
> Also why doesn't this use init_sync_kiocb?
I'm not sure I want ki_flags.
> > if (in->f_flags & O_DIRECT)
> > return generic_file_direct_splice_read(in, ppos, pipe, len, flags);
> > + return generic_file_buffered_splice_read(in, ppos, pipe, len, flags);
>
> Btw, can we drop the verbose generic_file_ prefix here?
Probably. Note that at some point cifs, for example, running in "unbuffered"
mode might want to call [generic_file_]direct_splice_read() directly.
David
Powered by blists - more mailing lists