From: Daniel Kan <dan@nyansa.com>
To: Prashant Upadhyaya <prashant.upadhyaya@aricent.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Query about this NIC
Date: Thu, 9 Jan 2014 10:54:28 -0800 [thread overview]
Message-ID: <C93A9C45-C4A7-4DD6-ABAF-4A58903A3C61@nyansa.com> (raw)
In-Reply-To: <C7CE7EEF248E2B48BBA63D0ABEEE700C5A21DC97E1@GUREXMB01.ASIAN.AD.ARICENT.COM>
I’m using X520-DA2 Server Adapter E10G42BTDA PCIe Dual-Port 2xSFP+ to evaluate DPDK. It works fine as far as i can tell.
Dan
On Jan 9, 2014, at 8:06 AM, Prashant Upadhyaya <prashant.upadhyaya@aricent.com> wrote:
> Hi,
>
> No, I have not used X520-T2 before.
>
> If anybody on the list has used the above successfully, please advise.
>
> Jayant, I will await your advice.
>
> Regards
> -Prashant
>
>
> -----Original Message-----
> From: Jayakumar, Muthurajan [mailto:muthurajan.jayakumar@intel.com]
> Sent: Thursday, January 09, 2014 9:32 PM
> To: Prashant Upadhyaya; dev@dpdk.org
> Subject: RE: Query about this NIC
>
> Hi Prashant,
> Thanks for using Intel DPDK.
> Intel DPDK supports X520-T2 (previously code named "Iron Pond")
>
> Will find out the differences between X520-T2 and X520-DA2 Server Adapter E10G42BTDA PCIe Dual-Port 2xSFP+ Copper 10GSFP+Cu Low-Profile
>
> BTW, have you used X520-T2?
>
> Thank you,
> M Jay
>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Prashant Upadhyaya
> Sent: Thursday, January 09, 2014 7:39 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] Query about this NIC
>
> Hi,
>
> Would the following NIC work with DPDK -
>
> Intel 10-Gigabit Ethernet X520-DA2 Server Adapter E10G42BTDA PCIe Dual-Port 2xSFP+ Copper 10GSFP+Cu Low-Profile
>
> Regards
> -Prashant
>
>
>
>
>
> ===============================================================================
> Please refer to http://www.aricent.com/legal/email_disclaimer.html
> for important disclosures regarding this electronic communication.
> ===============================================================================
>
>
>
>
> ===============================================================================
> Please refer to http://www.aricent.com/legal/email_disclaimer.html
> for important disclosures regarding this electronic communication.
> ===============================================================================
prev parent reply other threads:[~2014-01-09 18:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 15:38 Prashant Upadhyaya
2014-01-09 16:01 ` Jayakumar, Muthurajan
2014-01-09 16:06 ` Prashant Upadhyaya
2014-01-09 16:09 ` Jayakumar, Muthurajan
2014-01-09 16:31 ` Jayakumar, Muthurajan
2014-01-09 16:33 ` Schumm, Ken
2014-01-09 16:46 ` Jayakumar, Muthurajan
2014-01-09 18:54 ` Daniel Kan [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=C93A9C45-C4A7-4DD6-ABAF-4A58903A3C61@nyansa.com \
--to=dan@nyansa.com \
--cc=dev@dpdk.org \
--cc=prashant.upadhyaya@aricent.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).