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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220629091707.20d66524@kernel.org>
Date:   Wed, 29 Jun 2022 09:17:07 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     Maciej Fijalkowski <maciej.fijalkowski@...el.com>
Cc:     Björn Töpel <bjorn.topel@...il.com>,
        bpf <bpf@...r.kernel.org>, Alexei Starovoitov <ast@...nel.org>,
        Daniel Borkmann <daniel@...earbox.net>,
        Andrii Nakryiko <andrii@...nel.org>,
        Netdev <netdev@...r.kernel.org>,
        "Karlsson, Magnus" <magnus.karlsson@...el.com>
Subject: Re: [PATCH bpf] xsk: mark napi_id on sendmsg()

On Wed, 29 Jun 2022 09:16:29 -0700 Jakub Kicinski wrote:
> > Would it make sense to introduce napi_id to xsk_buff_pool then?
> > xp_set_rxq_info() could be setting it. We are sure that napi_id is the
> > same for whole pool (each xdp_buff_xsk's rxq info).  
> 
> Would it be possible to move the marking to when the queue is getting
> bound instead of the recv/send paths? 

I mean when socket is getting bound.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ