From: oulijun <oulijun@huawei.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev <dev@dpdk.org>, <linuxarm@openeuler.org>
Subject: [dpdk-dev] DPDK 21.05 Huawei hns3 Roadmap
Date: Tue, 23 Feb 2021 17:08:01 +0800 [thread overview]
Message-ID: <22bcc904-53c8-b353-ebd4-c03750d12830@huawei.com> (raw)
Hi，
Following are the work items of hns3 PMD planned for 21.05, Some
features are delayed to the current releases.
New features:
【1】 Add PTP(Precise Time Protocol) support
【2】 Add query optical module info by API
【3】 Support LSC(Link Status Changed) event
The LSC reporting function of the PF has been completed in
21.02. This task involves the LSC reporting function of the VF and
the LSC capability setting through the
rte_pci_drvier.drv_flags.
【4】 Implement tx_done_cleanup API
【5】 Implement Rx/Tx descriptor status API
【6】 Support runtime config for selecting Tx/Rx function
【7】 Kunpeng930 support electrical port
【8】 Kunpeng930 support flow control auto-negotiation
【9】 Kunpeng930 support for simple BD mode for Tx checksum
【10】 Kunpeng930 Support link speed configuration for PF
【11】 Support new RAS mechanism for Kunpeng930
Enhanced functionality:
【11】 Extend the DPDK stats
【12】 Extend the DPDK rte_dev_get_regs API implementation for query
more common register information
【13】 Extend outer UDP cksum offload
【14】 Rx receive function optimization for improving performance
support rxd advanced layout
support checksum simple computing and ptype optimization
【15】 Support push mode for Tx queue
bonding function：
【16】 some bonding modes support prepare API
testpmd updates：
【17】 testpmd support multi-process test
Others：
【18】 Extend for hns3 document
Thanks
Lijun Ou
next reply other threads:[~2021-02-23 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 9:08 oulijun [this message]
2021-02-28 17:44 ` Thomas Monjalon
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=22bcc904-53c8-b353-ebd4-c03750d12830@huawei.com \
--to=oulijun@huawei.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=linuxarm@openeuler.org \
--cc=thomas@monjalon.net \
/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).