From mboxrd@z Thu Jan 1 00:00:00 1970 From: Saeed Mahameed Date: Thu, 10 Dec 2020 10:58:07 -0800 Subject: [Intel-wired-lan] [PATCH v2 bpf 1/5] net: ethtool: add xdp properties flag set In-Reply-To: References: <20201204102901.109709-1-marekx.majtyka@intel.com> <20201204102901.109709-2-marekx.majtyka@intel.com> <878sad933c.fsf@toke.dk> <20201204124618.GA23696@ranger.igk.intel.com> <048bd986-2e05-ee5b-2c03-cd8c473f6636@iogearbox.net> <20201207135433.41172202@carbon> <5fce960682c41_5a96208e4@john-XPS-13-9370.notmuch> <20201207230755.GB27205@ranger.igk.intel.com> <5fd068c75b92d_50ce20814@john-XPS-13-9370.notmuch> <20201209095454.GA36812@ranger.igk.intel.com> <20201209125223.49096d50@carbon> <1e5e044c8382a68a8a547a1892b48fb21d53dbb9.camel@kernel.org> Message-ID: <6f8c23d4ac60525830399754b4891c12943b63ac.camel@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: intel-wired-lan@osuosl.org List-ID: On Thu, 2020-12-10 at 08:30 -0700, David Ahern wrote: > On 12/9/20 11:48 PM, Saeed Mahameed wrote: > > On Wed, 2020-12-09 at 20:34 -0700, David Ahern wrote: > > > On 12/9/20 10:15 AM, Saeed Mahameed wrote: > > > > > My personal experience with this one is mlx5/ConnectX4-LX > > > > > with a > > > > > limit > > > > > > > > This limit was removed from mlx5 > > > > https://patchwork.ozlabs.org/project/netdev/patch/20200107191335.12272-5-saeedm at mellanox.com/ > > > > Note: you still need to use ehttool to increase from 64 to 128 > > > > or > > > > 96 in > > > > your case. > > > > > > > > > > I asked you about that commit back in May: > > > > > > > :/, sorry i missed this email, must have been the mlnx nvidia email > > transition. > > > > > https://lore.kernel.org/netdev/198081c2-cb0d-e1d5-901c-446b63c36706 at gmail.com/ > > > > > > As noted in the thread, it did not work for me. > > > > Still relevant ? I might need to get you some tools to increase > > #msix > > in Firmware. > > > > not for me at the moment, but it would be good to document what a > user > needs to do - especially if it involves vendor specific tools and > steps. Ack, Thanks for pointing that out, I will take action on this.