[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACVXFVNYL+1ucYom_gpX4BD6ROm_GXG7-DEs+5_gxgmDCxNWfA@mail.gmail.com>
Date: Tue, 1 Nov 2016 06:50:04 +0800
From: Ming Lei <tom.leiming@...il.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: "Theodore Ts'o" <tytso@....edu>, Jens Axboe <axboe@...com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-block <linux-block@...r.kernel.org>,
Linux FS Devel <linux-fsdevel@...r.kernel.org>,
"Kirill A . Shutemov" <kirill.shutemov@...ux.intel.com>,
Mike Christie <mchristi@...hat.com>,
Hannes Reinecke <hare@...e.com>,
Keith Busch <keith.busch@...el.com>,
Mike Snitzer <snitzer@...hat.com>,
Johannes Thumshirn <jthumshirn@...e.de>,
Bart Van Assche <bart.vanassche@...disk.com>
Subject: Re: [PATCH 45/60] block: bio: introduce bio_for_each_segment_all_rd()
and its write pair
On Mon, Oct 31, 2016 at 11:11 PM, Christoph Hellwig <hch@...radead.org> wrote:
> On Mon, Oct 31, 2016 at 09:59:43AM -0400, Theodore Ts'o wrote:
>> What is _rd and _wt supposed to stand for?
>
> I think it's read and write, but I think the naming is highly
> unfortunate. I started dabbling around with the patches a bit,
> and to keep my sanity a started reaming it to _pages and _bvec
> which is the real semantics - the _rd or _pages gives you a synthetic
> bvec for each page, and the other one gives you the full bvec.
Looks _pages & _bvec is better and still a little confusing and not reflect
its real purpose from user view, since both points to real bvec. Could we
just rename _rd as bio_for_each_segment_all_ro() which means the pointed
bvec is readonly and not introduce _wt?
Thanks,
Ming Lei
Powered by blists - more mailing lists