Netdev List
 help / color / mirror / Atom feed
From: "Andreas Hübner" <andreas@k4n.de>
To: David Ahern <dsa@cumulusnetworks.com>
Cc: Hannes Frederic Sowa <hannes@stressinduktion.org>,
	netdev@vger.kernel.org, "d. caratti" <davide.caratti@gmail.com>
Subject: Re: icmpv6: issue with routing table entries from link local addresses
Date: Tue, 13 Sep 2016 11:22:42 +0200	[thread overview]
Message-ID: <20160913092242.GK26782@targo.k4n.de> (raw)
In-Reply-To: <bf36b487-1cdf-ede9-1ed8-cca17c7f5fc6@cumulusnetworks.com>

On Mon, Sep 12, 2016 at 01:17:24PM -0600, David Ahern wrote:
> v4.4 and on there are fib6 tracepoints that show the lookup result.
> May provide some insights.
>
> perf record -a -e fib6:*
> perf script

Thanks for the hint, didn't now that something like this exists.

Following up on my earlier mail, I wasn't able to reproduce the issue
with more recent kernel versions. (tried 4.7)

So I guess someone must have fixed it somewhere between 3.16 and 4.7. :)
Okay, will check the git and probably try to backport it.

Again, sorry that I did not check immediately with the more recent kernel
versions. Wasn't expecting that much has changed in this area.

But my request for information with regard to the FIB data structure
still remains, since I'm curious about how it actually works.
(And I already spent some time trying to understand it.)


Thanks for your help, everyone!

Andreas

  reply	other threads:[~2016-09-13  9:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-12 14:27 icmpv6: issue with routing table entries from link local addresses Andreas Hübner
2016-09-12 17:26 ` Hannes Frederic Sowa
2016-09-12 19:17   ` David Ahern
2016-09-13  9:22     ` Andreas Hübner [this message]
2016-09-13 11:59     ` Andreas Hübner
2016-09-13  2:03   ` Sowmini Varadhan
2016-09-13  2:42     ` Hannes Frederic Sowa
2016-09-13  3:05       ` Sowmini Varadhan
2016-09-13  3:01     ` YOSHIFUJI Hideaki
2016-09-13  6:35   ` Andreas Hübner

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=20160913092242.GK26782@targo.k4n.de \
    --to=andreas@k4n.de \
    --cc=davide.caratti@gmail.com \
    --cc=dsa@cumulusnetworks.com \
    --cc=hannes@stressinduktion.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox