All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Bernat <bernat@debian.org>
To: David Ahern <dsahern@gmail.com>
Cc: Baptiste Jonglez <baptiste@bitsofnetworks.org>,
	Alarig Le Lay <alarig@swordarmor.fr>,
	netdev@vger.kernel.org, jack@basilfillan.uk,
	Oliver <bird-o@sernet.de>
Subject: Re: IPv6 regression introduced by commit 3b6761d18bc11f2af2a6fc494e9026d39593f22c
Date: Mon, 28 Sep 2020 07:39:13 +0200	[thread overview]
Message-ID: <87wo0e8npa.fsf@debian.org> (raw)
In-Reply-To: <66345b05-7864-ced2-7f3c-493260be39f7@gmail.com> (David Ahern's message of "Sun, 27 Sep 2020 20:38:28 -0700")

 ❦ 27 septembre 2020 20:38 -07, David Ahern:

> fib_rt_alloc is incremented by calls to ip6_dst_alloc. Each of your
> 9,999 pings is to a unique address and hence causes a dst to be
> allocated and the counter to be incremented. It is never decremented.
> That is standard operating procedure.

At some point, only PMTU exceptions would create a dst entry.
-- 
Program defensively.
            - The Elements of Programming Style (Kernighan & Plauger)

  reply	other threads:[~2020-09-28  5:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-05  8:17 IPv6 regression introduced by commit 3b6761d18bc11f2af2a6fc494e9026d39593f22c Alarig Le Lay
2020-03-08  0:52 ` David Ahern
2020-03-08 10:57   ` Alarig Le Lay
2020-03-09  2:15     ` David Ahern
2020-03-09  8:59       ` Fabian Grünbichler
2020-03-09 10:47         ` Alarig Le Lay
2020-03-09 11:35           ` Fabian Grünbichler
2020-03-10 10:35       ` Alarig Le Lay
2020-03-10 15:27         ` David Ahern
2020-03-29 14:09           ` Alarig Le Lay
2020-09-27 15:35   ` Baptiste Jonglez
2020-09-27 16:10     ` Baptiste Jonglez
2020-09-28  3:38       ` David Ahern
2020-09-28  5:39         ` Vincent Bernat [this message]
2020-09-28  6:48         ` Baptiste Jonglez
2020-09-29  3:39           ` David Ahern

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=87wo0e8npa.fsf@debian.org \
    --to=bernat@debian.org \
    --cc=alarig@swordarmor.fr \
    --cc=baptiste@bitsofnetworks.org \
    --cc=bird-o@sernet.de \
    --cc=dsahern@gmail.com \
    --cc=jack@basilfillan.uk \
    --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.