DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Nulik Nol <nuliknol@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] using dpdk without glibc
Date: Sun, 23 Feb 2014 21:33:53 +0100	[thread overview]
Message-ID: <2279963.a9N1cjkmyL@x220> (raw)
In-Reply-To: <CAHO6xe8aQw=DDdTMp02fWFNLCCcw01hC2R0yr-PjvP+EVTVyXA@mail.gmail.com>

Hi,

23/02/2014 11:48, Nulik Nol :
> 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 ?

It seems a big challenge.
I think you should be more precise describing the libraries you need. Do you 
need only rings ? For which PMD ?

By the way, what's wrong with glibc ?

-- 
Thomas

  reply	other threads:[~2014-02-23 20:32 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 [this message]
2014-02-24  6:11 ` 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=2279963.a9N1cjkmyL@x220 \
    --to=thomas.monjalon@6wind.com \
    --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).