From: Stephen Hemminger <stephen@networkplumber.org>
To: "Jia.Sui" <Jia.Sui@advantech.com.cn>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK on bare-metal machine
Date: Wed, 19 Jun 2013 07:57:17 -0700 [thread overview]
Message-ID: <20130619075717.18a099fb@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <581E2E1085FAEF45B48CF8A139824CF804E5D6D419@ACNMAIL1.ACN.ADVANTECH.CORP>
With latest (3.9 or later) kernels the overhead from Linux kernel is minimal and shrinking
fast. The only overhead left is the timer tick and that is being eliminated.
Of course it is easy to write slow code and use system calls and defeat the purpose of DPDK.
Has anyone experimented with making the DPDK threads marked as real-time to keep
other processes away?
next prev parent reply other threads:[~2013-06-19 14:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BAY177-W41B0EB5E47C4EE7099BDCF28D0@phx.gbl>
2013-06-19 7:20 ` Adeel Amin
2013-06-19 8:28 ` Antti Kantee
2013-06-19 8:34 ` Jia.Sui
2013-06-19 14:57 ` Stephen Hemminger [this message]
2013-06-20 5:32 ` Stephen Hemminger
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=20130619075717.18a099fb@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=Jia.Sui@advantech.com.cn \
--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).