From: "François-Frédéric Ozog" <ff@ozog.com>
To: "'Sambath Kumar Balasubramanian'" <sambath.balasubramanian@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Question on the Ring Library
Date: Wed, 4 Dec 2013 21:02:32 +0100 [thread overview]
Message-ID: <03ee01cef12b$c56d85a0$504890e0$@com> (raw)
In-Reply-To: <CAPrcauMiBS=T8p9bd1w9_DsGoke7VY2xk=fhDXvPf_YEMrzVHQ@mail.gmail.com>
You are welcome !
Even if you insert packets in batch into a fifo, the mutex is still
unpredictable. If one pthread_lock costs 1ms, you are going to lose packets,
regardless of the number of RSS queues and ring sizes
Batching comes with
another issue: need to flush a batch after a certain timeout if you do not
have packets. Userland timer resolution is such that you are introducing
port to port latency quite a lot: DPDK native, you can manage to get a 2µs
latency (including PCI express), while with batch it may be 1ms
You may
find smarter algorithms but still you will be an order of magnitude higher
than DPDK.
Hope this helps.
François-Frédéric
De : Sambath Kumar Balasubramanian
[mailto:sambath.balasubramanian@gmail.com]
Envoyé : mercredi 4 décembre 2013 15:01
À : François-Frédéric Ozog
Cc : dev@dpdk.org
Objet : Re: [dpdk-dev] Question on the Ring Library
Thanks François-Frédéric. That puts real good perspective on the cost for
the vent assuming each packet in the fast will result
in an event. If event rate is orders of magnitude less than the packet rate,
then I guess we can still achieve 10G since the "extra cost" will be in the
event thread and not in the fast path thread.
Regards,
Sambath
next prev parent reply other threads:[~2013-12-04 20:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 11:46 Sambath Kumar Balasubramanian
2013-12-04 13:47 ` François-Frédéric Ozog
2013-12-04 14:00 ` Sambath Kumar Balasubramanian
2013-12-04 20:02 ` François-Frédéric Ozog [this message]
2013-12-04 21:49 ` Sambath Kumar Balasubramanian
2013-12-04 21:25 ` Stephen Hemminger
2013-12-04 21:47 ` Sambath Kumar Balasubramanian
2013-12-04 21:51 ` Stephen Hemminger
2013-12-04 21:58 ` Sambath Kumar Balasubramanian
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='03ee01cef12b$c56d85a0$504890e0$@com' \
--to=ff@ozog.com \
--cc=dev@dpdk.org \
--cc=sambath.balasubramanian@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).