Andi> On Wed, Nov 11, 1998 at 08:27:45PM +0100, Henner Eisen
Andi> wrote:
>> Will the dst entry also affect protocols that use
>> dev_queue_xmit() method? And is the latter obsolete and should
>> be replaced with the destination output method as done in
>> ipv[46]?
Andi> The second. Of course it is not required to port all
Andi> protocols to the dst_entry abstraction, but if it is done it
Andi> is a useful framework to share common information between
Andi> sockets pointing to the same destination and to organize the
Andi> protocol stack.
I once looked at the dst_* stuff but is was difficult to figure out
how it should be used (and I did not really figure out yet). The only usage
until now seemed to be inside the tcp/ip stack. This is obviously
the most important stack but also the most complex one.
Thus, looking at the tcp/ip implementation does not seem to be the most
convenient method to learn about it.
Is there some other information on that topic availabe somewhere?
I was also wondering whether the design of the dst_* code took connection
oriented datalink protocols (i.e. as provided by lapb devices and needed
by the X.25 PLP) into account. I realised there are output and connected_output
methods but those seem to be used by/related to the link's address resolution
(protocol) state.
Henner
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/