DPDK patches and discussions
 help / color / mirror / Atom feed
From: Nulik Nol <nuliknol@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] About interrupts and packet loss
Date: Sun, 1 Sep 2013 02:01:43 -0500	[thread overview]
Message-ID: <CAHO6xe-Qy9ZQgnF8icYzxNocDX+Pfu_NfO9XtW09O0LhA6Miww@mail.gmail.com> (raw)

Hi,
I have read in a pdf document about DPDK that the driver that comes
within the DPDK distribution was modified to disable interrupt
handling. This explains why DPDK is so fast.
However , this means the app in user space must constantly watch for
new packets, so the CPU load average will be almost 100% all the time,
correct? Well, then what happens if the app executes a busy process
and at that time all RX rings get filled, will the incoming network
traffic be lost?

Thanks in advance
Nulik

             reply	other threads:[~2013-09-01  7:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-01  7:01 Nulik Nol [this message]
2013-09-02 13:25 ` Thomas Monjalon

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=CAHO6xe-Qy9ZQgnF8icYzxNocDX+Pfu_NfO9XtW09O0LhA6Miww@mail.gmail.com \
    --to=nuliknol@gmail.com \
    --cc=dev@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).