From: David Miller <davem@davemloft.net>
To: netdev@vger.kernel.org
Subject: [PATCH 0/5] More rt->rt_{src,dst} removals.
Date: Wed, 04 May 2011 13:19:34 -0700 (PDT) [thread overview]
Message-ID: <20110504.131934.246537941.davem@davemloft.net> (raw)
After this set the number of uses of rt->rt_{src,dst} are very small.
One case to hit still will need a slight rearrangement of how we do
SRR handling, since SRR handling on input pops the nexthop and thus
creates situations where iph->daddr != rt->rt_dst and thus eliminates
the posibility of converting the rt->rt_dst access in ip_forward().
Another class of remaining cases occur in situations where we can
fetch the saddr/daddr from the inet socket.
Soon, all that will be left are the assignments and netlink dump code
cases in net/ipv4/route.c
reply other threads:[~2011-05-04 20:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20110504.131934.246537941.davem@davemloft.net \
--to=davem@davemloft.net \
--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).