From: BYEONG-GI KIM <kimbyeonggi@gmail.com>
To: "Cao, Min" <min.cao@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] DPDK supported processor
Date: Fri, 22 Aug 2014 14:34:46 +0900 [thread overview]
Message-ID: <CAEHt_JZ+tB3MD+X7qmKhgc9Qkqo6r0j9OBtt0DtRO4Ys6GcS2Q@mail.gmail.com> (raw)
In-Reply-To: <B6059B2012717B4390714544B1F509E110D59B4A@SHSMSX103.ccr.corp.intel.com>
Dear Cao Min
Thank you for the information.
Best regards
Byeong-Gi KIM
2014-08-22 14:30 GMT+09:00 Cao, Min <min.cao@intel.com>:
> Hi Byeong-Gi KIM,
>
> We tested with platform as below. Pls take information below as reference.
>
> Cpu: Genuine Intel(R) CPU 4000 @ 2.41GHz
> NIC: Niantic 82599
> Bios: EDVLCRB1.86B.0008.R00.1303061138
> OS: 3.4.18-yocto-standard(32/64 bit) or FC20
>
> We validated the test cases list below:
> pmd
> Checksum
> Ipv4frag
> Hello_world
> Flow director
> Jumboframe and scatter
> Ieee1588
> Multiprocess
> Flow control
> Whitelist
> blacklist
> vlan
>
> Regards,
> Cao Min
>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of BYEONG-GI KIM
> Sent: Thursday, August 21, 2014 2:04 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] DPDK supported processor
>
> Hello.
>
> I'm now using Intel Atom processor C2758 on the DPDK testing machines, but
> it seems not working.
>
> Which sample application would be recommended to test the NIC actually
> works well with DPDK?
>
> Best regards
>
> Byeong-Gi KIM
>
>
prev parent reply other threads:[~2014-08-22 5:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 6:04 BYEONG-GI KIM
2014-08-21 8:56 ` De Lara Guarch, Pablo
2014-08-21 9:00 ` BYEONG-GI KIM
2014-08-21 9:13 ` Masaru Oki
2014-08-21 9:15 ` BYEONG-GI KIM
[not found] ` <CADQQtgrXyb730robpVGfs0SoHF8rxu5tkxhjwgARV1XT+_eQ_g@mail.gmail.com>
2014-08-21 9:17 ` BYEONG-GI KIM
2014-08-21 9:51 ` De Lara Guarch, Pablo
2014-08-21 10:00 ` Masaru Oki
2014-08-21 10:09 ` BYEONG-GI KIM
[not found] ` <E115CCD9D858EF4F90C690B0DCB4D89721C6A575@IRSMSX103.ger.corp.intel.com>
[not found] ` <E115CCD9D858EF4F90C690B0DCB4D89721C6A583@IRSMSX103.ger.corp.intel.com>
2014-08-21 13:17 ` De Lara Guarch, Pablo
[not found] ` <CAD16F236028A64DBBC0158B1636EA4510F309FC@SHSMSX104.ccr.corp.intel.com>
[not found] ` <B6059B2012717B4390714544B1F509E110D59B4A@SHSMSX103.ccr.corp.intel.com>
2014-08-22 5:34 ` BYEONG-GI KIM [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=CAEHt_JZ+tB3MD+X7qmKhgc9Qkqo6r0j9OBtt0DtRO4Ys6GcS2Q@mail.gmail.com \
--to=kimbyeonggi@gmail.com \
--cc=dev@dpdk.org \
--cc=min.cao@intel.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).