On Tue, Apr 16, 2024 at 12:25 AM Jiri Pirko wrote:
>
> From: Jiri Pirko
>
> Currently there is no way for user to set what features the driver
> should obey or not, it is hard wired in the code.
>
> In order to be able to debug the device behavior in case some feature is
> disabled, introduce a d
On Mon, Apr 15, 2024 at 5:04 PM Xuan Zhuo wrote:
>
> On Mon, 15 Apr 2024 16:56:45 +0800, Jason Wang wrote:
> > On Mon, Apr 15, 2024 at 4:50 PM Xuan Zhuo
> > wrote:
> > >
> > > On Mon, 15 Apr 2024 14:43:24 +0800, Jason Wang
> > > wrote:
> > > > On Mon, Apr 15, 2024 at 10:35 AM Xuan Zhuo
> >
> From: Jakub Kicinski
> Sent: Friday, April 12, 2024 9:21 PM
> To: Dan Jurgens
> Cc: netdev@vger.kernel.org; m...@redhat.com; jasow...@redhat.com;
> xuanz...@linux.alibaba.com; virtualizat...@lists.linux.dev;
> da...@davemloft.net; eduma...@google.com; pab...@redhat.com; Jiri
> Pirko
> Subject:
在 2024/4/16 上午4:03, Simon Horman 写道:
On Mon, Apr 15, 2024 at 05:36:36PM +0800, Heng Qi wrote:
...
@@ -10229,6 +10230,61 @@ static void netdev_do_free_pcpu_stats(struct
net_device *dev)
}
}
+static int dev_dim_profile_init(struct net_device *dev)
+{
+#if IS_ENABLED(CONFIG_DIML
On 2024-04-15 18:25 +0200, Jiri Pirko wrote:
> From: Jiri Pirko
>
> The existing setup_wait*() helper family check the status of the
> interface to be up. Introduce wait_for_dev() to wait for the netdevice
> to appear, for example after test script does manual device bind.
>
> Signed-off-by: Jir
> From: Heng Qi
> Sent: Monday, April 15, 2024 8:42 AM
> To: Dan Jurgens ; netdev@vger.kernel.org
> Cc: m...@redhat.com; jasow...@redhat.com; xuanz...@linux.alibaba.com;
> virtualizat...@lists.linux.dev; da...@davemloft.net;
> eduma...@google.com; k...@kernel.org; pab...@redhat.com; Jiri Pirko
>
On Mon, Apr 15, 2024 at 05:36:36PM +0800, Heng Qi wrote:
...
> @@ -10229,6 +10230,61 @@ static void netdev_do_free_pcpu_stats(struct
> net_device *dev)
> }
> }
>
> +static int dev_dim_profile_init(struct net_device *dev)
> +{
> +#if IS_ENABLED(CONFIG_DIMLIB)
> + u32 supported = dev-
On Sat, 13 Apr 2024 15:23:53 +0200 Jiri Pirko wrote:
> That is a goal. Currently I do it with:
> vng --qemu-opts="-nic
> tap,id=nd0,ifname=xtap0,model=virtio-net-pci,script=no,downscript=no,mac=52:54:00:12:34:57
> -nic
> tap,id=nd1,ifname=xtap1,model=virtio-net-pci,script=no,downscript=no,mac=52
From: Jiri Pirko
Introduce initial tests for virtio_net driver. Focus on feature testing
leveraging previously introduced debugfs feature filtering
infrastructure. Add very basic ping and F_MAC feature tests.
To run this, do:
$ make -C tools/testing/selftests/ TARGETS=drivers/net/virtio_net/ run
From: Jiri Pirko
The existing setup_wait*() helper family check the status of the
interface to be up. Introduce wait_for_dev() to wait for the netdevice
to appear, for example after test script does manual device bind.
Signed-off-by: Jiri Pirko
---
v1->v2:
- reworked wait_for_dev() helper to us
From: Jiri Pirko
Add a helper to be used to check if the netdevice is backed by specified
driver.
Signed-off-by: Jiri Pirko
---
tools/testing/selftests/net/forwarding/lib.sh | 12
1 file changed, 12 insertions(+)
diff --git a/tools/testing/selftests/net/forwarding/lib.sh
b/tools
From: Jiri Pirko
Allow driver tests to work without specifying the netdevice names.
Introduce a possibility to search for available netdevices according to
set driver name. Allow test to specify the name by setting
NETIF_FIND_DRIVER variable.
Note that user overrides this either by passing netde
From: Jiri Pirko
These two check can be done at he very beginning of the script.
As the follow up patch needs to add early code that needs to be executed
after the checks, move them.
Signed-off-by: Jiri Pirko
---
tools/testing/selftests/net/forwarding/lib.sh | 20 +--
1 file ch
From: Jiri Pirko
Currently there is no way for user to set what features the driver
should obey or not, it is hard wired in the code.
In order to be able to debug the device behavior in case some feature is
disabled, introduce a debugfs infrastructure with couple of files
allowing user to see wh
From: Jiri Pirko
This patchset aims at introducing very basic initial infrastructure
for virtio_net testing, namely it focuses on virtio feature testing.
The first patch adds support for debugfs for virtio devices, allowing
user to filter features to pretend to be driver that is not capable
of t
在 2024/4/13 上午3:53, Daniel Jurgens 写道:
Once the RTNL locking around the control buffer is removed there can be
contention on the per queue RX interrupt coalescing data. Use a spin
lock per queue.
Signed-off-by: Daniel Jurgens
---
drivers/net/virtio_net.c | 23 ---
1 fi
Virtio-net has different types of back-end device implementations.
In order to effectively optimize the dim library's gains for
different device implementations, let's use the new interface
params to fine-tune the profile list.
Since the profile now exists in netdevice, adding a function similar
t
Extract the initialization and destruction actions
of dim for use in the next patch.
Signed-off-by: Heng Qi
---
drivers/net/virtio_net.c | 38 +++---
1 file changed, 27 insertions(+), 11 deletions(-)
diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.
The NetDIM library, currently leveraged by an array of NICs, delivers
excellent acceleration benefits. Nevertheless, NICs vary significantly
in their dim profile list prerequisites.
Specifically, virtio-net backends may present diverse sw or hw device
implementation, making a one-size-fits-all par
These will be used in subsequent patches, including
newly declared profile arrays.
Signed-off-by: Heng Qi
---
include/linux/dim.h | 13 +
lib/dim/net_dim.c | 10 ++
2 files changed, 15 insertions(+), 8 deletions(-)
diff --git a/include/linux/dim.h b/include/linux/dim.h
ind
The NetDIM library provides excellent acceleration for many modern
network cards. However, the default profiles of DIM limits its maximum
capabilities for different NICs, so providing a way which the NIC can
be custom configured is necessary.
Currently, interaction with the driver is still based o
Please ignore this set, "RESEND v7" will be used instead.
在 2024/4/15 下午5:36, Heng Qi 写道:
The NetDIM library provides excellent acceleration for many modern
network cards. However, the default profiles of DIM limits its maximum
capabilities for different NICs, so providing a way which the NIC ca
Hi Heng,
kernel test robot noticed the following build warnings:
[auto build test WARNING on net-next/main]
url:
https://github.com/intel-lab-lkp/linux/commits/Heng-Qi/linux-dim-move-useful-macros-to-h-file/20240415-173921
base: net-next/main
patch link:
https://lore.kernel.org/r
Hi Heng,
kernel test robot noticed the following build warnings:
[auto build test WARNING on net-next/main]
url:
https://github.com/intel-lab-lkp/linux/commits/Heng-Qi/linux-dim-move-useful-macros-to-h-file/20240415-173921
base: net-next/main
patch link:
https://lore.kernel.org/r
The NetDIM library, currently leveraged by an array of NICs, delivers
excellent acceleration benefits. Nevertheless, NICs vary significantly
in their dim profile list prerequisites.
Specifically, virtio-net backends may present diverse sw or hw device
implementation, making a one-size-fits-all par
Virtio-net has different types of back-end device implementations.
In order to effectively optimize the dim library's gains for
different device implementations, let's use the new interface
params to fine-tune the profile list.
Since the profile now exists in netdevice, adding a function similar
t
These will be used in subsequent patches, including
newly declared profile arrays.
Signed-off-by: Heng Qi
---
include/linux/dim.h | 13 +
lib/dim/net_dim.c | 10 ++
2 files changed, 15 insertions(+), 8 deletions(-)
diff --git a/include/linux/dim.h b/include/linux/dim.h
ind
Extract the initialization and destruction actions
of dim for use in the next patch.
Signed-off-by: Heng Qi
---
drivers/net/virtio_net.c | 38 +++---
1 file changed, 27 insertions(+), 11 deletions(-)
diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.
The NetDIM library provides excellent acceleration for many modern
network cards. However, the default profiles of DIM limits its maximum
capabilities for different NICs, so providing a way which the NIC can
be custom configured is necessary.
Currently, interaction with the driver is still based o
On Mon, 15 Apr 2024 16:56:45 +0800, Jason Wang wrote:
> On Mon, Apr 15, 2024 at 4:50 PM Xuan Zhuo wrote:
> >
> > On Mon, 15 Apr 2024 14:43:24 +0800, Jason Wang wrote:
> > > On Mon, Apr 15, 2024 at 10:35 AM Xuan Zhuo
> > > wrote:
> > > >
> > > > On Fri, 12 Apr 2024 13:49:12 +0800, Jason Wang
On Mon, Apr 15, 2024 at 4:50 PM Xuan Zhuo wrote:
>
> On Mon, 15 Apr 2024 14:43:24 +0800, Jason Wang wrote:
> > On Mon, Apr 15, 2024 at 10:35 AM Xuan Zhuo
> > wrote:
> > >
> > > On Fri, 12 Apr 2024 13:49:12 +0800, Jason Wang
> > > wrote:
> > > > On Fri, Apr 12, 2024 at 1:39 PM Xuan Zhuo
> >
On Mon, 15 Apr 2024 14:43:24 +0800, Jason Wang wrote:
> On Mon, Apr 15, 2024 at 10:35 AM Xuan Zhuo wrote:
> >
> > On Fri, 12 Apr 2024 13:49:12 +0800, Jason Wang wrote:
> > > On Fri, Apr 12, 2024 at 1:39 PM Xuan Zhuo
> > > wrote:
> > > >
> > > > On Fri, 12 Apr 2024 12:47:55 +0800, Jason Wang
Sun, Apr 14, 2024 at 09:32:46PM CEST, benjamin.poir...@gmail.com wrote:
>On 2024-04-13 15:27 +0200, Jiri Pirko wrote:
>> Fri, Apr 12, 2024 at 10:38:30PM CEST, benjamin.poir...@gmail.com wrote:
>> >On 2024-04-12 17:13 +0200, Jiri Pirko wrote:
>> >> From: Jiri Pirko
>> >>
>> >> Allow driver tests t
On Mon, Apr 15, 2024 at 4:15 PM Xuan Zhuo wrote:
>
> On Mon, 15 Apr 2024 14:45:36 +0800, Jason Wang wrote:
> > On Mon, Apr 15, 2024 at 10:51 AM Xuan Zhuo
> > wrote:
> > >
> > > On Thu, 11 Apr 2024 14:09:24 +0800, Jason Wang
> > > wrote:
> > > > On Wed, Apr 10, 2024 at 6:55 PM Xuan Zhuo
> >
On Mon, 15 Apr 2024 14:45:36 +0800, Jason Wang wrote:
> On Mon, Apr 15, 2024 at 10:51 AM Xuan Zhuo wrote:
> >
> > On Thu, 11 Apr 2024 14:09:24 +0800, Jason Wang wrote:
> > > On Wed, Apr 10, 2024 at 6:55 PM Xuan Zhuo
> > > wrote:
> > > >
> > > > On Wed, 10 Apr 2024 14:09:23 +0800, Jason Wang
35 matches
Mail list logo
