From: Chris Friesen <chris.friesen@genband.com>
To: David Miller <davem@davemloft.net>
Cc: mparemm@gmail.com, netdev@vger.kernel.org
Subject: Re: IPv6 destination cache in Linux kernel
Date: Tue, 05 Jul 2011 13:58:58 -0600 [thread overview]
Message-ID: <4E136D02.3060302@genband.com> (raw)
In-Reply-To: <20110704.174619.1196575558517508080.davem@davemloft.net>
On 07/04/2011 06:46 PM, David Miller wrote:
> From: Mikhail Paremski<mparemm@gmail.com>
> Date: Mon, 4 Jul 2011 17:35:04 -0700
>
>> 1. What are the reasons to rout datagrams differently fromIPv4?
>
> It was just a design decision made when the ipv6 routing code
> was implemented.
Presumably there was some rationale for doing it differently than the
existing IPv4 code. Or was it just for fun?
>> 2. Where I could get details how IPv6 stack routes datagrams?
>
> By reading the source code.
While the source code has the final say, for someone new to a given part
of the kernel it is helpful to have a high-level view of the overall
flow. It's a lot easier to understand something if you can place it in
the overall scheme of of things.
Chris
--
Chris Friesen
Software Developer
GENBAND
chris.friesen@genband.com
www.genband.com
prev parent reply other threads:[~2011-07-05 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 0:35 IPv6 destination cache in Linux kernel Mikhail Paremski
2011-07-05 0:46 ` David Miller
2011-07-05 19:58 ` Chris Friesen [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=4E136D02.3060302@genband.com \
--to=chris.friesen@genband.com \
--cc=davem@davemloft.net \
--cc=mparemm@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 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.