This commit adds the E610 MAC type to the filter support check.
Fixes: 962549bb27c7 ("net/ixgbe: move MAC type check macros")
Cc: sta...@dpdk.org
Signed-off-by: Kaiwen Deng
---
drivers/net/intel/ixgbe/ixgbe_ethdev.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net
From: Changqing Li
To support Y2038 issue, for 32bit system, -D_TIME_BITS=64 is passed to
gcc, struct timespec time->tv_sec is 64bit, but size_t is 32bits, so
dpdk will compile failed with error:
"../git/lib/ethdev/ethdev_trace.h: In function
'rte_eth_trace_timesync_write_time':
../git/lib/eal/in
22/04/2025 07:14, kirankum...@marvell.com:
> From: Kiran Kumar K
>
> On supporting hardware, RoCEv2 header can be used to
> perform RSS in the ingress path.
Do you mean IB BTH?
It would be good to adopt a unique name between RSS and flow matching:
RTE_FLOW_ITEM_TYPE_IB_BTH
22/04/2025 07:53, kirankum...@marvell.com:
> Add support for the following OpenFlow-defined action.
>
> RTE_FLOW_ACTION_TYPE_OF_POP_ETAG: Pop E-tag from the packet.
I'm not sure about adding such action.
There is a more generic which should cover it:
RTE_FLOW_ACTION_TYPE_MODIFY_FIELD
The
Hi Thomas,
This is very helpful. I've drafted a test plan that I believe will
work best to cover these attributes. My plan is to submit
incrementally larger tests as I go, to avoid the issues I've had in
the past when trying to write one monolithic suite that covers
everything. I will likely write
Greetings,
Last week on April 16th, there was a disruption with the credentials for
the github robot's email reporting. Patches were submitted to github,
but the emails that were supposed to report status did not get sent out.
The issue has been resolved as of April 22nd. If you see a series wi
From: Edwin Brossette
rx_buf_size is computed at 2 different places: in qede_rx_queue_setup()
and in qede_set_mtu().
In qede_rx_queue_setup(), it is initialized with mtu + RTE_ETHER_HDR_LEN
and QEDE_ETH_OVERHEAD is added to it in qede_calc_rx_buf_size().
In qede_set_mtu(), it is initialized wit
From: Edwin Brossette
When the MTU configured is lower than maximum mbuf size (all packet data
can be stored in a single mbuf), then rx buffer size is configured with
MTU + some overhead. A flooring is applied to this value to align it,
meaning its actual value is going to be lower than expected.
From: Edwin Brossette
This reverts commit d8ded501e05ce879f27f0ed1df7721a88b737e25.
The maximum length for Rx packets computed in qede_rx_queue_setup()
takes Ethernet CRC into account. This is not consistent with the value
computed in qede_set_mtu(). RTE_ETHER_CRC_LEN should not be added to
max_
From: Edwin Brossette
As per the rte_mbuf API: the driver is responsible of initializing all
the required fields. This is not done at qede alloc, meaning there can
be garbage data in mbufs memory, although this garbage data should be
overwritten when the mbufs are used. Since a sanity check is do
From: Didier Pallard
In tunnel case, L3 bad checksum is properly setting
RTE_MBUF_F_RX_OUTER_IP_CKSUM_BAD while all other flags are set in inner
part of offload flags, this can cause both L4 flags BAD and GOOD to be set
in inner offloads when a tunnel packet is processed, changing these flags
to
Hello,
I have several issues to report concerning the qede pmd as well as
potential solutions for them. Most of them have to do with configuring the
MTU.
== Abort on mtu change ===
First, the qede_assign_rxtx_handlers() seems to be working wrong since an
API change in the rte_eth
Hello,
The GB meeting has now been rescheduled, meaning that we can reclaim our
timeslot. Moving the DTS meeting on Thursday back to 13:00 UTC. Thanks.
On Mon, Apr 21, 2025 at 2:24 PM Patrick Robb wrote:
> Hello,
>
> There is a conflict between this Thursday's DPDK governing board meeting
> and
Observation.
Two instances of testpmd. Only one report shows correct stats when you run
16 queues on RX with the default RSS config.
i.e rss-ip , rss-udp etc. You only see the counter for a single queue.
How I know I took last report on first intestine test-pmd at the end of
run, take all bytes
From: Changqing Li
To support Y2038 issue, for 32bit system, -D_TIME_BITS=64 is passed to
gcc, struct timespec time->tv_sec is 64bit, but size_t is 32bits, so
dpdk will compile failed with error:
../git/lib/ethdev/ethdev_trace.h: In function
'rte_eth_trace_timesync_write_time':
../git/lib/eal/in
From: Changqing Li
To support Y2038 issue, for 32bit system, -D_TIME_BITS=64 is passed to
gcc, struct timespec time->tv_sec is 64bit, but size_t is 32bits, so
dpdk will compile failed with error:
../git/lib/ethdev/ethdev_trace.h: In function
'rte_eth_trace_timesync_write_time':
../git/lib/eal/in
Hi,
Please withdraw this patch. It was submitted prematurely as the fix for the
issue is already included here
https://mails.dpdk.org/archives/stable/2025-February/051616.html
Apologies for the confusion.
Thanks,
Patryk Ochal
17 matches
Mail list logo
