From: Michael Quicquaro <michael.quicquaro@gmail.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] glibc 2.1
Date: Fri, 22 Nov 2013 10:57:45 -0500 [thread overview]
Message-ID: <CAAD-K96RoAaQObkGiHKikV75kJroHohZFYQNHjtASxOoNLFXGA@mail.gmail.com> (raw)
In-Reply-To: <59AF69C657FD0841A61C55336867B5B01A975AA5@IRSMSX103.ger.corp.intel.com>
Right, thanks. I had a little brain fart.
On Fri, Nov 22, 2013 at 4:42 AM, Richardson, Bruce <
bruce.richardson@intel.com> wrote:
> The Intel DPDK should work fine on RHEL 6.4. There should be no need to
> update your glibc, since this is subversion 12 (> 7), rather than 1.2.
> Regards,
> /Bruce
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Michael Quicquaro
> > Sent: Thursday, November 21, 2013 6:26 PM
> > To: dev@dpdk.org
> > Subject: [dpdk-dev] glibc 2.1
> >
> > Hello all,
> >
> > I have built dpdk (and pktgen-dpdk) on a couple RHEL 6.4 servers. This
> > distribution comes with glibc 2.12
> >
> > I have read that glibc 2.7 is needed for coreset() functionality. My
> testing,
> > at the moment, only requires one cpu core.
> >
> > I assume that upgrading to glibc 2.7 would probably break many of the
> > executables on this system.
> >
> > The build seemed to work fine.
> >
> > Do you think that there are any adverse effects of using a dpdk that was
> > built with glibc 2.1 in this case?
> >
> > - Mike
>
prev parent reply other threads:[~2013-11-22 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 18:25 Michael Quicquaro
2013-11-22 9:42 ` Richardson, Bruce
2013-11-22 15:57 ` Michael Quicquaro [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=CAAD-K96RoAaQObkGiHKikV75kJroHohZFYQNHjtASxOoNLFXGA@mail.gmail.com \
--to=michael.quicquaro@gmail.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.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 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).