[PATCH bpf-next v3 0/2] xsk: XSKMAP lookup improvements · Björn Töpel <hidden> · 2019-10-25
[PATCH bpf-next v3 1/2] xsk: store struct xdp_sock as a flexible array member of the XSKMAP · Björn Töpel <hidden> · 2019-10-25
Re: [PATCH bpf-next v3 1/2] xsk: store struct xdp_sock as a flexible array member of the XSKMAP · Jonathan Lemon <hidden> · 2019-10-25
Re: [PATCH bpf-next v3 1/2] xsk: store struct xdp_sock as a flexible array member of the XSKMAP · Jakub Kicinski <hidden> · 2019-10-28
Re: [PATCH bpf-next v3 1/2] xsk: store struct xdp_sock as a flexible array member of the XSKMAP · Björn Töpel <hidden> · 2019-10-28
[PATCH bpf-next v3 2/2] bpf: implement map_gen_lookup() callback for XSKMAP · Björn Töpel <hidden> · 2019-10-25
Re: [PATCH bpf-next v3 2/2] bpf: implement map_gen_lookup() callback for XSKMAP · Jonathan Lemon <hidden> · 2019-10-25

Re: [PATCH bpf-next v3 1/2] xsk: store struct xdp_sock as a flexible array member of the XSKMAP

From: Jakub Kicinski <hidden>
Date: 2019-10-28 18:01:11
Also in: bpf

On Fri, 25 Oct 2019 11:32:18 +0200, Björn Töpel wrote:

From: Björn Töpel <redacted>

Prior this commit, the array storing XDP socket instances were stored
in a separate allocated array of the XSKMAP. Now, we store the sockets
as a flexible array member in a similar fashion as the arraymap. Doing
so, we do less pointer chasing in the lookup.

Signed-off-by: Björn Töpel <redacted>

Damn, looks like I managed to reply to v2. 

I think the size maths may overflow on 32bit machines on the addition.

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help