From: Stephen Hemminger <stephen@networkplumber.org>
To: Ciara Loftus <ciara.loftus@intel.com>
Cc: dev@dpdk.org, xiaolong.ye@intel.com, kevin.laatz@intel.com,
bruce.richardson@intel.com
Subject: Re: [dpdk-dev] [PATCH v2 2/3] net/af_xdp: support pinning of IRQs
Date: Mon, 30 Sep 2019 10:11:37 -0700 [thread overview]
Message-ID: <20190930101137.4919f93e@hermes.lan> (raw)
In-Reply-To: <20190930164205.19419-3-ciara.loftus@intel.com>
On Mon, 30 Sep 2019 16:42:04 +0000
Ciara Loftus <ciara.loftus@intel.com> wrote:
> +/* drivers supported for the queue_irq option */
> +enum supported_drivers {
> + I40E_DRIVER,
> + IXGBE_DRIVER,
> + MLX5_DRIVER,
> + NUM_DRIVERS
> +};
Anything device specific like this raises a red flag to me.
This regex etc, seems like a huge hack. Is there a better way using
irqbalance and smp_affinity in kernel drivers?
NACK
next prev parent reply other threads:[~2019-09-30 17:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 16:42 [dpdk-dev] [PATCH v2 0/3] AF_XDP tx halt fix, IRQ pinning and unaligned chunks Ciara Loftus
2019-09-30 16:42 ` [dpdk-dev] [PATCH v2 1/3] net/af_xdp: fix Tx halt when no recv packets Ciara Loftus
2019-10-22 5:32 ` Ye Xiaolong
2019-09-30 16:42 ` [dpdk-dev] [PATCH v2 2/3] net/af_xdp: support pinning of IRQs Ciara Loftus
2019-09-30 17:11 ` Stephen Hemminger [this message]
2019-10-03 13:23 ` Loftus, Ciara
2019-10-14 14:43 ` Bruce Richardson
2019-10-21 15:24 ` Ferruh Yigit
2019-10-21 15:54 ` Bruce Richardson
2019-10-21 16:02 ` Ferruh Yigit
2019-10-21 16:14 ` Bruce Richardson
2019-10-15 11:14 ` Ray Kinsella
2019-10-21 10:04 ` Loftus, Ciara
2019-10-21 12:52 ` Varghese, Vipin
2019-10-21 13:04 ` Bruce Richardson
2019-10-21 13:11 ` Varghese, Vipin
2019-10-21 13:17 ` Bruce Richardson
2019-10-21 13:45 ` Varghese, Vipin
2019-10-21 13:56 ` Bruce Richardson
2019-10-21 14:06 ` Varghese, Vipin
2019-10-18 23:49 ` Ye Xiaolong
2019-09-30 16:42 ` [dpdk-dev] [PATCH v2 3/3] net/af_xdp: enable support for unaligned umem chunks Ciara Loftus
2019-10-18 23:48 ` Ye Xiaolong
2019-10-22 14:28 ` Ferruh Yigit
2019-10-24 11:10 ` David Marchand
2019-10-24 12:18 ` David Marchand
2019-10-24 14:18 ` Ferruh Yigit
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=20190930101137.4919f93e@hermes.lan \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=ciara.loftus@intel.com \
--cc=dev@dpdk.org \
--cc=kevin.laatz@intel.com \
--cc=xiaolong.ye@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;
as well as URLs for NNTP newsgroup(s).