From: Jay Rolette <rolette@infiniteio.com>
To: "EaseTheWorld Mr." <easetheworld@gmail.com>
Cc: DPDK <dev@dpdk.org>
Subject: Re: [dpdk-dev] KNI example with pcap file
Date: Tue, 28 Jul 2015 07:05:53 -0500 [thread overview]
Message-ID: <CADNuJVp7_vstYXk1Ly0qZkPKQV0D8JW08DRBA76iTBMz5w-=6A@mail.gmail.com> (raw)
In-Reply-To: <CAJzQz-HyoOrN3UuuNW50C8TiuFrYVAM5eGdzq3+s-V_2U5ywbA@mail.gmail.com>
Maybe I just haven't had enough caffeine this morning yet, but why would
you add IP reassembly to KNI? If packets are going through KNI, they
already have IP reassembly via the normal Linux networking stack...
Jay
On Mon, Jul 27, 2015 at 8:55 PM, EaseTheWorld Mr. <easetheworld@gmail.com>
wrote:
> Hello. I'm a DPDK newbie, playing with KNI.
>
> I have a packet analysis application like tshark,
> which receives packets from network interface or pcap file.
>
> My plan with KNI is
> 1) Performance improvement without modifying my program
> 2) Add ip_reassembly, acl to kni example.
> (rte_eth_rx_burst -> ip_reassembly, acl -> rte_kni_tx_burst)
>
> If input is network interface, I think the plan is fine.
> but if input is pcap file, is it possible?
> Should I use vdev or something?
>
prev parent reply other threads:[~2015-07-28 12:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 1:55 EaseTheWorld Mr.
2015-07-28 12:05 ` Jay Rolette [this message]
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='CADNuJVp7_vstYXk1Ly0qZkPKQV0D8JW08DRBA76iTBMz5w-=6A@mail.gmail.com' \
--to=rolette@infiniteio.com \
--cc=dev@dpdk.org \
--cc=easetheworld@gmail.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).