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 BE9FCB119 for ; Sat, 17 May 2014 12:05:35 +0200 (CEST) Received: from [127.0.0.1] (hutcs.cs.hut.fi [130.233.192.10]) by mail.cs.hut.fi (Postfix) with ESMTPS id F31833088BE; Sat, 17 May 2014 13:05:43 +0300 (EEST) Message-ID: <53773477.8000100@fixup.fi> Date: Sat, 17 May 2014 10:05:43 +0000 From: Antti Kantee MIME-Version: 1.0 To: daniel chapiesky , dev@dpdk.org References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] DPDK Bare Metal 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: Sat, 17 May 2014 10:05:35 -0000 Daniel, On 16/05/14 22:16, daniel chapiesky wrote: > We are interested in finding out how much we can decrease the attack surface > of our application by going full bare metal.. (i.e. sans OS). The mention > of a bare metal version of dpdk is one of the contributing factors for our > working on our prototype. > > Can you please provide any information on the dpdk bare metal version? > Such as: I don't know about _the_ bare metal version, but if I'm allowed to advertise a project I'm working on, I'll mention _a_ potential bare metal version: The goal of rump kernels (http://rumpkernel.org/) is to provide an OS quality driver stack without the OS (hence *rump* kernels). The TCP/IP stack provided by rump kernels already integrates with DPDK, and many existing POSIX-y apps "just work" on top of rump kernels in an OS-less environment. It's no stretch to imagine DPDK running on a bare metal rump kernel platform, TCP/IP optional. > 1) is it in fact - a zero OS version or is it based on a RTOS such as > those from Wind River. > > 2) Does the bare metal version only support one kind of processor family > such > as i7, or is it possible to target atom or arm with it as well? > > 3) what are the licensing terms for it? > > 4) are royalties required? Rump kernels are [based on] NetBSD, so there's support for a variety of architectures, including Intel, ARM, MIPS, etc. Everything is open source and BSD-licensed, no royalties. However, since the idea of the open source project is to provide a driver stack instead of ready-baked solutions, you have to write (or copypaste) the lowest bootstrap/machine layer yourself (*). The good news is that, speaking from experience, the required lowlevel support is a simple few-nighter. - antti *) feel free to call that development investment a licensing fee if it translates better to your finance department