From: Mike Christie <michael.christie@oracle.com>
To: Zou Mingzhe <mingzhe.zou@easystack.cn>,
martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
target-devel@vger.kernel.org
Subject: Re: [PATCH] target: add iscsi/cpus_allowed_list in configfs
Date: Wed, 16 Feb 2022 11:13:38 -0600 [thread overview]
Message-ID: <1ba93dce-7dbe-89da-a026-e8816c678f9b@oracle.com> (raw)
In-Reply-To: <7ff3a449-980e-ab44-42cf-7520a0796483@easystack.cn>
On 2/9/22 5:48 AM, Zou Mingzhe wrote:
>>> +cpumask_t __iscsi_allowed_cpumask;
>> Maybe better to put this in iscsi_target.c with the other vars like
>> it.
>
> Originally I wanted to put it in struct iscsit_global and use it in iscsit_thread_check_cpumask.
>
> However iscsit_thread_check_cpumask is also called in cxgbit_target.c. I don't know if I also
>
> need to modify cxgbit at the same time, and I only modified two calls in iscsi_target.c. I would
>
The new configfs file shows up for software iscsi and cxgb right? If so I think you need to
modify both, or you end up with a file that returns success but doesn't do anything and it's
confusing to users. It's also a simple change to cxgb.
> like to know how to handle in cxgbit_target.c?
>
> I want to move 'static inline void iscsit_thread_check_cpumask' from iscsi_target_core.h to
>
> iscsi_target.c and EXPORT_SYMBOL(iscsit_thread_check_cpumask). Do you agree it?
>
I think that is ok.
next prev parent reply other threads:[~2022-02-16 17:13 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 [this message]
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
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=1ba93dce-7dbe-89da-a026-e8816c678f9b@oracle.com \
--to=michael.christie@oracle.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mingzhe.zou@easystack.cn \
--cc=target-devel@vger.kernel.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