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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 19 Jan 2021 15:43:43 -0800 From: Ivan Babrou <ivan@...udflare.com> To: Jakub Kicinski <kuba@...nel.org> Cc: Linux Kernel Network Developers <netdev@...r.kernel.org>, linux-kernel <linux-kernel@...r.kernel.org>, bpf@...r.kernel.org, kernel-team <kernel-team@...udflare.com>, Edward Cree <ecree.xilinx@...il.com>, Martin Habets <habetsm.xilinx@...il.com>, "David S. Miller" <davem@...emloft.net>, Alexei Starovoitov <ast@...nel.org>, Daniel Borkmann <daniel@...earbox.net>, Jesper Dangaard Brouer <hawk@...nel.org>, John Fastabend <john.fastabend@...il.com> Subject: Re: [PATCH net-next] sfc: reduce the number of requested xdp ev queues On Thu, Dec 17, 2020 at 10:14 AM Jakub Kicinski <kuba@...nel.org> wrote: > > On Mon, 14 Dec 2020 17:29:06 -0800 Ivan Babrou wrote: > > Without this change the driver tries to allocate too many queues, > > breaching the number of available msi-x interrupts on machines > > with many logical cpus and default adapter settings: > > > > Insufficient resources for 12 XDP event queues (24 other channels, max 32) > > > > Which in turn triggers EINVAL on XDP processing: > > > > sfc 0000:86:00.0 ext0: XDP TX failed (-22) > > > > Signed-off-by: Ivan Babrou <ivan@...udflare.com> > > Looks like the discussion may have concluded, but we don't take -next > patches during the merge window, so please repost when net-next reopens. > > Thanks! > -- > # Form letter - net-next is closed > > We have already sent the networking pull request for 5.11 and therefore > net-next is closed for new drivers, features, code refactoring and > optimizations. We are currently accepting bug fixes only. > > Please repost when net-next reopens after 5.11-rc1 is cut. Should I resend my patch now that the window is open or is bumping this thread enough? > Look out for the announcement on the mailing list or check: > http://vger.kernel.org/~davem/net-next.html > > RFC patches sent for review only are obviously welcome at any time.
Powered by blists - more mailing lists