From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Shahar Belkar <shahar.belkar@huawei.com>,
"Huwei (Xavier)" <xavier.huwei@huawei.com>,
"web@dpdk.org" <web@dpdk.org>
Cc: Linuxarm <linuxarm@huawei.com>,
"xavier_huwei@163.com" <xavier_huwei@163.com>,
"xavier.huwei@tom.com" <xavier.huwei@tom.com>,
"Zhouchang (Forest)" <forest.zhouchang@huawei.com>,
Tanya Brokhman <tanya.brokhman@huawei.com>,
Luoxianjun <luoxianjun@huawei.com>,
"Yangbaochuan (Roger, IT Chip application)" <bc.y@huawei.com>
Subject: Re: [dpdk-web] [PATCH] add Hisilicon hns3 to supported NICs
Date: Wed, 16 Oct 2019 19:44:52 +0100 [thread overview]
Message-ID: <3e9b1fb4-30f0-9ec0-fe61-db2d90104466@intel.com> (raw)
In-Reply-To: <860AA2E59AE2574D8CD34967F17D44E9F522CF@lhreml523-mbs.china.huawei.com>
On 10/15/2019 10:47 PM, Shahar Belkar wrote:
> Hi Ferruh,
>
> Thanks for this email, the hinic (IN200) should be under Huawei, you can see the info here:
> https://support.huawei.com/enterprise/en/doc/EDOC1100063073/3e7a397b/getting-to-know-the-in200
Thanks Shahar,
Are 'hns3' and 'hinic' should be documented as different vedors?
Not both of them from Huawei?
>
> Best Regards,
>
> Shahar
>
> -----Original Message-----
> From: Ferruh Yigit [mailto:ferruh.yigit@intel.com]
> Sent: Tuesday, October 15, 2019 3:44 PM
> To: Huwei (Xavier) <xavier.huwei@huawei.com>; web@dpdk.org
> Cc: Linuxarm <linuxarm@huawei.com>; xavier_huwei@163.com; xavier.huwei@tom.com; Zhouchang (Forest) <forest.zhouchang@huawei.com>; Tanya Brokhman <tanya.brokhman@huawei.com>; Shahar Belkar <shahar.belkar@huawei.com>
> Subject: Re: [PATCH] add Hisilicon hns3 to supported NICs
>
> On 10/11/2019 3:32 AM, Wei Hu (Xavier) wrote:
>> The PMD hns3 was added in DPDK 19.11.
>>
>> Signed-off-by: Wei Hu (Xavier) <xavier.huwei@huawei.com>
>> ---
>> content/supported/nics/hisilicon.md | 7 +++++++
>> 1 file changed, 7 insertions(+)
>> create mode 100644 content/supported/nics/hisilicon.md
>>
>> diff --git a/content/supported/nics/hisilicon.md b/content/supported/nics/hisilicon.md
>> new file mode 100644
>> index 0000000..a032a11
>> --- /dev/null
>> +++ b/content/supported/nics/hisilicon.md
>
> Should it be hisilicon or huawei? hinic has it as huawei. cc'ed Tanya.
>
> This part is refers the vendor, should the vendor be different for hinic & hns3?
>
>> @@ -0,0 +1,7 @@
>> ++++
>> +title = "Hisilicon"
>> +description = "hns3"
>> +hidden = true
>> ++++
>> +
>> +- [hns3](http://doc.dpdk.org/guides/nics/hns3.html) (Kunpeng 920, Kunpeng 920s)
>>
>
next prev parent reply other threads:[~2019-10-16 18:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 2:32 Wei Hu (Xavier)
2019-10-15 12:44 ` Ferruh Yigit
2019-10-15 21:47 ` Shahar Belkar
2019-10-16 18:44 ` Ferruh Yigit [this message]
2019-10-17 10:36 ` Shahar Belkar
2019-10-17 11:06 ` Wei Hu (Xavier)
2019-10-20 9:44 ` Thomas Monjalon
2019-10-23 8:08 ` Ferruh Yigit
2019-10-23 15:07 ` Thomas Monjalon
2019-10-23 18:22 ` Ferruh Yigit
2019-10-23 18:28 ` Ferruh Yigit
2019-10-23 18:49 ` Trishan de Lanerolle
-- strict thread matches above, loose matches on Subject: below --
2019-09-29 9:07 Wei Hu (Xavier)
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=3e9b1fb4-30f0-9ec0-fe61-db2d90104466@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bc.y@huawei.com \
--cc=forest.zhouchang@huawei.com \
--cc=linuxarm@huawei.com \
--cc=luoxianjun@huawei.com \
--cc=shahar.belkar@huawei.com \
--cc=tanya.brokhman@huawei.com \
--cc=web@dpdk.org \
--cc=xavier.huwei@huawei.com \
--cc=xavier.huwei@tom.com \
--cc=xavier_huwei@163.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).