Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Szycik <marcin.szycik@linux.intel.com>
To: Tony Nguyen <anthony.l.nguyen@intel.com>,
	intel-wired-lan@lists.osuosl.org,
	Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Cc: mustafa.ismail@intel.com, shiraz.saleem@intel.com
Subject: Re: [Intel-wired-lan] [PATCH net-next] ice: Do not use WQ_MEM_RECLAIM flag for workqueue
Date: Thu, 1 Dec 2022 10:31:46 +0100	[thread overview]
Message-ID: <f4b4a380-edda-3864-33a0-51bcb013e483@linux.intel.com> (raw)
In-Reply-To: <e1a372de-05e7-118a-dc92-1083bb8df883@intel.com>

Sorry, my bad. I'll send v2.

On 30.11.2022 20:50, Tony Nguyen wrote:
> 
> 
> On 11/30/2022 4:34 AM, Marcin Szycik wrote:
> 
> I believe Ani is the author for this? I don't see him as the author though.
> 
> i.e.
> From: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
> 
>> When both ice and the irdma driver are loaded, a warning
>> in check_flush_dependency is being triggered. This seems
>> to be because of the ice driver workqueue is allocated with
>> the WQ_MEM_RECLAIM flag, and the irdma one is not.
>>
>> Looking at the kernel documentation, it doesn't seem like
>> the ice driver needs to use WQ_MEM_RECLAIM. Remove it.
>>
>> Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
>> Signed-off-by: Marcin Szycik <marcin.szycik@linux.intel.com>
>> ---
>>   drivers/net/ethernet/intel/ice/ice_main.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/net/ethernet/intel/ice/ice_main.c b/drivers/net/ethernet/intel/ice/ice_main.c
>> index 69984fea7fce..d01d1073ffec 100644
>> --- a/drivers/net/ethernet/intel/ice/ice_main.c
>> +++ b/drivers/net/ethernet/intel/ice/ice_main.c
>> @@ -5617,7 +5617,7 @@ static int __init ice_module_init(void)
>>       pr_info("%s\n", ice_driver_string);
>>       pr_info("%s\n", ice_copyright);
>>   -    ice_wq = alloc_workqueue("%s", WQ_MEM_RECLAIM, 0, KBUILD_MODNAME);
>> +    ice_wq = alloc_workqueue("%s", 0, 0, KBUILD_MODNAME);
>>       if (!ice_wq) {
>>           pr_err("Failed to create workqueue\n");
>>           return -ENOMEM;
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

      reply	other threads:[~2022-12-01  9:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30 12:34 [Intel-wired-lan] [PATCH net-next] ice: Do not use WQ_MEM_RECLAIM flag for workqueue Marcin Szycik
2022-11-30 19:50 ` Tony Nguyen
2022-12-01  9:31   ` Marcin Szycik [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=f4b4a380-edda-3864-33a0-51bcb013e483@linux.intel.com \
    --to=marcin.szycik@linux.intel.com \
    --cc=anirudh.venkataramanan@intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=mustafa.ismail@intel.com \
    --cc=shiraz.saleem@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox