gcc-13.2.0
arc allyesconfiggcc-13.2.0
arc randconfig-001-20250215gcc-13.2.0
arc randconfig-002-20250215gcc-13.2.0
arm allmodconfiggcc-14.2.0
arm allnoconfig
-20250215gcc-13.2.0
arc randconfig-002-20250215gcc-13.2.0
arm allyesconfiggcc-14.2.0
arm randconfig-001-20250215clang-15
arm randconfig-002-20250215clang-17
arm randconfig-003
allmodconfiggcc-13.2.0
arc allnoconfiggcc-14.2.0
arc allyesconfiggcc-13.2.0
arc defconfiggcc-13.2.0
arc randconfig-001-20250215gcc-13.2.0
arc randconfig-002
On Thu, Feb 13, 2025 at 08:44:52AM +0100, Jedrzej Jagielski wrote:
> E610 NICs unlike the previous devices utilizing ixgbe driver
> are notified in the case of overheating by the FW ACI event.
>
> In event of overheat when threshold is exceeded, FW suspends all
> traffic and sends overtemp event t
On Sunday, February 16, 2025 3:04 AM, Jakub Kicinski wrote:
>On Sat, 15 Feb 2025 11:01:59 -0800 Jakub Kicinski wrote:
>> On Fri, 7 Feb 2025 10:19:39 +0800 Song Yoong Siang wrote:
>> > Extend the XDP Tx metadata framework so that user can requests launch time
>> > hardware offload, where the Ether
Extend the XDP Tx metadata framework so that user can requests launch time
hardware offload, where the Ethernet device will schedule the packet for
transmission at a pre-determined time called launch time. The value of
launch time is communicated from user space to Ethernet driver via
launch_time f
Add launch time hardware offload request to xdp_hw_metadata. Users can
configure the delta of launch time relative to HW RX-time using the "-l"
argument. By default, the delta is set to 0 ns, which means the launch time
is disabled. By setting the delta to a non-zero value, the launch time
hardware
This series expands the XDP TX metadata framework to allow user
applications to pass per packet 64-bit launch time directly to the kernel
driver, requesting launch time hardware offload support. The XDP TX
metadata framework will not perform any clock conversion or packet
reordering.
Please note t
Refactor the code for inserting an empty frame into a new function
igc_insert_empty_frame(). This change extracts the logic for inserting
an empty packet from igc_xmit_frame_ring() into a separate function,
allowing it to be reused in future implementations, such as the XDP
zero copy transmit funct
Enable launch time (Time-Based Scheduling) support for XDP zero copy via
the XDP Tx metadata framework.
This patch has been tested with tools/testing/selftests/bpf/xdp_hw_metadata
on Intel Tiger Lake platform. Below are the test steps and result.
Test 1: Send a single packet with the launch time
Enable Launch Time Control (LTC) support for XDP zero copy via XDP Tx
metadata framework.
This patch has been tested with tools/testing/selftests/bpf/xdp_hw_metadata
on Intel I225-LM Ethernet controller. Below are the test steps and result.
Test 1: Send a single packet with the launch time set to
On Fri, 7 Feb 2025 10:19:39 +0800 Song Yoong Siang wrote:
> Extend the XDP Tx metadata framework so that user can requests launch time
> hardware offload, where the Ethernet device will schedule the packet for
> transmission at a pre-determined time called launch time. The value of
> launch time i
On Sat, 15 Feb 2025 11:01:59 -0800 Jakub Kicinski wrote:
> On Fri, 7 Feb 2025 10:19:39 +0800 Song Yoong Siang wrote:
> > Extend the XDP Tx metadata framework so that user can requests launch time
> > hardware offload, where the Ethernet device will schedule the packet for
> > transmission at a pre
On Tue, 11 Feb 2025 14:06:51 -0700 Ahmed Zaki wrote:
> Drivers usually need to re-apply the user-set IRQ affinity to their IRQs
> after reset. However, since there can be only one IRQ affinity notifier
> for each IRQ, registering IRQ notifiers conflicts with the ARFS rmap
> management in the core (
On Sat, 15 Feb 2025 09:41:54 -0800 Jakub Kicinski wrote:
> On Tue, 11 Feb 2025 14:06:51 -0700 Ahmed Zaki wrote:
> > Drivers usually need to re-apply the user-set IRQ affinity to their IRQs
> > after reset. However, since there can be only one IRQ affinity notifier
> > for each IRQ, registering IRQ
On Tue, 11 Feb 2025 14:06:53 -0700 Ahmed Zaki wrote:
> +static void netif_napi_affinity_release(struct kref *ref)
> +{
> + struct napi_struct *napi =
> + container_of(ref, struct napi_struct, notify.kref);
> + struct cpu_rmap *rmap = napi->dev->rx_cpu_rmap;
> +
We should only g
On Tue, 11 Feb 2025 14:06:54 -0700 Ahmed Zaki wrote:
> @@ -11575,9 +11615,9 @@ struct net_device *alloc_netdev_mqs(int sizeof_priv,
> const char *name,
> void (*setup)(struct net_device *),
> unsigned int txqs, unsigned int rxqs)
> {
> + unsigned int maxqs, i, numa
On Thu, Feb 13, 2025 at 01:32:38PM +0100, Marcin Szycik wrote:
>
>
> On 13.02.2025 11:55, Simon Horman wrote:
> > On Tue, Feb 11, 2025 at 06:43:21PM +0100, Marcin Szycik wrote:
> >> If ice_ena_vfs() fails after calling ice_create_vf_entries(), it frees
> >> all VFs without removing them from snap
18 matches
Mail list logo
