bpf: stream: start using kmalloc_nolock()#10082
bpf: stream: start using kmalloc_nolock()#10082kernel-patches-daemon-bpf[bot] wants to merge 2 commits intobpf-next_basefrom
Conversation
|
Upstream branch: e758657 |
|
Upstream branch: e758657 |
c9d3615 to
ab446b6
Compare
d4664e4 to
7c1a423
Compare
|
Upstream branch: e758657 |
ab446b6 to
800994f
Compare
7c1a423 to
ecdeefe
Compare
|
Upstream branch: e758657 |
800994f to
4b97e68
Compare
ecdeefe to
10ce4bd
Compare
|
Upstream branch: ff88079 |
4b97e68 to
39bdf49
Compare
10ce4bd to
e5828a2
Compare
|
Upstream branch: f9db3a3 |
39bdf49 to
b8d722f
Compare
e5828a2 to
13927c8
Compare
|
Upstream branch: 8842732 |
b8d722f to
2bcca1e
Compare
13927c8 to
9b73883
Compare
|
Upstream branch: 23f852d |
2bcca1e to
b8dc219
Compare
9b73883 to
3cfe497
Compare
|
Upstream branch: 54c134f |
b8dc219 to
5567403
Compare
3cfe497 to
6d6792d
Compare
|
Upstream branch: 9f317bd |
5567403 to
4ea0bce
Compare
6d6792d to
4481a85
Compare
|
Upstream branch: 54c134f |
4ea0bce to
6fc81c6
Compare
4481a85 to
5125528
Compare
BPF stream kfuncs need to be non-sleeping as they can be called from programs running in any context, this requires a way to allocate memory from any context. Currently, this is done by a custom per-CPU NMI-safe bump allocation mechanism, backed by try_alloc_pages() and free_pages_nolock() primitives. As kmalloc_nolock() and kfree_nolock() primitives are available now, the custom allocator can be removed in favor of these. Signed-off-by: Puranjay Mohan <puranjay@kernel.org> Acked-by: Kumar Kartikeya Dwivedi <memxor@gmail.com>
|
Upstream branch: e2e668b |
6fc81c6 to
89868e0
Compare
5125528 to
1e2d874
Compare
|
At least one diff in series https://patchwork.kernel.org/project/netdevbpf/list/?series=1015112 irrelevant now. Closing PR. |
Pull request for series with
subject: bpf: stream: start using kmalloc_nolock()
version: 1
url: https://patchwork.kernel.org/project/netdevbpf/list/?series=1015112