netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] ipv4: fix TCP early demux
Date: Fri, 27 Jul 2012 16:00:01 -0700 (PDT)	[thread overview]
Message-ID: <20120727.160001.1267518985220537042.davem@davemloft.net> (raw)
In-Reply-To: <1343424873.2626.13112.camel@edumazet-glaptop>

From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Fri, 27 Jul 2012 23:34:33 +0200

> I wonder why cookie is not stored in dst, and must be stored outside
> of it ?

Because in ipv6, cloned routes are never invalidated on a route
insertion or deletion.  We keep them around.

The fn_sernum tracks path reachability, rather than validation of
dsts.

So when we delete or insert a new ipv6 route, we update the serial
number of all the FIB nodes on the way down to the insert/delete
point.

If, afterwards, we can still reach a route cloned from one of those
entries successfully.  It is still valid.

If we were to store the serial number on the dst, it would invalidate
the cloned route, which the ipv6 code is largely not designed for.

To be honest, the whole route validation scheme in ipv6 was
jackhammered into place.  It was basically two years of Alexey
repairing the largely broken scheme that Pedro had put into place.

This is ~1997 legacy stuff.

It deserves a complete rewrite, but we are too busy with ipv4 at the
moment.  And frankly if nobody other than myself was concerned enough
to delete the ipv4 routing cache (code people actually use) the
likelyhood of anyone embarking on a task of similar size for ipv6 is
basically zero.

      reply	other threads:[~2012-07-27 23:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-27 16:23 [PATCH] ipv4: fix TCP early demux Eric Dumazet
2012-07-27 20:47 ` David Miller
2012-07-27 21:34   ` Eric Dumazet
2012-07-27 23:00     ` David Miller [this message]

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=20120727.160001.1267518985220537042.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=eric.dumazet@gmail.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 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).