From: David Miller <davem@davemloft.net>
To: ja@ssi.bg
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 11/16] ipv4: Cache input routes in fib_info nexthops.
Date: Mon, 23 Jul 2012 14:06:57 -0700 (PDT) [thread overview]
Message-ID: <20120723.140657.730477254993765697.davem@davemloft.net> (raw)
In-Reply-To: <20120723.125837.2165279339112720363.davem@davemloft.net>
From: David Miller <davem@davemloft.net>
Date: Mon, 23 Jul 2012 12:58:37 -0700 (PDT)
> The only time skb->dev->ifindex can change from rt->rt_iif is when we
> demux a tunnel, but at that point we would first reinject and do
> another route lookup, at which point rt->rt_iif would match again.
>
> And this is the intended semantic of this field anyways.
Ok Julian, you probably already say the DIRECTSRC patches and upcoming
are two patches to take care of the rt->rt_iif thing.
next prev parent reply other threads:[~2012-07-23 21:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 21:26 [PATCH 11/16] ipv4: Cache input routes in fib_info nexthops David Miller
2012-07-23 9:13 ` Julian Anastasov
2012-07-23 20:00 ` Julian Anastasov
2012-07-23 19:58 ` David Miller
2012-07-23 21:06 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-19 21:35 David Miller
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=20120723.140657.730477254993765697.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ja@ssi.bg \
--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).