From: Victor Boudon <vctrhb@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Dealing with pcaps
Date: Fri, 6 May 2016 01:41:38 +0400 [thread overview]
Message-ID: <CAP9v+dTu=_Y2Faqfdv_G479w7KXr=LWDcKi8DT1Kf8rcA1Hjfg@mail.gmail.com> (raw)
Hi,
I'm trying to build an application based on dpdk, but I'm a little lost,
and I
feel like I'm not in the traditional use case:
The idea is that i can have pcaps that a are "dropped" into my application.
What I was thinking of doing:
Build a new driver based on the one in net/pcap. It will read on a queue:
"what pcap should I read", and send the packets through the rx_queue.
- How does the threading model works ? For what I understand, the driver is
a
"producer", that push the datas to worker thought the rx_queue.
- Can I add add additional metadata for the packet into the rx_queue ? Stuff
like a pcapid, and the offset of the packet in the pcap.
- Can I detect "are all packet processed" and aggregate statistics based on
that
?
- In which case should I use one or multiple rx_queues ?
- Should I implement the tx_queues parts, event if I'm not going to use this
driver for dumping ?
Thanks,
Victor
next reply other threads:[~2016-05-05 21:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 21:41 Victor Boudon [this message]
2016-05-06 11:14 ` Upendra Pathrikar
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='CAP9v+dTu=_Y2Faqfdv_G479w7KXr=LWDcKi8DT1Kf8rcA1Hjfg@mail.gmail.com' \
--to=vctrhb@gmail.com \
--cc=users@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).