From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Ahmed Zaki <ahmed.zaki@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org
Subject: Re: [Intel-wired-lan] [PATCH RFC net-next 2/2] idpf: use napi's irq affinity
Date: Fri, 6 Dec 2024 09:29:28 +0100 [thread overview]
Message-ID: <c011ef8d-04c0-485e-8fd9-e05952bfef82@molgen.mpg.de> (raw)
In-Reply-To: <20241206001209.213168-3-ahmed.zaki@intel.com>
Dear Ahmed,
Thank you for your patch.
Am 06.12.24 um 01:12 schrieb Ahmed Zaki:
> Delete the driver CPU affinity info and use the core's napi config
> instead.
Excuse my ignorance, but could you please state why? (Is the core’s napi
config the successor?)
> Cc: intel-wired-lan@lists.osuosl.org
> Signed-off-by: Ahmed Zaki <ahmed.zaki@intel.com>
> ---
> drivers/net/ethernet/intel/idpf/idpf_txrx.c | 18 ++++--------------
> drivers/net/ethernet/intel/idpf/idpf_txrx.h | 6 ++----
> 2 files changed, 6 insertions(+), 18 deletions(-)
[…]
Kind regards,
Paul
next prev parent reply other threads:[~2024-12-06 8:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241206001209.213168-1-ahmed.zaki@intel.com>
2024-12-06 0:12 ` [Intel-wired-lan] [PATCH RFC net-next 2/2] idpf: use napi's irq affinity Ahmed Zaki
2024-12-06 8:29 ` Paul Menzel [this message]
2024-12-06 17:58 ` Ahmed Zaki
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=c011ef8d-04c0-485e-8fd9-e05952bfef82@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=ahmed.zaki@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev@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