linux-stable.git/include/net/ip_fib.h, branch linux-2.6.39.y

ipv4: Fix nexthop caching wrt. scoping.

2011-03-25T01:06:47+00:00

Move the scope value out of the fib alias entries and into fib_info,
so that we always use the correct scope when recomputing the nexthop
cached source address.

Reported-by: Julian Anastasov 
Signed-off-by: David S. Miller

ipv4: Invalidate nexthop cache nh_saddr more correctly.

2011-03-25T00:42:21+00:00

Any operation that:

1) Brings up an interface
2) Adds an IP address to an interface
3) Deletes an IP address from an interface

can potentially invalidate the nh_saddr value, requiring
it to be recomputed.

Perform the recomputation lazily using a generation ID.

Reported-by: Julian Anastasov 
Signed-off-by: David S. Miller

ipv4: Pass ipv4 flow objects into fib_lookup() paths.

2011-03-12T23:08:47+00:00

To start doing these conversions, we need to add some temporary
flow4_* macros which will eventually go away when all the protocol
code paths are changed to work on AF specific flowi objects.

Signed-off-by: David S. Miller

ipv4: Kill flowi arg to fib_select_multipath()

2011-03-11T01:03:45+00:00

Completely unused.

Signed-off-by: David S. Miller

ipv4: Fix scope value used in route src-address caching.

2011-03-08T19:03:21+00:00

We have to use cfg->fc_scope not the final nh_scope value.

Reported-by: Julian Anastasov 
Signed-off-by: David S. Miller

ipv4: Cache source address in nexthop entries.

2011-03-08T04:54:48+00:00

When doing output route lookups, we have to select the source address
if the user has not specified an explicit one.

First, if the route has an explicit preferred source address
specified, then we use that.

Otherwise we search the route's outgoing interface for a suitable
address.

This search can be precomputed and cached at route insertion time.

The only missing part is that we have to refresh this precomputed
value any time addresses are added or removed from the interface, and
this is accomplished by fib_update_nh_saddrs().

Signed-off-by: David S. Miller

ipv4: Use const'ify fib_result deep in the route call chains.

2011-02-17T23:54:42+00:00

The only troublesome bit here is __mkroute_output which wants
to override res->fi and res->type, compute those in local
variables instead.

Signed-off-by: David S. Miller

ipv4: Mark fib_combine_itag()'s 'res' arg as const.

2011-02-17T23:52:59+00:00

Signed-off-by: David S. Miller

ipv4: Update some fib_hash centric interface names.

2011-02-01T23:35:25+00:00

fib_hash_init() --> fib_trie_init()
fib_hash_table() --> fib_trie_table()

Signed-off-by: David S. Miller

ipv4: Consolidate all default route selection implementations.

2011-02-01T00:16:50+00:00

Both fib_trie and fib_hash have a local implementation of
fib_table_select_default().  This is completely unnecessary
code duplication.

Since we now remember the fib_table and the head of the fib
alias list of the default route, we can implement one single
generic version of this routine.

Looking at the fib_hash implementation you may get the impression
that it's possible for there to be multiple top-level routes in
the table for the default route.  The truth is, it isn't, the
insert code will only allow one entry to exist in the zero
prefix hash table, because all keys evaluate to zero and all
keys in a hash table must be unique.

Signed-off-by: David S. Miller