From: Antti Kantee <pooka-X3B1VOXEql0@public.gmane.org>
To: Adeel Amin <adeel_amin-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
Cc: "dev-VfR2kkLFssw@public.gmane.org" <dev-VfR2kkLFssw@public.gmane.org>
Subject: Re: DPDK on bare-metal machine
Date: Wed, 19 Jun 2013 10:28:23 +0200 [thread overview]
Message-ID: <51C16BA7.4060001@iki.fi> (raw)
In-Reply-To: <BAY177-W752C60F73448CB913E422F28D0-MsuGFMq8XAE@public.gmane.org>
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
next prev parent reply other threads:[~2013-06-19 8:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BAY177-W41B0EB5E47C4EE7099BDCF28D0@phx.gbl>
[not found] ` <BAY177-W41B0EB5E47C4EE7099BDCF28D0-MsuGFMq8XAE@public.gmane.org>
2013-06-19 7:20 ` DPDK on bare-metal machine Adeel Amin
[not found] ` <BAY177-W752C60F73448CB913E422F28D0-MsuGFMq8XAE@public.gmane.org>
2013-06-19 8:28 ` Antti Kantee [this message]
[not found] ` <51C16BA7.4060001-X3B1VOXEql0@public.gmane.org>
2013-06-19 8:34 ` Jia.Sui(贾睢)
[not found] ` <581E2E1085FAEF45B48CF8A139824CF804E5D6D419-vBGlDtGOlKBBva6MZ6yAsJWt57iikwTfrKKpfKFFTNI@public.gmane.org>
2013-06-19 14:57 ` Stephen Hemminger
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=51C16BA7.4060001@iki.fi \
--to=pooka-x3b1voxeql0@public.gmane.org \
--cc=adeel_amin-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.