From: Stephen Hemminger <stephen@networkplumber.org>
To: Vladimir Ratnikov <vratnikov@netgate.com>
Cc: hkalra@marvell.com, dev@dpdk.org,
Junfeng Guo <junfeng.guo@intel.com>,
Simei Su <simei.su@intel.com>,
qi.z.zhang@intel.com, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH] eal/interrupts: Allow UIO interrupts when using igb_uio
Date: Tue, 4 Jul 2023 08:55:30 -0700 [thread overview]
Message-ID: <20230704085530.1cf47bc7@hermes.local> (raw)
In-Reply-To: <CABxizg7T485u3jEBkN9iMUHYKXv+HD0XNuGqZDOBvA8+2YKqhg@mail.gmail.com>
On Tue, 4 Jul 2023 12:45:54 +0200
Vladimir Ratnikov <vratnikov@netgate.com> wrote:
> Sorry for a long reply, sure.
>
> Stephen,
> am I right that the most concern is about a place where interrupt
> capabilities check appears for non MSI-X support?
> What if having dedicated rte_intr_cap_single analog when there's no support
> for MSI-X and just do the same(check capability, allocate interrupt vector
> etc) ?
>
>
> Regards,
> -Vladimir
With single interrupt, only link state interrupt is possible.
Does that work with igb_uio? It should, if not then yes rte_intr_cap_single
or something like that is needed.
next prev parent reply other threads:[~2023-07-04 15:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 13:40 [PATCH] eal/interrupts: Allow UIO interrupts when using igb_uio Vladimir Ratnikov
2023-06-14 16:46 ` Stephen Hemminger
2023-07-03 15:32 ` Thomas Monjalon
2023-07-04 10:45 ` Vladimir Ratnikov
2023-07-04 15:55 ` Stephen Hemminger [this message]
2023-07-04 18:19 ` Vladimir Ratnikov
2023-07-05 23:27 ` Stephen Hemminger
2023-10-31 17:17 ` Stephen Hemminger
2023-07-03 7:19 ` [EXT] " Harman Kalra
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=20230704085530.1cf47bc7@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=hkalra@marvell.com \
--cc=junfeng.guo@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=simei.su@intel.com \
--cc=thomas@monjalon.net \
--cc=vratnikov@netgate.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.