From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.cs.hut.fi (mail.cs.hut.fi [130.233.192.7]) by dpdk.org (Postfix) with ESMTP id 2D86D232 for ; Wed, 19 Jun 2013 10:28:13 +0200 (CEST) Received: from [IPv6:::1] (hutcs.cs.hut.fi [130.233.192.10]) by mail.cs.hut.fi (Postfix) with ESMTPS id CBAE9308BD7; Wed, 19 Jun 2013 11:28:24 +0300 (EEST) Message-ID: <51C16BA7.4060001@iki.fi> Date: Wed, 19 Jun 2013 10:28:23 +0200 From: Antti Kantee MIME-Version: 1.0 To: Adeel Amin References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] DPDK on bare-metal machine X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jun 2013 08:28:13 -0000 On 19.06.2013 09:20, Adeel Amin wrote: > Hello, > > Can anyone tell me that how I can run a DPDK application as a bare-metal (i.e. without Linux support). I've tried to run rump kernel TCP/IP stack by Antti Kantee but I'm unable to figure out that how I'll be using it to run stand alone on x86 CPU. Currently I'm running the rump kernel as a Linux application. Hi, As far as I've been able to gather, the open source version of DPDK does not include bare-metal support. However, I'm not very knowledgeable on DPDK, especially on code which I cannot read myself, so maybe someone else can answer that better. I do know something about rump kernels, though. One of main future use cases I see is indeed to have them run on bare metal and therefore allow to continue use essential kernel-only implemented features but still get rid of the prehistoric OS overhead layer. I have good reason to suspect that running rump kernels this would be easy, but as far as I know, no one has done the necessary work, at least not for x86. Unless the bare-metal version of DPDK provides a suitable portability layer, you'd be looking at implementing the rump kernel hypervisor interface for bare metal (or bare firmware ?-). In such a case, you might find using that using also the device layer from a rump kernel is the shortest path to initial success, with migration to DPDK only after reaching stability in that setup. But, that's getting quite off-topic for this list. Contact me off-list if you are serious about putting effort into the above. - antti