DPDK patches and discussions
 help / color / mirror / Atom feed
From: Pavel Odintsov <pavel.odintsov@gmail.com>
To: Andrew Theurer <atheurer@redhat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Could not achieve wire speed for 40GE with any DPDK version on XL710 NIC's
Date: Mon, 29 Jun 2015 18:41:08 +0300	[thread overview]
Message-ID: <CALgsdbd__EBf+hnWxTNeNO-c8Dikyt1SM4eQQMsndSu2m-G+9w@mail.gmail.com> (raw)
In-Reply-To: <CAD5-U7TuQJsEqcrXQFaXr0=hO8gHKx_V_J+dwJw9zZ0bg4L5uw@mail.gmail.com>

Hello, Andrew!

What NIC have you used? Is it XL710?

On Mon, Jun 29, 2015 at 6:38 PM, Andrew Theurer <atheurer@redhat.com> wrote:
>
>
> On Mon, Jun 29, 2015 at 10:06 AM, Keunhong Lee <dlrmsghd@gmail.com> wrote:
>>
>> I have not used XL710 or i40e.
>> I have no opinion for those NICs.
>>
>> Keunhong.
>>
>> 2015-06-29 15:59 GMT+09:00 Pavel Odintsov <pavel.odintsov@gmail.com>:
>>
>> > Hello!
>> >
>> > Lee, thank you so much for sharing your experience! What do you think
>> > about 40GE version of 82599?
>> >
>> > On Mon, Jun 29, 2015 at 2:35 AM, Keunhong Lee <dlrmsghd@gmail.com>
>> > wrote:
>> > > DISCLAIMER: This information is not verified. This is truly my
>> > > personal
>> > > opinion.
>> > >
>> > > As I know, intel 82599 is the only 10G NIC which supports line rate
>> > > with
>> > > minimum sized packets (64 byte).
>> > > According to our internal tests, Mellanox's 40G NICs even support less
>> > than
>> > > 30Mpps.
>> > > I think 40 Mpps is the hardware capacity.
>
>
> This is approximately what I see as well.
>
>>
>> > >
>> > > Keunhong.
>> > >
>> > >
>> > >
>> > > 2015-06-28 19:34 GMT+09:00 Pavel Odintsov <pavel.odintsov@gmail.com>:
>> > >>
>> > >> Hello, folks!
>> > >>
>> > >> We have execute bunch of tests for receive data with Intel XL710 40GE
>> > >> NIC. We want to achieve wire speed on this platform for traffic
>> > >> capture.
>> > >>
>> > >> But we definitely can't do it. We tried with different versions of
>> > >> DPDK: 1.4, 1.6, 1.8, 2.0. And have not success.
>> > >>
>> > >> We achieved only 40Mpps and could do more.
>> > >>
>> > >> Could anybody help us with this issue? Looks like this NIC's could
>> > >> not
>> > >> work on wire speed :(
>> > >>
>> > >> Platform: Intel Xeon E5 e5 2670 + XL 710.
>> > >>
>> > >> --
>> > >> Sincerely yours, Pavel Odintsov
>> > >
>> > >
>> >
>> >
>> >
>> > --
>> > Sincerely yours, Pavel Odintsov
>> >
>
> -Andrew
>
>



-- 
Sincerely yours, Pavel Odintsov

  reply	other threads:[~2015-06-29 15:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-28 10:34 Pavel Odintsov
2015-06-28 23:35 ` Keunhong Lee
2015-06-29  6:59   ` Pavel Odintsov
2015-06-29 15:06     ` Keunhong Lee
2015-06-29 15:38       ` Andrew Theurer
2015-06-29 15:41         ` Pavel Odintsov [this message]
2015-07-01 12:06           ` Vladimir Medvedkin
2015-07-01 12:44             ` Pavel Odintsov
2015-07-01 12:59               ` Bruce Richardson
2015-07-01 13:05                 ` Pavel Odintsov
2015-07-01 13:40                   ` Vladimir Medvedkin
2015-07-01 14:22                     ` Anuj Kalia
2015-07-01 17:32                       ` Vladimir Medvedkin
2015-07-01 18:01                         ` Anuj Kalia
2015-07-03  8:35                           ` Pavel Odintsov

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=CALgsdbd__EBf+hnWxTNeNO-c8Dikyt1SM4eQQMsndSu2m-G+9w@mail.gmail.com \
    --to=pavel.odintsov@gmail.com \
    --cc=atheurer@redhat.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).