From: Guixin Liu <kanie@linux.alibaba.com>
To: Chaitanya Kulkarni <chaitanyak@nvidia.com>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"hch@lst.de" <hch@lst.de>, "sagi@grimberg.me" <sagi@grimberg.me>
Subject: Re: [PATCH] nvmet: make nvmet_wq visible in sysfs
Date: Tue, 29 Oct 2024 14:46:05 +0800 [thread overview]
Message-ID: <0e90730a-74c0-401a-82bd-92fdbcd2cbe0@linux.alibaba.com> (raw)
In-Reply-To: <8b4591d7-f0bd-4e4c-b1b3-1b375f25bda0@nvidia.com>
在 2024/10/29 13:04, Chaitanya Kulkarni 写道:
> On 10/28/24 18:49, Guixin Liu wrote:
>> Make nvmet_wq visible in sysfs, allowing for tuning the it's attr
>> through sysfs.
>>
>> Signed-off-by: Guixin Liu<kanie@linux.alibaba.com>
>> ---
> do you happened have a usecase for this?
>
> -ck
Sometimes, in order to respond promptly to certain events or
manage commands, we need to reserve resources and partition
the CPU cores. For example, if there are 4 cores available,
we can initially allocate them by dedicating one core for
management while the remaining 3 cores are specifically for handling IO.
Best Regards,
Guixin Liu
>
next prev parent reply other threads:[~2024-10-29 6:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 1:49 [PATCH] nvmet: make nvmet_wq visible in sysfs Guixin Liu
2024-10-29 5:04 ` Chaitanya Kulkarni
2024-10-29 6:46 ` Guixin Liu [this message]
2024-10-29 19:52 ` Chaitanya Kulkarni
2024-10-30 0:49 ` Chaitanya Kulkarni
2024-10-30 1:44 ` Guixin Liu
2024-10-30 5:53 ` hch
2024-10-30 6:44 ` Guixin Liu
2024-10-30 6:33 ` Chaitanya Kulkarni
2024-10-30 11:20 ` Guixin Liu
2024-10-30 18:38 ` Chaitanya Kulkarni
2024-10-31 2:01 ` Guixin Liu
2024-10-31 2:45 ` Chaitanya Kulkarni
2024-10-31 6:39 ` Chaitanya Kulkarni
2024-10-31 6:55 ` Guixin Liu
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=0e90730a-74c0-401a-82bd-92fdbcd2cbe0@linux.alibaba.com \
--to=kanie@linux.alibaba.com \
--cc=chaitanyak@nvidia.com \
--cc=hch@lst.de \
--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.