diff options
author | David S. Miller <davem@davemloft.net> | 2019-04-15 23:36:51 +0300 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2019-04-15 23:36:51 +0300 |
commit | c7cf89b5dd38a9f2aa410f70f80ba0c4c4d02239 (patch) | |
tree | baba7e7942d6e6a3162db024a2995f306d0afad4 /drivers | |
parent | 93144b0ecde584e1e480abf45429ef47a5e02ac9 (diff) | |
parent | 9dde27de3e5efa0d032f3c891a0ca833a0d31911 (diff) | |
download | linux-c7cf89b5dd38a9f2aa410f70f80ba0c4c4d02239.tar.xz |
Merge branch 'sctp-fully-support-memory-accounting'
Xin Long says:
====================
sctp: fully support memory accounting
sctp memory accounting is added in this patchset by using
these kernel APIs on send side:
- sk_mem_charge()
- sk_mem_uncharge()
- sk_wmem_schedule()
- sk_under_memory_pressure()
- sk_mem_reclaim()
and these on receive side:
- sk_mem_charge()
- sk_mem_uncharge()
- sk_rmem_schedule()
- sk_under_memory_pressure()
- sk_mem_reclaim()
With sctp memory accounting, we can limit the memory allocation by
either sysctl:
# sysctl -w net.sctp.sctp_mem="10 20 50"
or cgroup:
# echo $((8<<14)) > \
/sys/fs/cgroup/memory/sctp_mem/memory.kmem.tcp.limit_in_bytes
When the socket is under memory pressure, the send side will block
and wait, while the receive side will renege or drop.
v1->v2:
- add the missing Reported/Tested/Acked/-bys.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions