From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: DPDK on bare-metal machine Date: Wed, 19 Jun 2013 07:57:17 -0700 Message-ID: <20130619075717.18a099fb@nehalam.linuxnetplumber.net> References: <51C16BA7.4060001@iki.fi> <581E2E1085FAEF45B48CF8A139824CF804E5D6D419@ACNMAIL1.ACN.ADVANTECH.CORP> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "dev-VfR2kkLFssw@public.gmane.org" To: =?utf-8?B?SmlhLlN1aQ==?=(=?utf-8?B?6LS+552i?=) Return-path: In-Reply-To: <581E2E1085FAEF45B48CF8A139824CF804E5D6D419-vBGlDtGOlKBBva6MZ6yAsJWt57iikwTfrKKpfKFFTNI@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" 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?