From: Jakub Kicinski <kuba@kernel.org>
To: Menglong Dong <menglong8.dong@gmail.com>
Cc: David Miller <davem@davemloft.net>,
Steven Rostedt <rostedt@goodmis.org>,
mingo@redhat.com, Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
dsahern@kernel.org, Menglong Dong <imagedong@tencent.com>,
LKML <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 0/2] net: snmp: tracepoint support for snmp
Date: Thu, 11 Nov 2021 17:50:32 -0800 [thread overview]
Message-ID: <20211111175032.14999302@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <CADxym3bk5+3t9jFmEgCBBYHWvNJx6BJGdjk+-zqiQaJPtLM=Ug@mail.gmail.com>
On Fri, 12 Nov 2021 09:40:47 +0800 Menglong Dong wrote:
> > I feel like I have seen this idea before. Is this your first posting?
> >
> > Would you mind including links to previous discussion if you're aware
> > of any?
>
> This is the first time that I post this patch. Do you mean that someone
> else has done this before? Sorry, I didn't find it~
I see. Yes, I believe very similar changes were proposed in the past.
I believe that concerns about the performance impact had prevented them
from being merged.
next prev parent reply other threads:[~2021-11-12 1:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 13:35 [PATCH net-next 0/2] net: snmp: tracepoint support for snmp menglong8.dong
2021-11-11 13:35 ` [PATCH net-next 1/2] net: snmp: add " menglong8.dong
2021-11-16 21:34 ` Steven Rostedt
2021-11-17 13:55 ` Menglong Dong
2021-11-11 13:35 ` [PATCH net-next 2/2] net: snmp: add snmp tracepoint support for udp menglong8.dong
2021-11-11 21:07 ` kernel test robot
2021-11-11 21:07 ` kernel test robot
2021-11-13 3:32 ` kernel test robot
2021-11-13 3:32 ` kernel test robot
2021-11-11 14:08 ` [PATCH net-next 0/2] net: snmp: tracepoint support for snmp Jakub Kicinski
2021-11-12 1:40 ` Menglong Dong
2021-11-12 1:50 ` Jakub Kicinski [this message]
2021-11-12 6:42 ` Menglong Dong
2021-11-12 14:31 ` Steven Rostedt
2021-11-16 2:27 ` 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=20211111175032.14999302@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=imagedong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menglong8.dong@gmail.com \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=yoshfuji@linux-ipv6.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.