From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Alejandro Lucero <alejandro.lucero@netronome.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 2/4] nfp-uio: new uio driver for netronome nfp6000 card
Date: Wed, 21 Oct 2015 18:03:08 +0200 [thread overview]
Message-ID: <1729488.TmXe30SXlp@xps13> (raw)
In-Reply-To: <CAD+H993aWa1=fb2Dts9roLYwUwew-oa+x8zEg7MEy-kjcq5PmQ@mail.gmail.com>
2015-10-21 16:57, Alejandro Lucero:
> I understand interest for not having another UIO driver does exist. We
> could maintain an external nfp_uio by now till either we get rid of it or
> we definitely find out it is really needed. any chance to accept nfp_uio by
> now?
No, there are some work currently to get rid of igb_uio.
So there are little chances to accept nfp_uio one day.
Please take the first step of integrating your PMD without link interrupt.
Later we'll be able to discuss how to mitigate the interrupt issue.
next prev parent reply other threads:[~2015-10-21 16:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 10:45 [dpdk-dev] [PATCH v3 0/4] support for netronome nfp-6xxx card Alejandro.Lucero
2015-10-16 10:45 ` [dpdk-dev] [PATCH v3 1/4] nfp: new poll mode driver for netronome nfp6000 card Alejandro.Lucero
2015-10-16 10:45 ` [dpdk-dev] [PATCH v3 2/4] nfp-uio: new uio " Alejandro.Lucero
2015-10-21 5:24 ` David Marchand
2015-10-21 14:39 ` Alejandro Lucero
2015-10-21 15:25 ` Thomas Monjalon
2015-10-21 15:57 ` Alejandro Lucero
2015-10-21 16:03 ` Thomas Monjalon [this message]
2015-10-21 19:40 ` Alejandro Lucero
2015-10-22 11:46 ` Alejandro Lucero
2015-10-16 10:45 ` [dpdk-dev] [PATCH v3 3/4] doc: add netronome nfp6000 guide Alejandro.Lucero
2015-10-16 10:45 ` [dpdk-dev] [PATCH v3 4/4] tools: add support for nfp_uio Alejandro.Lucero
2015-10-19 19:17 ` [dpdk-dev] [PATCH v3 0/4] support for netronome nfp-6xxx card Mcnamara, John
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=1729488.TmXe30SXlp@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=alejandro.lucero@netronome.com \
--cc=dev@dpdk.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;
as well as URLs for NNTP newsgroup(s).