RE: [RFC PATCH v1] net/i40e: put mempool cache out of API

2022-07-10 Thread Honnappa Nagarahalli
> > > > Refer to "i40e_tx_free_bufs_avx512", this patch puts mempool cache out > > of API to free buffers directly. There are two changes different with > > previous version: > > 1. change txep from "i40e_entry" to "i40e_vec_entry" > > 2. put cache out of "mempool_bulk" API to copy buffers into

回复: [RFC PATCH v1] net/i40e: put mempool cache out of API

2022-07-10 Thread Feifei Wang
> -邮件原件- > 发件人: Feifei Wang > 发送时间: Wednesday, July 6, 2022 7:36 PM > 收件人: 'Konstantin Ananyev' ; 'Yuying > Zhang' ; 'Beilei Xing' ; > Ruifeng Wang > 抄送: 'dev@dpdk.org' ; nd ; Honnappa > Nagarahalli ; nd ; nd > > 主题: 回复: [RFC PATCH v1] net/i40e: put mempool cache out of API > > > > >

RE: [PATCH] doc: announce marking device and driver objects as internal

2022-07-10 Thread Xia, Chenbo
Hi David, > -Original Message- > From: David Marchand > Sent: Sunday, July 10, 2022 2:18 PM > To: dev@dpdk.org; techbo...@dpdk.org > Cc: Ray Kinsella > Subject: [PATCH] doc: announce marking device and driver objects as > internal > > rte_driver and rte_device are unnecessarily exposed

Re: [PATCH v2] ip_frag: add IPv4 fragment copy packet API

2022-07-10 Thread Konstantin Ananyev
> Some NIC drivers support MBUF_FAST_FREE(Device supports optimization > for fast release of mbufs. When set application must guarantee that > per-queue all mbufs comes from the same mempool and has refcnt = 1) > offload. In order to adapt to this offload function, add this API. > Add some test da

[PATCH v3] common/mlx5: update DevX error logging

2022-07-10 Thread Gregory Etelson
Current PMD logs all DevX errors at error level. DevX interface can fail queue counters allocation on some hardware types. That is a known issue. PMD fallback to VERB API to allocate queue counters when it detects the fault. That DevX failure should not be logged as PMD error. The patch provides

Re: [PATCH] doc: announce marking device and driver objects as internal

2022-07-10 Thread Andrew Rybchenko
On 7/10/22 09:17, David Marchand wrote: rte_driver and rte_device are unnecessarily exposed in the public API/ABI. Announce that they will be made opaque in the public API and mark associated API as internal. This impacts all bus, as their driver registration mechanism will be made internal. Not