Re: [ANNOUNCE] NF-HIPAC: High Performance Packet Classification
Nivedita Singhvi (firstname.lastname@example.org)
Wed, 25 Sep 2002 17:50:11 -0700
"David S. Miller" wrote:
> From: "Nivedita Singhvi" <email@example.com>
> Date: 25 Sep 2002 17:06:53 -0700
> > Everything, from packet forwarding, to firewalling, to TCP socket
> > packet receive, can be described with routes. It doesn't make sense
> > for forwarding, TCP, netfilter, and encapsulation schemes to duplicate
> > all of this table lookup logic and in fact it's entirely superfluous.
> Are you saying combine the tables themselves?
> One of the tradeoffs would be serialization of the access, then,
> right? i.e. Much less stuff could happen in parallel? Or am I
> completely misunderstanding your proposal?
> In fact the exact opposite, such a suggested flow cache is about
> as parallel as you can make it.
> Even if the per-cpu toplevel flow cache idea were not implemented and
> we used the current top-level route lookup infrastructure, it is fully
> parallelized since the toplevel hash table uses per-hashchain locks.
> Please see net/ipv4/route.c:ip_route_input() and friends.
Well, true - we have per hashchain locks, but are we now adding
the times we need to lookup something on this chain because we now
have additional info other than the route, is what I was
> I don't understand why you think using the routing tables to their
> full potential would imply serialization. If you still believe this
> you have to describe why in more detail.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/