[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161029152933.GA17241@infradead.org>
Date: Sat, 29 Oct 2016 08:29:33 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Ming Lei <tom.leiming@...il.com>
Cc: Jens Axboe <axboe@...com>, linux-kernel@...r.kernel.org,
linux-block@...r.kernel.org, linux-fsdevel@...r.kernel.org,
Christoph Hellwig <hch@...radead.org>,
"Kirill A . Shutemov" <kirill.shutemov@...ux.intel.com>,
Mike Christie <mchristi@...hat.com>,
Hannes Reinecke <hare@...e.de>,
Dan Williams <dan.j.williams@...el.com>,
Toshi Kani <toshi.kani@....com>, shli@...nel.org,
linux-raid@...r.kernel.org
Subject: Re: [PATCH 23/60] block: introduce flag QUEUE_FLAG_NO_MP
On Sat, Oct 29, 2016 at 04:08:22PM +0800, Ming Lei wrote:
> MD(especially raid1 and raid10) is a bit difficult to support
> multipage bvec, so introduce this flag for not enabling multipage
> bvec, then MD can still accept singlepage bvec only, and once
> direct access to bvec table in MD and other fs/drivers are cleanuped,
> the flag can be removed. BTRFS has the similar issue too.
There is really no good reason for that. The RAID1 and 10 code really
just needs some love to use the bio cloning infrastructure, bio
iterators and generally recent bio apis. btrfs just needs a tiny little
bit of help and I'll send patches soon.
Having two different code path is just asking for trouble in the long
run.
Powered by blists - more mailing lists