From: Stephen Hemminger <stephen@networkplumber.org>
To: Sambath Kumar Balasubramanian <sambath.balasubramanian@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Question on the Ring Library
Date: Wed, 4 Dec 2013 13:25:48 -0800 [thread overview]
Message-ID: <20131204132548.05a151fe@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <CAPrcauPLZrC5ve4ZX47de5JzT8fSDi6Za3Oe2wKKLpKNTuc6_g@mail.gmail.com>
On Wed, 4 Dec 2013 03:46:36 -0800
Sambath Kumar Balasubramanian <sambath.balasubramanian@gmail.com> wrote:
> Hi,
>
> The ring library seems to be an excellent IPC. But looking at one use
> case where the fast path code posts events to event thread for example, the
> event thread will spend some cycles polling the ring rather than waiting
> for the event. One approach could be a fast path code basically posts the
> event in the ring as is today and there is a background thread that polls
> the queues and wakes up the event threads. This is similar to Linux
> SOFTIRQs.The event threads are asynchronous. Is this a fair model to avoid
> extra polling CPU cycles by the event threads? Is there any other
> alternatives in dpdk?
>
> Regards,
> Sambath
I have in several cases combined RTE ring with use of eventfd + poll to
get wakeup
next prev parent reply other threads:[~2013-12-04 21:24 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
2013-12-04 21:49 ` Sambath Kumar Balasubramanian
2013-12-04 21:25 ` Stephen Hemminger [this message]
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=20131204132548.05a151fe@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--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).