ping.py has 3 cases, test_v4, test_v6 and test_tcp.
But these cases are not executed on the XDP environment.
So, it adds XDP environment, existing tests(test_v4, test_v6, and
test_tcp) are executed too on the below XDP environment.
So, it adds XDP cases.
1. xdp-generic + single-buffer
2. xdp-generi
When devmem socket is closed, netdev_rx_queue_restart() is called to
reset queue by the net_devmem_unbind_dmabuf(). But callback may return
-ENETDOWN if the interface is down because queues are already freed
when the interface is down so queue reset is not needed.
So, it should not warn if the retu
The bnxt_rx_pkt() updates ip_summed value at the end if checksum offload
is enabled.
When the XDP-MB program is attached and it returns XDP_PASS, the
bnxt_xdp_build_skb() is called to update skb_shared_info.
The main purpose of bnxt_xdp_build_skb() is to update skb_shared_info,
but it updates ip_su
When mb-xdp is set and return is XDP_PASS, packet is converted from
xdp_buff to sk_buff with xdp_update_skb_shared_info() in
bnxt_xdp_build_skb().
bnxt_xdp_build_skb() passes incorrect truesize argument to
xdp_update_skb_shared_info().
The truesize is calculated as BNXT_RX_PAGE_SIZE * sinfo->nr_fra
When a queue is restarted, it sets MRU to 0 for stopping packet flow.
MRU variable is a member of vnic_info[], the first vnic_info is default
and the second is ntuple.
Only when ntuple is enabled(ethtool -K eth0 ntuple on), vnic_info for
ntuple is allocated in init logic.
The bp->nr_vnics indicates
The bnxt_queue_mem_alloc() is called to allocate new queue memory when
a queue is restarted.
It internally accesses rx buffer descriptor corresponding to the index.
The rx buffer descriptor is allocated and set when the interface is up
and it's freed when the interface is down.
So, if queue is rest
The first fixes setting incorrect skb->truesize.
When xdp-mb prog returns XDP_PASS, skb is allocated and initialized.
Currently, The truesize is calculated as BNXT_RX_PAGE_SIZE *
sinfo->nr_frags, but sinfo->nr_frags is flushed by napi_build_skb().
So, it stores sinfo before calling napi_build_skb()
On Thu, 06 Mar 2025 00:09:56 +1100, David Disseldorp wrote:
> We already have a comment regarding why .data -> .init references are
> present for initramfs_test_cases[]. This allows us to suppress the
> modpost warning.
>
>
Folded, thanks!
---
Applied to the vfs-6.15.initramfs branch of the vf
On Sun, Mar 2, 2025 at 5:15 PM Sergio González Collado
wrote:
>
> The longest length of a symbol (KSYM_NAME_LEN) was increased to 512
> in the reference [1]. This patch adds kunit test suite to check the longest
> symbol length. These tests verify that the longest symbol length defined
> is suppor
ay-ci/archive/20250305/202503050109.t5ab93hx-...@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20250305/202503050109.t5ab93hx-...@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not j
On Fri, 21 Feb 2025 09:33:29 +, Catalin Marinas wrote:
> The first patch makes use of the correct terminology for synchronous and
> asynchronous errors. The second patch checks whether PROT_MTE is
> supported on hugetlb mappings before continuing with the tests. Such
> support was added in 6.13
We already have a comment regarding why .data -> .init references are
present for initramfs_test_cases[]. This allows us to suppress the
modpost warning.
Reported-by: kernel test robot
Closes:
https://lore.kernel.org/oe-kbuild-all/202503050109.t5ab93hx-...@intel.com/
Suggested-by: Stephen Rothwe
d5fea0d1a20bb2ad1eaa6dd4
> > commit: b6736cfccb582b7c016cba6cd484fbcf30d499af [205/231] initramfs_test:
> > kunit tests for initramfs unpacking
> > config: x86_64-buildonly-randconfig-002-20250304
> > (https://download.01.org/0day-ci/archive/20250305/202503050109.t5ab93hx-.
13 matches
Mail list logo