netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: menglong8.dong@gmail.com
To: rostedt@goodmis.org, idosch@idosch.org
Cc: mingo@redhat.com, nhorman@tuxdriver.com, davem@davemloft.net,
	kuba@kernel.org, imagedong@tencent.com, dsahern@kernel.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: [PATCH net-next 0/2] net: drop_monitor: support drop reason
Date: Tue,  8 Feb 2022 15:28:34 +0800	[thread overview]
Message-ID: <20220208072836.3540192-1-imagedong@tencent.com> (raw)

From: Menglong Dong <imagedong@tencent.com>

This series patches is to make drop monitor supporting drop reason
and report it to user space.

In the first patch, we define the macro 'SKB_DR_MAX_LEN', which is
the max string length of drop reasons. We introduce this macro as
drop_monitor need to know the memory allocated for NET_DM_ATTR_REASON
in the second patch.

In the second patch, we report drop reasons as string to user space
in drop_monitor.


Menglong Dong (2):
  net: skb: introduce SKB_DR_MAX_LEN
  net: drop_monitor: support drop reason

 include/trace/events/skb.h       |  5 +++++
 include/uapi/linux/net_dropmon.h |  1 +
 net/core/drop_monitor.c          | 34 ++++++++++++++++++++++++++++----
 3 files changed, 36 insertions(+), 4 deletions(-)

-- 
2.27.0


             reply	other threads:[~2022-02-08  7:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08  7:28 menglong8.dong [this message]
2022-02-08  7:28 ` [PATCH net-next 1/2] net: skb: introduce SKB_DR_MAX_LEN menglong8.dong
2022-02-08  7:28 ` [PATCH v7 net-next 2/2] net: drop_monitor: support drop reason menglong8.dong
2022-02-08 14:58   ` Ido Schimmel
2022-02-09  2:49     ` Menglong Dong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220208072836.3540192-1-imagedong@tencent.com \
    --to=menglong8.dong@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=idosch@idosch.org \
    --cc=imagedong@tencent.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=rostedt@goodmis.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).