lkml.org 
[lkml]   [2000]   [Sep]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Q: sock output serialization
Date
From
>    I sense that usually, LAPB handles this issue at a different
> level, in the hardware? Does LAPB specify how to maintain
> reliably delivery and could we hook into this "how" when we
> need to drop LAPB frames? Perhaps it is too late by the time
> netif_rx is dealing with it.

LAPB maintains a window of (normally 8) frames. When a frame is accepted it
as acked (RR) or if there is no room it is rejected (RNR). Once it has been
accepted with an RR it can from that point onwards not get lost.

> LAPB sounds like quite a broken protocol at the moment... But I'm
> sure there are details which will emerge and clear this all up.

LAPB isnt broken, its actually rather clever and ideal for tiny low power
devices


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:38    [W:0.032 / U:0.920 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site