From: Christoph Hellwig <hch@lst.de>
To: Hannes Reinecke <hare@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Keith Busch <kbusch@kernel.org>,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvme-tcp: align I/O cpu with blk-mq mapping
Date: Wed, 19 Jun 2024 07:30:15 +0200 [thread overview]
Message-ID: <20240619053015.GB29159@lst.de> (raw)
In-Reply-To: <20240618120345.64761-1-hare@kernel.org>
On Tue, Jun 18, 2024 at 02:03:45PM +0200, Hannes Reinecke wrote:
> Add a new module parameter 'wq_affinity' to spread the I/O
> over all cpus within the blk-mq hctx mapping for the queue.
> This avoids bouncing I/O between cpus when we have less
> hardware queues than cpus.
What is the benefit when setting it? What is the downside? Why do you
think it needs to be conditional?
> + }
> if (wq_unbound)
> queue->io_cpu = WORK_CPU_UNBOUND;
> + else if (wq_affinity) {
Missing curly braces. But this also means the wq_unbound options
is incompatible with your new one.
> + } else
> queue->io_cpu = cpumask_next_wrap(n - 1, cpu_online_mask, -1, false);
Overly long line here.
next prev parent reply other threads:[~2024-06-19 5:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 12:03 [PATCH] nvme-tcp: align I/O cpu with blk-mq mapping Hannes Reinecke
2024-06-19 5:30 ` Christoph Hellwig [this message]
2024-06-19 8:57 ` Sagi Grimberg
2024-06-19 10:01 ` Hannes Reinecke
2024-06-19 10:14 ` Sagi Grimberg
2024-06-19 10:09 ` Hannes Reinecke
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=20240619053015.GB29159@lst.de \
--to=hch@lst.de \
--cc=hare@kernel.org \
--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 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.