From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-f66.google.com ([209.85.215.66]:35486 "EHLO mail-lf0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751121AbdASI1j (ORCPT ); Thu, 19 Jan 2017 03:27:39 -0500 MIME-Version: 1.0 In-Reply-To: References: From: Ming Lei Date: Thu, 19 Jan 2017 16:27:36 +0800 Message-ID: Subject: Re: [LSF/MM ATTEND] block: multipage bvec upstreaming & next step To: Coly Li Cc: lsf-pc@lists.linux-foundation.org, linux-block , Linux FS Devel Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Hi Coly, On Thu, Jan 19, 2017 at 3:57 PM, Coly Li wrote: > On 2017/1/17 =E4=B8=8A=E5=8D=8811:56, Ming Lei wrote: >> Hi Guys, >> >> The multipage bvec patchset[1] has been posted out for a while, and >> xfstest(ext4, xfs and btrfs) have been run and no regression is >> observed, and I hope having talk about this in person would help >> moving it forward. >> >> Secondly I'd like to discuss with guys about the following next steps >> of mp-bvec: >> >> 1) cleanup raid1/raid5/raid10 for removing the only singlepage bvec path > > Hi Ming, > > I am interested on this topic. Could you please provide a hint that what > is the proper way to remove single page bvec from md raid code ? Basically speaking the raid code can't access the bvec table directly like referencing .bi_vcnt or .bi_io_vec once multipage bvec is supported, especially after pages are added to the bio via bio_add_page(). I am looking at the raid1 code, and maybe we can discuss a bit about the cleanup. > And > will dm code involved in as well ? No, nothing at all, and no such usage in dm code. Thanks, Ming Lei