linux/include/net/flow.h, branch v3.0

net: Order ports in same order as addresses in flow objects.

2011-04-01T01:03:35Z

For consistency. Signed-off-by: David S. Miller

net: Add helper flowi4_init_output().

2011-03-31T11:52:14Z

On-stack initialization via assignment of flow structures are expensive because GCC emits a memset() to clear the entire structure out no matter what. Add a helper for ipv4 output flow key setup which we can use to avoid the memset. Signed-off-by: David S. Miller

decnet: Convert to use flowidn where applicable.

2011-03-12T23:08:55Z

Signed-off-by: David S. Miller

net: Put fl6_* macros to struct flowi6 and use them again.

2011-03-12T23:08:55Z

Signed-off-by: David S. Miller

net: Put fl4_* macros to struct flowi4 and use them again.

2011-03-12T23:08:54Z

Signed-off-by: David S. Miller

net: Add flowi6_* member helper macros.

2011-03-12T23:08:52Z

Signed-off-by: David S. Miller

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

2011-03-12T23:08:47Z

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

net: Add flowiX_to_flowi() shorthands.

2011-03-12T23:08:47Z

This is just a shorthand which will help in passing around AF specific flow structures as generic ones. Signed-off-by: David S. Miller

net: Break struct flowi out into AF specific instances.

2011-03-12T23:08:46Z

Now we have struct flowi4, flowi6, and flowidn for each address family. And struct flowi is just a union of them all. It might have been troublesome to convert flow_cache_uli_match() but as it turns out this function is completely unused and therefore can be simply removed. Signed-off-by: David S. Miller

net: Make flowi ports AF dependent.

2011-03-12T23:08:46Z

Create two sets of port member accessors, one set prefixed by fl4_* and the other prefixed by fl6_* This will let us to create AF optimal flow instances. It will work because every context in which we access the ports, we have to be fully aware of which AF the flowi is anyways. Signed-off-by: David S. Miller