From: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
To: "hch@lst.de" <hch@lst.de>
Cc: Keith Busch <kbusch@kernel.org>,
Mark Ruijter <MRuijter@onestopsystems.com>,
Hannes Reinecke <hare@suse.com>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH] nvmet: introduce use_vfs ns-attr
Date: Mon, 28 Oct 2019 07:38:05 +0000 [thread overview]
Message-ID: <BYAPR04MB5749A6D339572EFC0C9C401686660@BYAPR04MB5749.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20191028073545.GA20427@lst.de
On 10/28/19 12:35 AM, hch@lst.de wrote:
> On Mon, Oct 28, 2019 at 07:32:45AM +0000, Chaitanya Kulkarni wrote:
>> Just did a quick test with following patch on the top of
>> plug patch :-
>
> Yes, that change makes total sense - in fact Keith also mentioned I
> placed the finish_plug incorrectly.
>
Do you want me to send a new plug patch with updated patch
description and performance numbers keeping you original
author ?
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2019-10-28 7:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 20:17 [PATCH] nvmet: introduce use_vfs ns-attr Chaitanya Kulkarni
2019-10-24 2:00 ` Keith Busch
2019-10-24 11:30 ` Mark Ruijter
2019-10-25 4:05 ` Keith Busch
2019-10-25 4:26 ` Keith Busch
2019-10-25 8:44 ` Mark Ruijter
2019-10-26 1:06 ` Keith Busch
2019-10-27 15:03 ` hch
2019-10-27 16:06 ` Mark Ruijter
2019-10-28 0:55 ` Keith Busch
2019-10-28 7:26 ` Chaitanya Kulkarni
2019-10-28 7:32 ` Chaitanya Kulkarni
2019-10-28 7:35 ` hch
2019-10-28 7:38 ` Chaitanya Kulkarni [this message]
2019-10-28 7:43 ` hch
2019-10-28 8:04 ` Chaitanya Kulkarni
2019-10-28 8:01 ` Keith Busch
2019-10-28 8:41 ` Mark Ruijter
2019-10-25 3:29 ` Chaitanya Kulkarni
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=BYAPR04MB5749A6D339572EFC0C9C401686660@BYAPR04MB5749.namprd04.prod.outlook.com \
--to=chaitanya.kulkarni@wdc.com \
--cc=MRuijter@onestopsystems.com \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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).