From: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Max Gurtovoy <mgurtovoy@nvidia.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"oren@nvidia.com" <oren@nvidia.com>,
"idanb@nvidia.com" <idanb@nvidia.com>,
"yossike@nvidia.com" <yossike@nvidia.com>,
Damien Le Moal <Damien.LeMoal@wdc.com>
Subject: Re: [PATCH v2 1/1] null_blk: add option for managing virtual boundary
Date: Mon, 12 Apr 2021 17:57:48 +0000 [thread overview]
Message-ID: <BYAPR04MB4965C17CF4AA51BE9C5C5F7486709@BYAPR04MB4965.namprd04.prod.outlook.com> (raw)
In-Reply-To: af599b5f-0e1f-99c8-8d59-73fc48227d9c@kernel.dk
Jens,
On 4/12/21 05:48, Jens Axboe wrote:
> On 4/12/21 3:55 AM, Max Gurtovoy wrote:
>> This will enable changing the virtual boundary of null blk devices. For
>> now, null blk devices didn't have any restriction on the scatter/gather
>> elements received from the block layer. Add a module parameter and a
>> configfs option that will control the virtual boundary. This will
>> enable testing the efficiency of the block layer bounce buffer in case
>> a suitable application will send discontiguous IO to the given device.
> Applied, thanks.
>
If this is still on the top and can be done easily please add.
Reviewed-by: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
prev parent reply other threads:[~2021-04-12 17:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 9:55 [PATCH v2 1/1] null_blk: add option for managing virtual boundary Max Gurtovoy
2021-04-12 11:53 ` Damien Le Moal
2021-04-12 12:47 ` Jens Axboe
2021-04-12 17:57 ` Chaitanya Kulkarni [this message]
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=BYAPR04MB4965C17CF4AA51BE9C5C5F7486709@BYAPR04MB4965.namprd04.prod.outlook.com \
--to=chaitanya.kulkarni@wdc.com \
--cc=Damien.LeMoal@wdc.com \
--cc=axboe@kernel.dk \
--cc=idanb@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mgurtovoy@nvidia.com \
--cc=oren@nvidia.com \
--cc=yossike@nvidia.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).