On Fri, Mar 22, 2019 at 4:28 AM Michael S. Tsirkin <[email protected]> wrote:
>
>
> Just a thought: would it make sense to flush the cache
> in enter_memory_pressure?
>
Good question, thanks !
Willem asked me something similar yesterday.
The argument of keeping one skb for tx and one for rx makes some sense
to me, since it will more or less facilitate forward progress.
References :
commit 8e4d980ac215 ("tcp: fix behavior for epoll edge trigger")
commit eb9344781a2f8 ("tcp: add a force_schedule argument to
sk_stream_alloc_skb()")
The global tcp_memory_pressure status should play its role for
elephant flows (not the RPC workload targeted by this patch series),
so that they gradually reduce their memory usage to the minimum of one
packet per TCP flow.
