From: Nitesh Shetty <nitheshshetty@gmail.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Damien Le Moal <dlemoal@kernel.org>,
Ming Lei <ming.lei@redhat.com>
Subject: Re: [PATCH v4 1/7] block: Introduce the flag QUEUE_FLAG_NO_ZONE_WRITE_LOCK
Date: Thu, 27 Jul 2023 16:29:22 +0530 [thread overview]
Message-ID: <CAOSviJ0uBynC9M16cRusttU1OaB4HJS8=xmjCGP7bUCMicmiOA@mail.gmail.com> (raw)
In-Reply-To: <20230726193440.1655149-2-bvanassche@acm.org>
On Thu, Jul 27, 2023 at 1:39 AM Bart Van Assche <bvanassche@acm.org> wrote:
> + * Do not use the zone write lock for sequential writes for sequential write
> + * required zones.
> + */
> +#define QUEUE_FLAG_NO_ZONE_WRITE_LOCK 8
Instead of QUEUE_FLAG_NO_ZONE_WRITE_LOCK I feel
QUEUE_FLAG_SKIP_ZONE_WRITE_LOCK is better.
--Nitesh Shetty
next prev parent reply other threads:[~2023-07-27 10:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 19:34 [PATCH v4 0/7] Improve the performance of F2FS on zoned UFS Bart Van Assche
2023-07-26 19:34 ` [PATCH v4 1/7] block: Introduce the flag QUEUE_FLAG_NO_ZONE_WRITE_LOCK Bart Van Assche
2023-07-26 23:49 ` Damien Le Moal
2023-07-27 0:54 ` Chaitanya Kulkarni
2023-07-27 20:20 ` Bart Van Assche
2023-07-27 20:52 ` Chaitanya Kulkarni
2023-07-27 10:59 ` Nitesh Shetty [this message]
2023-07-27 14:43 ` Bart Van Assche
2023-07-27 19:06 ` Nitesh Shetty
2023-07-26 19:34 ` [PATCH v4 2/7] block: Introduce the flag REQ_NO_ZONE_WRITE_LOCK Bart Van Assche
2023-07-27 0:03 ` Damien Le Moal
2023-07-26 19:34 ` [PATCH v4 3/7] block/mq-deadline: Only use zone locking if necessary Bart Van Assche
2023-07-27 0:09 ` Damien Le Moal
2023-07-26 19:34 ` [PATCH v4 4/7] block/null_blk: Support disabling zone write locking Bart Van Assche
2023-07-27 0:04 ` Damien Le Moal
2023-07-27 0:36 ` Chaitanya Kulkarni
2023-07-27 20:26 ` Bart Van Assche
2023-07-27 19:02 ` Nitesh Shetty
2023-07-26 19:34 ` [PATCH v4 5/7] scsi: Retry unaligned zoned writes Bart Van Assche
2023-07-27 0:33 ` Damien Le Moal
2023-07-27 1:03 ` Bart Van Assche
2023-07-27 1:09 ` Damien Le Moal
2023-07-27 14:53 ` Bart Van Assche
2023-07-27 20:57 ` Bart Van Assche
2023-07-26 19:34 ` [PATCH v4 6/7] scsi: ufs: Disable zone write locking Bart Van Assche
2023-07-27 21:55 ` kernel test robot
2023-07-26 19:34 ` [PATCH v4 7/7] fs/f2fs: " Bart Van Assche
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='CAOSviJ0uBynC9M16cRusttU1OaB4HJS8=xmjCGP7bUCMicmiOA@mail.gmail.com' \
--to=nitheshshetty@gmail.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=dlemoal@kernel.org \
--cc=hch@lst.de \
--cc=jaegeuk@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.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).