From: Nitesh Shetty <nj.shetty@samsung.com>
To: Chaitanya Kulkarni <chaitanyak@nvidia.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-bcache@vger.kernel.org" <linux-bcache@vger.kernel.org>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"josef@toxicpanda.com" <josef@toxicpanda.com>,
"minchan@kernel.org" <minchan@kernel.org>,
"senozhatsky@chromium.org" <senozhatsky@chromium.org>,
"colyli@suse.de" <colyli@suse.de>,
"kent.overstreet@gmail.com" <kent.overstreet@gmail.com>,
"dlemoal@kernel.org" <dlemoal@kernel.org>,
"johannes.thumshirn@wdc.com" <johannes.thumshirn@wdc.com>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"vincent.fu@samsung.com" <vincent.fu@samsung.com>,
"akinobu.mita@gmail.com" <akinobu.mita@gmail.com>,
"shinichiro.kawasaki@wdc.com" <shinichiro.kawasaki@wdc.com>,
"nbd@other.debian.org" <nbd@other.debian.org>,
"Jason@zx2c4.com" <Jason@zx2c4.com>
Subject: Re: [PATCH 0/5] block/drivers: don't clear the flag that is not set
Date: Mon, 24 Apr 2023 16:10:46 +0530 [thread overview]
Message-ID: <20230424104046.GA17688@green245> (raw)
In-Reply-To: <86043b4b-0960-215f-17a7-4c1facdb0713@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 756 bytes --]
On Mon, Apr 24, 2023 at 10:25:34AM +0000, Chaitanya Kulkarni wrote:
> On 4/24/23 02:26, Nitesh Shetty wrote:
> > On 23/04/24 12:30AM, Chaitanya Kulkarni wrote:
> >> null_blk
> >> brd
> >> nbd
> >> zram
> >> bcache
> >
> > Any particular reason for leaving out mtip and s390 drivers ?
> >
>
> I didn't find why this flag is clear at first place,
> if this gets accepted I'll others gradually..
>
> > Will it be better to use the flag similar to scsi devices and
> > use it for random number generation ?
> >
>
> I didn't understand this comment.
>
My bad. I intended, may be we can set QUEUE_FLAG_ADD_RANDOM flag.
Similar to scsi once the request completes, using function
add_disc_randomness() random generator can be updated.
Regards,
Nitesh Shetty
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2023-04-24 12:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230424092940epcas5p3407002e7d5c79593ffbafc38f2b49e51@epcas5p3.samsung.com>
2023-04-24 7:30 ` [PATCH 0/5] block/drivers: don't clear the flag that is not set Chaitanya Kulkarni
2023-04-24 7:30 ` [PATCH 1/5] null_blk: " Chaitanya Kulkarni
2023-04-24 7:30 ` [PATCH 2/5] brd: " Chaitanya Kulkarni
2023-04-24 7:30 ` [PATCH 3/5] nbd: " Chaitanya Kulkarni
2023-04-24 7:30 ` [PATCH 4/5] zram: " Chaitanya Kulkarni
2023-04-24 7:30 ` [PATCH 5/5] bcache: " Chaitanya Kulkarni
2023-04-24 10:19 ` [PATCH 5/5] bcache: don't clear the flag that is not set^[ Coly Li
2023-04-24 9:26 ` [PATCH 0/5] block/drivers: don't clear the flag that is not set Nitesh Shetty
2023-04-24 10:25 ` Chaitanya Kulkarni
2023-04-24 10:40 ` Nitesh Shetty [this message]
2023-04-24 16:39 ` Jens Axboe
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=20230424104046.GA17688@green245 \
--to=nj.shetty@samsung.com \
--cc=Jason@zx2c4.com \
--cc=akinobu.mita@gmail.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=chaitanyak@nvidia.com \
--cc=colyli@suse.de \
--cc=dlemoal@kernel.org \
--cc=johannes.thumshirn@wdc.com \
--cc=josef@toxicpanda.com \
--cc=kent.overstreet@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=nbd@other.debian.org \
--cc=senozhatsky@chromium.org \
--cc=shinichiro.kawasaki@wdc.com \
--cc=vincent.fu@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.