Hello Slava,
I confirm that the patch http://git.dpdk.org/dpdk/commit/?id=f66323717e
has resolved this issue.
I have tested that after applying the patch, the problem no longer occurs.
With best regards,
Mário
On 07/03/2023 10:37, Jan Viktorin wrote:
Hello all,
Mario (CC) will look at this.
nding: support flow API")
Cc: ma...@mellanox.com
Signed-off-by: Mário Kuka
---
drivers/net/bonding/rte_eth_bond_flow.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/net/bonding/rte_eth_bond_flow.c
b/drivers/net/bonding/rte_eth_bond_flow.c
index 71a91675f7..5d0be5caf5 10
how to achieve full throughput would be
greatly appreciated.
Thank you,
Mário Kuka
smime.p7s
Description: S/MIME Cryptographic Signature
:22, Kozlyuk wrote:
Hi Mário,
2024-06-19 08:45 (UTC+0200), Mário Kuka:
Hello,
I want to use hairpin queues to forward high priority traffic (such as
LACP).
My goal is to ensure that this traffic is not dropped in case the
software pipeline is overwhelmed.
But during testing with dpdk-testpmd I
t are
shared between the hairpin and CPU queues?
Any guidance or suggestions on how to achieve this would be greatly
appreciated.
Mário
On 27/06/2024 13:42, Mário Kuka wrote:
Hi Dmitry,
Thank you for your helpful reply.
Try enabling "Explicit Tx rule" mode if possible.
I was able
avoid this problem, we can split the iovec buffer into smaller
chunks with a maximum size of IOV_MAX and write them sequentially by
calling the writev() repeatedly.
Fixes: 8d23ce8f5ee9 ("pcapng: add new library for writing pcapng files")
Cc: step...@networkplumber.org
Signed-off-by:
our cases is to copy the packets into a
separate buffer and the process of writing to the file is done in some
slow path, for example by writing in a separate thread or at the end of
the application, where we don't mind the limitation of the typically
slow speed of the storage medium.
Mário
: 8d23ce8f5ee9 ("pcapng: add new library for writing pcapng files")
Cc: step...@networkplumber.org
Signed-off-by: Mário Kuka
---
app/test/test_pcapng.c | 42 +++-
lib/pcapng/rte_pcapng.c | 47 -
2 files changed, 64 inserti
writev(), and if we get a partial write, we need to call the
writev() function again on any ivo buffers that were not written or
were written partially.
Fixes: 8d23ce8f5ee9 ("pcapng: add new library for writing pcapng files")
Cc: step...@networkplumber.org
Signed-off-by: Mário Kuka
where there's a risk that it won't write all the packets or that the
file will
by corrupted due to a partial write and still not even let me know about
it?
On 29/07/2022 18:00, Stephen Hemminger wrote:
On Fri, 29 Jul 2022 09:18:41 +0200
Mário Kuka wrote:
+pcapng_writev(int fd, stru
ation. if I did something wrong, let me know.
The problem of partial writig is addressed in the second patch [PATCH v2
2/2]
On 29/07/2022 17:58, Stephen Hemminger wrote:
On Fri, 29 Jul 2022 09:18:39 +0200
Mário Kuka wrote:
This patchset contains fixes for some issues that occur when writ
: 8d23ce8f5ee9 ("pcapng: add new library for writing pcapng files")
Cc: step...@networkplumber.org
Signed-off-by: Mário Kuka
---
v3:
* Remove unwanted changes to check for partial writes from the writev().
app/test/test_pcapng.c | 42 +++-
lib/pcapng/rte_pca
hypothetical case, can't see why it needs to be
addressed.
OK, I'm sending patch v3 which only fixes the IVO_MAX limit issue.
I've removed the changes related to the partial write check.
On 29/07/2022 20:14, Stephen Hemminger wrote:
On Fri, 29 Jul 2022 19:08:41 +0200
Mário Kuka
13 matches
Mail list logo