From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>
Subject: [dpdk-dev] unimplemented API heads-up notice
Date: Fri, 28 Dec 2018 16:18:06 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB977258010D8BF5C2@IRSMSX106.ger.corp.intel.com> (raw)
Hi everyone,
As you probably know, all un-implemented API inside DPDK
planned to be deprecated in 19.05 and removed in 19.08.
For more details, please refer to:
https://mails.dpdk.org/archives/dev/2018-November/118697.html
Below is the list (probably incomplete) of currently un-implemented API.
If you are aware of some extra unimplemented API that is not in that list,
or you believe that something was added into the list by mistake,
please reply to that message.
Happy NY :)
Konstantin
1) rte_security
a) RTE_SECURITY_ACTION_TYPE_INLINE_PROTOCOL
b) RTE_SECURITY_RX_HW_TRAILER_OFFLOAD, RTE_SECURITY_TX_HW_TRAILER_OFFLOAD
c) rte_security_ops methods:
- get_userdata
- session_update
- session_stats_get (and rte_security_stats)
2) rte_ethdev
a) RTE_ETH_EVENT_IPSEC_*
b) rx offloads:
- DEV_RX_OFFLOAD_SCTP_CKSUM
- DEV_RX_OFFLOAD_OUTER_UDP_CKSUM
- DEV_RX_OFFLOAD_HEADER_SPLIT
- DEV_RX_OFFLOAD_MACSEC_STRIP
3) rte_mbuf
a) rte_mbuf.inner_esp_next_proto
b) RTE_PTYPE_TUNNEL_ESP
4) rte_bbdev
a) rte_bbdev_ops methods:
- setup_queues
- intr_enable
- start
- stop
- close
- stats_get
- stats_reset
- queue_start
- queue_stop
- queue_intr_enable
- queue_intr_disable
next reply other threads:[~2018-12-28 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-28 16:18 Ananyev, Konstantin [this message]
2019-08-05 14:30 ` Thomas Monjalon
2019-12-16 11:01 ` 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=2601191342CEEE43887BDE71AB977258010D8BF5C2@IRSMSX106.ger.corp.intel.com \
--to=konstantin.ananyev@intel.com \
--cc=dev@dpdk.org \
--cc=techboard@dpdk.org \
/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).