From: David Ahern <dsahern@gmail.com>
To: Martin Lau <kafai@fb.com>, David Ahern <dsahern@kernel.org>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"idosch@mellanox.com" <idosch@mellanox.com>
Subject: Re: [PATCH v3 net-next 1/5] ipv4: Update fib_table_lookup tracepoint to take common nexthop
Date: Tue, 2 Apr 2019 10:03:34 -0600 [thread overview]
Message-ID: <4e015b18-cd94-76ba-e922-34d4c91c9f89@gmail.com> (raw)
In-Reply-To: <20190402160058.efxurtjpgxa7mxa4@kafai-mbp.dhcp.thefacebook.com>
On 4/2/19 10:01 AM, Martin Lau wrote:
> On Mon, Apr 01, 2019 at 08:02:30PM -0700, David Ahern wrote:
>> From: David Ahern <dsahern@gmail.com>
>>
>> Update fib_table_lookup tracepoint to take a fib_nh_common struct and
>> dump the v6 gateway address if the nexthop uses it.
>>
>> Signed-off-by: David Ahern <dsahern@gmail.com>
>> ---
>> include/trace/events/fib.h | 45 ++++++++++++++++++++++++++-------------------
>> net/ipv4/fib_trie.c | 2 +-
>> 2 files changed, 27 insertions(+), 20 deletions(-)
>>
>> diff --git a/include/trace/events/fib.h b/include/trace/events/fib.h
>> index 61ea7a24c8e5..7f83b6eafc5c 100644
>> --- a/include/trace/events/fib.h
>> +++ b/include/trace/events/fib.h
>> @@ -13,9 +13,9 @@
>> TRACE_EVENT(fib_table_lookup,
>>
>> TP_PROTO(u32 tb_id, const struct flowi4 *flp,
>> - const struct fib_nh *nh, int err),
>> + const struct fib_nh_common *nhc, int err),
>>
>> - TP_ARGS(tb_id, flp, nh, err),
>> + TP_ARGS(tb_id, flp, nhc, err),
>>
>> TP_STRUCT__entry(
>> __field( u32, tb_id )
>> @@ -28,14 +28,17 @@ TRACE_EVENT(fib_table_lookup,
>> __field( __u8, flags )
>> __array( __u8, src, 4 )
>> __array( __u8, dst, 4 )
>> - __array( __u8, gw, 4 )
>> - __array( __u8, saddr, 4 )
> saddr is no longer useful?
>
I have not found it useful, and I use this tracepoint a lot. The line
length is really long as is and adding the ipv6 address just makes it worse.
next prev parent reply other threads:[~2019-04-02 16:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 3:02 [PATCH v3 net-next 0/5] net: More movement to fib_nh_common David Ahern
2019-04-02 3:02 ` [PATCH v3 net-next 1/5] ipv4: Update fib_table_lookup tracepoint to take common nexthop David Ahern
2019-04-02 16:01 ` Martin Lau
2019-04-02 16:03 ` David Ahern [this message]
2019-04-02 17:06 ` Martin Lau
2019-04-02 17:41 ` David Miller
2019-04-02 3:02 ` [PATCH v3 net-next 2/5] ipv4: Add fib_nh_common to fib_result David Ahern
2019-04-02 17:10 ` Martin Lau
2019-04-02 17:18 ` David Ahern
2019-04-02 3:02 ` [PATCH v3 net-next 3/5] ipv4: Refactor nexthop attributes in fib_dump_info David Ahern
2019-04-02 17:10 ` Martin Lau
2019-04-02 3:02 ` [PATCH v3 net-next 4/5] ipv4: Change fib_nexthop_info and fib_add_nexthop to take fib_nh_common David Ahern
2019-04-02 17:11 ` Martin Lau
2019-04-02 3:02 ` [PATCH v3 net-next 5/5] ipv6: Flip to fib_nexthop_info David Ahern
2019-04-02 17:13 ` Martin Lau
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=4e015b18-cd94-76ba-e922-34d4c91c9f89@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=idosch@mellanox.com \
--cc=kafai@fb.com \
--cc=netdev@vger.kernel.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.