From: "Jan Mędala" <jan@semihalf.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org, matua@amazon.com
Subject: Re: [dpdk-dev] [PATCH 0/4] DPDK polling-mode driver for Amazon Elastic Network Adapters (ENA)
Date: Fri, 29 Jan 2016 16:42:05 +0100 [thread overview]
Message-ID: <CANw_3ZdgKWicPLNLLN6CBwRkFdLg=T2y3QQxX8kr-FCmD_57ug@mail.gmail.com> (raw)
In-Reply-To: <4623588.IlxFVFWOgI@xps13>
Hello Thomas,
2016-01-28 16:40 GMT+01:00 Thomas Monjalon <thomas.monjalon@6wind.com>:
> > lib/librte_eal/linuxapp/ena_uio/ena_uio_driver.c | 276 +++
>
> Sorry the kernel module party is over.
> One day, igb_uio will be removed.
> I suggest to make a first version without interrupt support
> and work with Linux community to fix your issues.
>
Rationale to deliver UIO kernel module is based on lack of legacy INTx
interrupts in ENA device. It's operating only on MSI-X.
Currently we do not implement interrupt support (yet) in PMD, but hardware
was unable to operate under uio_generic_pci driver - probe is failing.
It might be possible to use igb_uio kmod with ENA and I will do necessary
investigation+experiments to prove that.
Could you elaborate on the topic of kernel module removal - how would it
look like, is there going to be generic PCI driver dedicated for MSI-X
devices?
Thanks,
Jan
next prev parent reply other threads:[~2016-01-29 15:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 15:20 Jan Medala
2016-01-28 15:20 ` [dpdk-dev] [PATCH 1/4] Amazon ENA UIO driver Jan Medala
2016-01-28 15:20 ` [dpdk-dev] [PATCH 2/4] Amazon ENA communication layer Jan Medala
2016-01-28 15:20 ` [dpdk-dev] [PATCH 3/4] Amazon ENA communication layer for DPDK platform Jan Medala
2016-01-28 15:20 ` [dpdk-dev] [PATCH 4/4] DPDK polling-mode driver for Amazon Elastic Network Adapters (ENA) Jan Medala
2016-01-28 15:40 ` [dpdk-dev] [PATCH 0/4] " Thomas Monjalon
2016-01-29 15:42 ` Jan Mędala [this message]
2016-01-29 16:04 ` Thomas Monjalon
2016-01-30 16:39 ` Matushevsky, Alexander
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='CANw_3ZdgKWicPLNLLN6CBwRkFdLg=T2y3QQxX8kr-FCmD_57ug@mail.gmail.com' \
--to=jan@semihalf.com \
--cc=dev@dpdk.org \
--cc=matua@amazon.com \
--cc=thomas.monjalon@6wind.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).