From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH] nvmet: use shared workqueue for file-ns
Date: Thu, 21 Jun 2018 23:03:01 -0700 [thread overview]
Message-ID: <20180622060301.GA24685@infradead.org> (raw)
In-Reply-To: <20180621214736.6238-1-chaitanya.kulkarni@wdc.com>
On Thu, Jun 21, 2018@05:47:36PM -0400, Chaitanya Kulkarni wrote:
> This patch removes the per-ns workqueue and adds per-subsys workqueue
> which is shared by all the namespaces belongs to the same subsystem to
> offload the I/O submission for buffered I/Os for the file-backed namespace.
I think we can just have an entirely global workqueue instead of the
per-subsystem one. We can then also use it directly instead of needing
the pointer in struct nvmet_ns.
prev parent reply other threads:[~2018-06-22 6:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 21:47 [PATCH] nvmet: use shared workqueue for file-ns Chaitanya Kulkarni
2018-06-22 6:03 ` Christoph Hellwig [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=20180622060301.GA24685@infradead.org \
--to=hch@infradead.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 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.