From: Christian Loehle <christian.loehle@arm.com>
To: Bart Van Assche <bvanassche@acm.org>,
MANISH PANDEY <quic_mapa@quicinc.com>,
Sandeep Dhavale <dhavale@google.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>
Cc: Qais Yousef <qyousef@layalina.io>,
axboe@kernel.dk, mingo@kernel.org, peterz@infradead.org,
vincent.guittot@linaro.org, linux-block@vger.kernel.org,
sudeep.holla@arm.com, Jaegeuk Kim <jaegeuk@kernel.org>,
Christoph Hellwig <hch@infradead.org>,
kailash@google.com, tkjos@google.com, bvanassche@google.com,
quic_nitirawa@quicinc.com, quic_cang@quicinc.com,
quic_rampraka@quicinc.com, quic_narepall@quicinc.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Regarding patch "block/blk-mq: Don't complete locally if capacities are different"
Date: Mon, 26 Aug 2024 18:32:10 +0100 [thread overview]
Message-ID: <a93c34a9-7fcf-4bb9-9c67-20202e2f6e59@arm.com> (raw)
In-Reply-To: <340f156b-0dbb-45d2-a6dd-31e468ead846@acm.org>
On 8/23/24 15:12, Bart Van Assche wrote:
> On 8/23/24 6:49 AM, MANISH PANDEY wrote:
>> while making the patch, i figured out that queue_flags is unsigned long type and we already reached up to 32 flags as of now.
>
> Really? In Linus' master branch I see 13 queue flags. This is less than
> half of 32. From include/linux/blkdev.h:
@Manish:
See recent (6.11) cleanup
https://lore.kernel.org/linux-block/20240719112912.3830443-1-john.g.garry@oracle.com/
>
> enum {
> QUEUE_FLAG_DYING, /* queue being torn down */
> QUEUE_FLAG_NOMERGES, /* disable merge attempts */
> QUEUE_FLAG_SAME_COMP, /* complete on same CPU-group */
> QUEUE_FLAG_FAIL_IO, /* fake timeout */
> QUEUE_FLAG_NOXMERGES, /* No extended merges */
> QUEUE_FLAG_SAME_FORCE, /* force complete on same CPU */
> QUEUE_FLAG_INIT_DONE, /* queue is initialized */
> QUEUE_FLAG_STATS, /* track IO start and completion times */
> QUEUE_FLAG_REGISTERED, /* queue has been registered to a disk */
> QUEUE_FLAG_QUIESCED, /* queue has been quiesced */
> QUEUE_FLAG_RQ_ALLOC_TIME, /* record rq->alloc_time_ns */
> QUEUE_FLAG_HCTX_ACTIVE, /* at least one blk-mq hctx is active */
> QUEUE_FLAG_SQ_SCHED, /* single queue style io dispatch */
> QUEUE_FLAG_MAX
> };
>
> Bart.
>
next prev parent reply other threads:[~2024-08-26 17:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 13:46 Regarding patch "block/blk-mq: Don't complete locally if capacities are different" MANISH PANDEY
2024-08-01 9:25 ` MANISH PANDEY
2024-08-01 16:05 ` Qais Yousef
2024-08-02 9:03 ` Christian Loehle
2024-08-05 2:07 ` Qais Yousef
2024-08-05 10:18 ` Christian Loehle
2024-08-05 17:24 ` MANISH PANDEY
2024-08-09 0:47 ` Qais Yousef
2024-08-09 0:23 ` Qais Yousef
2024-08-13 16:20 ` Christian Loehle
2024-09-01 17:25 ` Qais Yousef
2024-08-05 17:17 ` Bart Van Assche
2024-08-05 17:35 ` MANISH PANDEY
2024-08-05 17:52 ` Bart Van Assche
2024-08-08 6:05 ` MANISH PANDEY
2024-08-09 0:36 ` Qais Yousef
2024-08-11 17:41 ` Dietmar Eggemann
2024-08-12 18:15 ` Sandeep Dhavale
2024-08-21 12:29 ` MANISH PANDEY
2024-08-21 17:22 ` Bart Van Assche
2024-08-22 10:46 ` MANISH PANDEY
2024-08-22 14:24 ` Bart Van Assche
2024-08-23 7:57 ` MANISH PANDEY
2024-08-23 12:03 ` Christian Loehle
2024-08-23 13:49 ` MANISH PANDEY
2024-08-23 14:12 ` Bart Van Assche
2024-08-26 17:32 ` Christian Loehle [this message]
2024-09-01 17:13 ` Qais Yousef
2024-08-09 0:28 ` Qais Yousef
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=a93c34a9-7fcf-4bb9-9c67-20202e2f6e59@arm.com \
--to=christian.loehle@arm.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=bvanassche@google.com \
--cc=dhavale@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=hch@infradead.org \
--cc=jaegeuk@kernel.org \
--cc=kailash@google.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=quic_cang@quicinc.com \
--cc=quic_mapa@quicinc.com \
--cc=quic_narepall@quicinc.com \
--cc=quic_nitirawa@quicinc.com \
--cc=quic_rampraka@quicinc.com \
--cc=qyousef@layalina.io \
--cc=sudeep.holla@arm.com \
--cc=tkjos@google.com \
--cc=vincent.guittot@linaro.org \
/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