netdev - [PATCH 0/3] Routing refinements.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Thu, 28 Apr 2011 22:25:06 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	netdev@...r.kernel.org
Subject: [PATCH 0/3] Routing refinements.

Don't initialize dst entries multiple times during allocation
and creation.

Use caller's flowi object in output route lookup paths.

These changes open the door to getting rid of several aspect of struct
rtcache.  For example, since the output route lookup updates the flow
keys, there is no need to use things like rt->rt_src since the same
information is present in the lookup flow key.

For example, connect() of stream sockets and sendmsg() of datagram
sockets do something like:

	rt = ip_route_connect(... &fl ...);
	...
	something using rt->rt_src

When we can now replace rt->rt_src with fl.saddr

Eventually all instance specific aspects of struct rtable can be
removed and we are left with a routing object that can exist as
a single instance pointed to directly from the routing table
nexthop slots.

The only part I don't have a clean vision on is the inetpeer and
metrics.  But I don't anticipate that being insurmountable.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html