Message ID | 20210927182523.2704818-1-weiwan@google.com (mailing list archive) |
---|---|
Headers | show |
Series | net: add new socket option SO_RESERVE_MEM | expand |
On Mon, 27 Sep 2021 11:25:20 -0700 Wei Wang wrote: > This patch series introduces a new socket option SO_RESERVE_MEM. > This socket option provides a mechanism for users to reserve a certain > amount of memory for the socket to use. When this option is set, kernel > charges the user specified amount of memory to memcg, as well as > sk_forward_alloc. This amount of memory is not reclaimable and is > available in sk_forward_alloc for this socket. > With this socket option set, the networking stack spends less cycles > doing forward alloc and reclaim, which should lead to better system > performance, with the cost of an amount of pre-allocated and > unreclaimable memory, even under memory pressure. Does not apply cleanly - would you mind rebasing/resending? Would you be able to share what order of magnitude improvements you see? Thanks!
On Mon, Sep 27, 2021 at 5:50 PM Jakub Kicinski <kuba@kernel.org> wrote: > > On Mon, 27 Sep 2021 11:25:20 -0700 Wei Wang wrote: > > This patch series introduces a new socket option SO_RESERVE_MEM. > > This socket option provides a mechanism for users to reserve a certain > > amount of memory for the socket to use. When this option is set, kernel > > charges the user specified amount of memory to memcg, as well as > > sk_forward_alloc. This amount of memory is not reclaimable and is > > available in sk_forward_alloc for this socket. > > With this socket option set, the networking stack spends less cycles > > doing forward alloc and reclaim, which should lead to better system > > performance, with the cost of an amount of pre-allocated and > > unreclaimable memory, even under memory pressure. > > Does not apply cleanly - would you mind rebasing/resending? > Sure. Will do. Sorry about that. > Would you be able to share what order of magnitude improvements you see? > OK. Will share some results from a synthetic benchmark. > Thanks!