Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Mon, 02 Jul 2018 22:42:47 +0900 (KST)
Message-Id: <20180702.224247.143793494675352608.davem@davemloft.net>
To:     laoar.shao@gmail.com
Cc:     satoru.moriya@hds.com, netdev@vger.kernel.org,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: expose sk wmem in sock_exceed_buf_limit tracepoint
From:   David Miller <davem@davemloft.net>
In-Reply-To: <1530459090-11037-1-git-send-email-laoar.shao@gmail.com>
References: <1530459090-11037-1-git-send-email-laoar.shao@gmail.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

From: Yafang Shao <laoar.shao@gmail.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@gmail.com>

Applied to net-next.