From: Upendra Pathrikar <uspathrikar@gmail.com>
To: Victor Boudon <vctrhb@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Dealing with pcaps
Date: Fri, 6 May 2016 16:44:47 +0530 [thread overview]
Message-ID: <CAGSHHKfbayXc21SQZC-Cu4z9aSTcEjWhY=-eURPNtVTOww0qeQ@mail.gmail.com> (raw)
In-Reply-To: <CAP9v+dTu=_Y2Faqfdv_G479w7KXr=LWDcKi8DT1Kf8rcA1Hjfg@mail.gmail.com>
Hi Victor,
I think this page
Libpcap and Ring Based Poll Mode Drivers
http://dpdk.org/doc/guides/nics/pcap_ring.html?highlight=pcap
can help you.
On Fri, May 6, 2016 at 3:11 AM, Victor Boudon <vctrhb@gmail.com> wrote:
> 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
>
--
*Regards,Upendra Sunil PathrikarBharti School of Telecom Technology and
Management,Indian Institute of Technology, Delhi.*
prev parent reply other threads:[~2016-05-06 11:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 21:41 Victor Boudon
2016-05-06 11:14 ` Upendra Pathrikar [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='CAGSHHKfbayXc21SQZC-Cu4z9aSTcEjWhY=-eURPNtVTOww0qeQ@mail.gmail.com' \
--to=uspathrikar@gmail.com \
--cc=users@dpdk.org \
--cc=vctrhb@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).