Re: [PATCH bpf-next v5 1/3] devmap/cpumap: Use flush list instead of bitmap

2019-06-28 Thread Toke Høiland-Jørgensen
Daniel Borkmann writes: > On 06/23/2019 04:17 AM, Toke Høiland-Jørgensen wrote: >> From: Toke Høiland-Jørgensen >> >> The socket map uses a linked list instead of a bitmap to keep track of >> which entries to flush. Do the same for devmap and cpumap, as this means we >> don't have to care about

Re: [PATCH bpf-next v5 1/3] devmap/cpumap: Use flush list instead of bitmap

2019-06-27 Thread Daniel Borkmann
On 06/23/2019 04:17 AM, Toke Høiland-Jørgensen wrote: > From: Toke Høiland-Jørgensen > > The socket map uses a linked list instead of a bitmap to keep track of > which entries to flush. Do the same for devmap and cpumap, as this means we > don't have to care about the map index when enqueueing th

Re: [PATCH bpf-next v5 1/3] devmap/cpumap: Use flush list instead of bitmap

2019-06-24 Thread Jonathan Lemon
On 22 Jun 2019, at 19:17, Toke Høiland-Jørgensen wrote: > From: Toke Høiland-Jørgensen > > The socket map uses a linked list instead of a bitmap to keep track of > which entries to flush. Do the same for devmap and cpumap, as this means we > don't have to care about the map index when enqueuei

[PATCH bpf-next v5 1/3] devmap/cpumap: Use flush list instead of bitmap

2019-06-22 Thread Toke Høiland-Jørgensen
From: Toke Høiland-Jørgensen The socket map uses a linked list instead of a bitmap to keep track of which entries to flush. Do the same for devmap and cpumap, as this means we don't have to care about the map index when enqueueing things into the map (and so we can cache the map lookup). Signed-