From: Stephen Hemminger <stephen@networkplumber.org>
To: Nulik Nol <nuliknol@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] using dpdk without glibc
Date: Sun, 23 Feb 2014 22:11:32 -0800 [thread overview]
Message-ID: <CAOaVG17kWw1nex5CxnfkHsmUs6PJapU4JhHeVFcPZ5TF5UnNug@mail.gmail.com> (raw)
In-Reply-To: <CAHO6xe8aQw=DDdTMp02fWFNLCCcw01hC2R0yr-PjvP+EVTVyXA@mail.gmail.com>
If the restriction is size based, have you looked at the smaller libc
variants used in embedded world?
If the restriction is a legal issue, you need to find a different lawyer...
On Sun, Feb 23, 2014 at 9:48 AM, Nulik Nol <nuliknol@gmail.com> wrote:
> Hi,
> I need to develop an application to forward packets, but it must not
> use GLIBC. It will not have malloc(), printf() and other functions
> except syscalls. What files should I copy from DPDK distribution that
> would allow me to manage the rings ? Is this doable or it will require
> rewriting all the code, and probably I should write my own light DPDK
> for this purpose ?
>
> Thanks in advance
> Nulik
prev parent reply other threads:[~2014-02-24 6:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-23 17:48 Nulik Nol
2014-02-23 20:33 ` Thomas Monjalon
2014-02-24 6:11 ` Stephen Hemminger [this message]
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=CAOaVG17kWw1nex5CxnfkHsmUs6PJapU4JhHeVFcPZ5TF5UnNug@mail.gmail.com \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=nuliknol@gmail.com \
/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).