lkml.org 
[lkml]   [1998]   [Nov]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] Compilation fixes for 2.1.127
On Thu, Nov 12, 1998 at 09:12:40PM +0100, Henner Eisen wrote:
> >>>>> "Andi" == Andi Kleen <ak@muc.de> writes:
>
> 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?

Only information I know of - although it is a bit outdated - is included
in some emails from Alexey Kuznetsov on the netdev mailing list. See
http://www.wcug.wwu.edu/lists/netdev/199611/msg00125.html and the other
mails in this thread.

> 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.

I think you're confusing the destination cache with the neighbour cache
here (net/dst.h vs net/neighbour.h). They're different things. The neighbour
cache is a generalisation of the ARP table and is used only by lower
layers, while the destination cache (or "virtual path cache") generally
describes the way of the packet inside the stack.

-Andi

-
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/

\
 
 \ /
  Last update: 2005-03-22 13:45    [W:0.088 / U:0.052 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site