From: Wang Jinchao <wangjinchao@xfusion.com>
To: Steffen Klassert <steffen.klassert@secunet.com>,
Daniel Jordan <daniel.m.jordan@oracle.com>,
<linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <stone.xulei@xfusion.com>
Subject: Issue: Can padata avoid dealing with CPU-related operations?
Date: Wed, 27 Sep 2023 21:25:54 +0800 [thread overview]
Message-ID: <ZRQtYnAhF2byr784@fedora> (raw)
Hello, I have a few questions about the padata code I've been studying recently:
- Why does padata use the WQ_UNBOUND attribute of the workqueue? Because I've noticed a significant maintenance cost related to CPUs. Are there any specific benefits?
- In what scenarios is it necessary to specify a CPU for serial execution, or is ensuring the order sufficient?
In fact, the two questions can be summarized into one: Is it possible to avoid handling CPU-related operations to simplify the code logic?
Thanks.
next reply other threads:[~2023-09-27 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 13:25 Wang Jinchao [this message]
2023-10-04 14:52 ` Issue: Can padata avoid dealing with CPU-related operations? Daniel Jordan
2023-10-07 2:56 ` Wang Jinchao
2023-10-25 17:14 ` Daniel Jordan
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=ZRQtYnAhF2byr784@fedora \
--to=wangjinchao@xfusion.com \
--cc=daniel.m.jordan@oracle.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=stone.xulei@xfusion.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;
as well as URLs for NNTP newsgroup(s).