From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: mingzhe.zou@easystack.cn, target-devel@vger.kernel.org,
linux-scsi@vger.kernel.org
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>, zoumingzhe@qq.com
Subject: Re: [PATCH v3] target: add iscsi/cpus_allowed_list in configfs
Date: Fri, 18 Mar 2022 23:57:00 -0400 [thread overview]
Message-ID: <164766213030.31329.5393511645473283160.b4-ty@oracle.com> (raw)
In-Reply-To: <20220301075500.14266-1-mingzhe.zou@easystack.cn>
On Tue, 1 Mar 2022 15:55:00 +0800, mingzhe.zou@easystack.cn wrote:
> From: Mingzhe Zou <mingzhe.zou@easystack.cn>
>
> The RX/TX threads for iSCSI connection can be scheduled to
> any online cpus, and will not be rescheduled.
>
> If bind other heavy load threads with iSCSI connection
> RX/TX thread to the same cpu, the iSCSI performance will
> be worse.
>
> [...]
Applied to 5.18/scsi-queue, thanks!
[1/1] target: add iscsi/cpus_allowed_list in configfs
https://git.kernel.org/mkp/scsi/c/d72d827f2f26
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2022-03-19 3:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 8:38 [PATCH] target: add iscsi/cpus_allowed_list in configfs mingzhe.zou
2022-02-08 17:50 ` Mike Christie
2022-02-09 11:48 ` Zou Mingzhe
2022-02-16 17:13 ` Mike Christie
2022-02-17 7:45 ` [PATCH v2] " mingzhe.zou
2022-02-23 6:24 ` Zou Mingzhe
2022-02-23 15:51 ` michael.christie
2022-02-28 17:58 ` Mike Christie
2022-03-01 7:35 ` Zou Mingzhe
2022-03-01 7:55 ` [PATCH v3] " mingzhe.zou
2022-03-08 8:34 ` Zou Mingzhe
2022-03-09 19:27 ` Mike Christie
2022-03-15 3:40 ` Martin K. Petersen
2022-03-19 3:57 ` Martin K. Petersen [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=164766213030.31329.5393511645473283160.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mingzhe.zou@easystack.cn \
--cc=target-devel@vger.kernel.org \
--cc=zoumingzhe@qq.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 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.