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, 16 Nov 2022 08:04:56 +0200 From: Leon Romanovsky <leon@...nel.org> To: "Samudrala, Sridhar" <sridhar.samudrala@...el.com> Cc: Michal Swiatkowski <michal.swiatkowski@...ux.intel.com>, netdev@...r.kernel.org, davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com, edumazet@...gle.com, intel-wired-lan@...ts.osuosl.org, jiri@...dia.com, anthony.l.nguyen@...el.com, alexandr.lobakin@...el.com, wojciech.drewek@...el.com, lukasz.czapnik@...el.com, shiraz.saleem@...el.com, jesse.brandeburg@...el.com, mustafa.ismail@...el.com, przemyslaw.kitszel@...el.com, piotr.raczynski@...el.com, jacob.e.keller@...el.com, david.m.ertman@...el.com, leszek.kaliszczuk@...el.com Subject: Re: [PATCH net-next 00/13] resource management using devlink reload On Tue, Nov 15, 2022 at 07:59:06PM -0600, Samudrala, Sridhar wrote: > On 11/15/2022 11:57 AM, Leon Romanovsky wrote: <...> > > > In case of ice driver lspci -vs shows: > > > Capabilities: [70] MSI-X: Enable+ Count=1024 Masked > > > > > > so all vectors that hw supports (PFs, VFs, misc, etc). Because of that > > > total number of MSI-X in the devlink example from cover letter is 1024. > > > > > > I see that mellanox shows: > > > Capabilities: [9c] MSI-X: Enable+ Count=64 Masked > > > > > > I assume that 64 is in this case MSI-X ony for this one PF (it make > > > sense). > > Yes and PF MSI-X count can be changed through FW configuration tool, as > > we need to write new value when the driver is unbound and we need it to > > be persistent. Users are expecting to see "stable" number any time they > > reboot the server. It is not the case for VFs, as they are explicitly > > created after reboots and start "fresh" after every boot. > > > > So we set large enough but not too large value as a default for PFs. > > If you find sane model of how to change it through kernel, you can count > > on our support. > > I guess one main difference is that in case of ice, PF driver manager resources > for all its associated functions, not the FW. So the MSI-X count reported for PF > shows the total vectors(PF netdev, VFs, rdma, SFs). VFs talk to PF over a mailbox > to get their MSI-X vector information. What is the output of lspci for ice VF when the driver is not bound? Thanks > > >
Powered by blists - more mailing lists