From: Jeff Cody <jcody@redhat.com>
To: Jaze Lee <jazeltq@gmail.com>
Cc: Josh Durgin <jdurgin@redhat.com>,
Jason Dillaman <dillaman@redhat.com>,
Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>,
qemu-block@nongnu.org, qemu-devel@nongnu.org,
ceph-devel <ceph-devel@vger.kernel.org>,
tianqing <tianqing@unitedstack.com>
Subject: Re: [Qemu-devel] [RFC v6] RBD: Add support readv,writev for rbd
Date: Fri, 24 Feb 2017 06:42:22 -0500 [thread overview]
Message-ID: <20170224114222.GA16659@localhost.localdomain> (raw)
In-Reply-To: <CAKZcxgcWpz5g-WdeFNu8Ad_4PQZMPHoJDmn_1HENntVLLZG_Jg@mail.gmail.com>
On Fri, Feb 24, 2017 at 02:09:31PM +0800, Jaze Lee wrote:
> 2017-02-24 11:52 GMT+08:00 Jeff Cody <jcody@redhat.com>:
> > On Tue, Feb 21, 2017 at 02:50:03PM +0800, jazeltq@gmail.com wrote:
> >> From: tianqing <tianqing@unitedstack.com>
> >>
> >> Rbd can do readv and writev directly, so wo do not need to transform
> >> iov to buf or vice versa any more.
> >>
> >> Signed-off-by: tianqing <tianqing@unitedstack.com>
> >> ---
> >
> >
> > This is marked as an RFC still - is this a series you would like to see in
> > 2.9?
>
> Yes. What should i do if i like it in 2.9
>
Ideally you would submit the series as a non-RFC patch (that is, it would
have progressed to a normal patch away from RFC).
But in this case, it seems to me that this patch has progressed beyond RFC;
is there any reason it is still marked as RFC instead of just a patch? It
looks OK to me.
next prev parent reply other threads:[~2017-02-24 11:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 6:50 [Qemu-devel] [RFC v6] RBD: Add support readv,writev for rbd jazeltq
2017-02-24 3:52 ` Jeff Cody
2017-02-24 6:09 ` Jaze Lee
2017-02-24 11:42 ` Jeff Cody [this message]
2017-02-24 12:51 ` Jaze Lee
-- strict thread matches above, loose matches on Subject: below --
2017-02-21 3:43 jazeltq
2017-02-21 3:50 ` no-reply
2017-02-21 4:01 ` no-reply
2017-02-21 4:50 ` Jeff Cody
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170224114222.GA16659@localhost.localdomain \
--to=jcody@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=dillaman@redhat.com \
--cc=jazeltq@gmail.com \
--cc=jdurgin@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=tianqing@unitedstack.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).