[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20180702.224247.143793494675352608.davem@davemloft.net>
Date: Mon, 02 Jul 2018 22:42:47 +0900 (KST)
From: David Miller <davem@...emloft.net>
To: laoar.shao@...il.com
Cc: satoru.moriya@....com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] net: expose sk wmem in sock_exceed_buf_limit tracepoint
From: Yafang Shao <laoar.shao@...il.com>
Date: Sun, 1 Jul 2018 23:31:30 +0800
> Currently trace_sock_exceed_buf_limit() only show rmem info,
> but wmem limit may also be hit.
> So expose wmem info in this tracepoint as well.
>
> Regarding memcg, I think it is better to introduce a new tracepoint(if
> that is needed), i.e. trace_memcg_limit_hit other than show memcg info in
> trace_sock_exceed_buf_limit.
>
> Signed-off-by: Yafang Shao <laoar.shao@...il.com>
Applied to net-next.
Powered by blists - more mailing lists