From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Fri, 1 Jun 2018 01:35:57 -0700 From: Christoph Hellwig To: Jens Axboe Cc: Ming Lei , Kent Overstreet , Christoph Hellwig , Alexander Viro , David Sterba , Huang Ying , linux-kernel@vger.kernel.org, linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, Theodore Ts'o , "Darrick J . Wong" , Coly Li , Filipe Manana Subject: Re: [RESEND PATCH V5 00/33] block: support multipage bvec Message-ID: <20180601083557.GA30694@infradead.org> References: <20180525034621.31147-1-ming.lei@redhat.com> <20180525045306.GB8740@kmo-pixel> <8aa4276d-c0bc-3266-aa53-bf08a2e5ab5c@kernel.dk> <20180527072332.GA18240@ming.t460p> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org List-ID: On Sun, May 27, 2018 at 07:44:52PM -0600, Jens Axboe wrote: > Yes, we discussed exactly this, which is why I'm surprised you went > ahead with the same approach. I told you I don't like tree wide renames, > if they can be avoided. I'd rather suffer some pain wrt page vs segments > naming, and then later do a rename (if it bothers us) once the dust has > settled on the interesting part of the changes. > > I'm very well away of our current naming and what it signifies. With > #1, you are really splitting hairs, imho. Find a decent name for > multiple segment. Chunk? vec? bio_for_each_segment (page) bio_for_each_vec (whole bvec)