[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120824205812.GJ21325@google.com>
Date: Fri, 24 Aug 2012 13:58:12 -0700
From: Tejun Heo <tj@...nel.org>
To: "Martin K. Petersen" <martin.petersen@...cle.com>
Cc: Kent Overstreet <koverstreet@...gle.com>,
linux-bcache@...r.kernel.org, linux-kernel@...r.kernel.org,
dm-devel@...hat.com, vgoyal@...hat.com, mpatocka@...hat.com,
bharrosh@...asas.com, Jens Axboe <axboe@...nel.dk>,
NeilBrown <neilb@...e.de>,
Lars Ellenberg <lars.ellenberg@...bit.com>,
Peter Osterlund <petero2@...ia.com>,
Sage Weil <sage@...tank.com>
Subject: Re: [PATCH v6 11/13] block: Rework bio_pair_split()
Hello, Martin.
On Thu, Aug 23, 2012 at 10:25:47PM -0400, Martin K. Petersen wrote:
> However, I'm not sure I like the overall approach of the new splitting.
> Instead of all this cloning, slicing and dicing of bio_vecs I'd rather
> we bit the bullet and had an offset + length for the vector inside each
> bio. That way we could keep the bio_vec immutable and make clones more
> lightweight since their vecs would always point to the parent. This also
> makes it trivial to split I/Os in the stacking drivers and removes evils
> in the partial completion code path. It would also allow to sever the
> ties between "size of block range operated on" vs. bi_size which we need
> for copy offload, discard, etc.
Yeah, I'm fairly sure we all want that but that's gonna have to be a
separate not-so-small project. Also, how we split underlying bvec
doesn't affect the split interface update being done here. This
patchset is updating split so that it can handle arbirarily sized
bios, which is useful whether its implementation is using immutable
bvec or COWing it.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists