From: Bruce Richardson <bruce.richardson@intel.com>
To: Panu Matilainen <pmatilai@redhat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] 2.3 Roadmap
Date: Tue, 1 Dec 2015 15:19:41 +0000 [thread overview]
Message-ID: <20151201151941.GA33120@bricha3-MOBL3> (raw)
In-Reply-To: <565DB580.9090209@redhat.com>
On Tue, Dec 01, 2015 at 04:58:08PM +0200, Panu Matilainen wrote:
> On 12/01/2015 04:48 PM, Vincent JARDIN wrote:
> >On 01/12/2015 15:27, Panu Matilainen wrote:
> >>The problem with that (unless I'm missing something here) is that KNI
> >>requires using out-of-tree kernel modules which makes it pretty much a
> >>non-option for distros.
> >
> >It works fine with some distros. I do not think it should be an argument.
>
> Its not a question of *working*, its that out-of-tree kernel modules are
> considered unsupportable by the kernel people. So relying on KNI would make
> the otherwise important and desireable tcpdump feature non-existent on at
> least Fedora and RHEL where such modules are practically outright banned by
> distro policies.
>
> - Panu -
Yes, KNI is a bit of a problem right now in that way.
How about a solution which is just based around the idea of setting up a generic
port mirroring callback? Hopefully in the future we can get KNI exposed as a PMD,
and we already have a ring PMD, and could possibly do a generic file/fifo PMD.
Between the 3, we could then have multiple options for intercepting traffic
going in/out of an app. The callback would just have to copy the traffic to the
selected interface before returning it to the app as normal?
/Bruce
next prev parent reply other threads:[~2015-12-01 15:19 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 20:50 O'Driscoll, Tim
2015-11-30 21:50 ` Thomas Monjalon
2015-11-30 22:19 ` Dave Neary
2015-12-01 11:57 ` O'Driscoll, Tim
2015-11-30 22:30 ` Hobywan Kenoby
2015-12-01 11:52 ` O'Driscoll, Tim
2015-11-30 22:53 ` Kyle Larose
2015-12-01 1:16 ` Stephen Hemminger
2015-12-01 10:03 ` Bruce Richardson
2015-12-01 11:26 ` Yoshinobu Inoue
2015-12-01 11:58 ` Bruce Richardson
2015-12-01 13:42 ` Matthew Hall
2015-12-01 14:45 ` Kyle Larose
2015-12-01 19:28 ` Matthew Hall
2015-12-02 0:53 ` Yoshinobu Inoue
2015-12-01 14:27 ` Panu Matilainen
2015-12-01 14:48 ` Vincent JARDIN
2015-12-01 14:58 ` Panu Matilainen
2015-12-01 15:16 ` Christian Ehrhardt
2015-12-01 15:19 ` Bruce Richardson [this message]
2015-12-01 15:31 ` Aaron Conole
2015-12-01 15:54 ` Richardson, Bruce
2015-12-02 1:38 ` Wiles, Keith
2015-12-02 2:42 ` Matthew Hall
2015-12-01 19:32 ` Matthew Hall
2015-12-02 11:24 ` Neil Horman
2015-12-01 12:59 ` Matthew Hall
2015-12-01 13:16 ` O'Driscoll, Tim
2015-12-01 13:44 ` Matthew Hall
2015-12-01 13:57 ` Bruce Richardson
2015-12-01 19:49 ` Matthew Hall
2015-12-02 12:35 ` Bruce Richardson
2015-12-02 15:47 ` Matthew Hall
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=20151201151941.GA33120@bricha3-MOBL3 \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=pmatilai@redhat.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).