From: Vincent JARDIN <vincent.jardin@6wind.com>
To: sujith sankar <sujithsankar2@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Fwd: PMD for Broadcom/Emulex OCe14000 OCP Skyhawk-R
Date: Thu, 8 Mar 2018 08:20:15 +0100 [thread overview]
Message-ID: <bb8831f4-a3d5-7e92-c7be-954256b21dec@6wind.com> (raw)
In-Reply-To: <CAMTiEwdZfCUY+wunu3ry75gS4dctQ6B7DpjoxjX8vY2k_qV7ZA@mail.gmail.com>
Le 07/03/2018 à 04:56, sujith sankar a écrit :
> Is PMD for Broadcom/Emulex OCe14000 OCP Skyhawk-R available? There
> are a few documents in Broadcom's site. But could not find the source
> code of it.
Right, it has not been upstreamed. Currently, it is even deprecated at
6WIND for our new releases.
www.6wind.com/products/6windgate/6windgate-platfoarm-support/
see the NIC section.
>
> I believe 6Wind team developed the PMD for Broadcom. But what is the
> status of it? Is it freely available?
I guess you are referring to:
https://docs.broadcom.com/docs/12356248
This PMD is deprecated. We kept it only for old DPDK releases because it
relies on some specific SDK from Emulex/Skyhawk's designers! The PMD
without the SDK is useless.
>
> Tried to get some help from users alias, but could not.
> Could someone please help me with info on this?
In fact, the best option is to use AF_XDP PMD if you need to support
this Emulex/SkyhawkNIC. Please, give a try to this AF_XDP PMD. Your
benchmarks will be welcomed. I guess it is better to invest time in
improving AF_XDP PMD,
http://dpdk.org/ml/archives/dev/2018-February/091502.html
best regards,
Vincent
next prev parent reply other threads:[~2018-03-08 7:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMTiEwc_POBUSWoYZ4RiFpaydu1WYLkRf-vNX6PLrp6iaj7S-A@mail.gmail.com>
2018-03-07 3:56 ` sujith sankar
2018-03-08 7:20 ` Vincent JARDIN [this message]
2018-03-08 10:01 ` sujith sankar
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=bb8831f4-a3d5-7e92-c7be-954256b21dec@6wind.com \
--to=vincent.jardin@6wind.com \
--cc=dev@dpdk.org \
--cc=sujithsankar2@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).