lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 7 Sep 2022 19:51:38 +0000 From: Parav Pandit <parav@...dia.com> To: "Michael S. Tsirkin" <mst@...hat.com> CC: Gavin Li <gavinl@...dia.com>, "stephen@...workplumber.org" <stephen@...workplumber.org>, "davem@...emloft.net" <davem@...emloft.net>, "jesse.brandeburg@...el.com" <jesse.brandeburg@...el.com>, "kuba@...nel.org" <kuba@...nel.org>, "sridhar.samudrala@...el.com" <sridhar.samudrala@...el.com>, "jasowang@...hat.com" <jasowang@...hat.com>, "loseweigh@...il.com" <loseweigh@...il.com>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "virtualization@...ts.linux-foundation.org" <virtualization@...ts.linux-foundation.org>, "virtio-dev@...ts.oasis-open.org" <virtio-dev@...ts.oasis-open.org>, Gavi Teitz <gavi@...dia.com>, Xuan Zhuo <xuanzhuo@...ux.alibaba.com>, Si-Wei Liu <si-wei.liu@...cle.com> Subject: RE: [PATCH v5 2/2] virtio-net: use mtu size as buffer length for big packets > From: Michael S. Tsirkin <mst@...hat.com> > Sent: Wednesday, September 7, 2022 3:36 PM > > On Wed, Sep 07, 2022 at 07:27:16PM +0000, Parav Pandit wrote: > > > > > From: Michael S. Tsirkin <mst@...hat.com> > > > Sent: Wednesday, September 7, 2022 3:24 PM > > > > > > On Wed, Sep 07, 2022 at 07:18:06PM +0000, Parav Pandit wrote: > > > > > > > > > From: Michael S. Tsirkin <mst@...hat.com> > > > > > Sent: Wednesday, September 7, 2022 3:12 PM > > > > > > > > > > Because of shallow queue of 16 entries deep. > > > > > > > > > > but why is the queue just 16 entries? > > > > I explained the calculation in [1] about 16 entries. > > > > > > > > [1] > > > > > > > > https://lore.kernel.org/netdev/PH0PR12MB54812EC7F4711C1EA4CAA119DC > > > 419@ > > > > PH0PR12MB5481.namprd12.prod.outlook.com/ > > > > > > > > > does the device not support indirect? > > > > > > > > > Yes, indirect feature bit is disabled on the device. > > > > > > OK that explains it. > > > > So can we proceed with v6 to contain > > (a) updated commit message and > > (b) function name change you suggested to drop _fields suffix? > > (c) replace mtu = 0 with sensibly not calling the function when mtu is > unknown. > > > And I'd like commit log to include results of perf testing > - with indirect feature on Which device do you suggest using for this test? > - with mtu feature off Why is this needed when it is not touching the area of mtu being not offered? > just to make sure nothing breaks. Not sure why you demand this. Can you please share the link to other patches that ensured that nothing breaks, for example I didn't see a similar "test ask" in v14 series [1]? What is so special about current patch of interest vs [1] that requires this special testing details in commit log, and it is not required in [1] or past patches? Do you have link to the tests done with synchronization tests by commit [2]? This will help to define test matrix for developers and internal regression and similar report in all subsequent patches like [1]. [1] https://lore.kernel.org/bpf/20220801063902.129329-41-xuanzhuo@linux.alibaba.com/ [2] 6213f07cb54
Powered by blists - more mailing lists