linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Werner Almesberger <wa@almesberger.net>
To: chas williams <chas@locutus.cmf.nrl.navy.mil>
Cc: "David S. Miller" <davem@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][ATM] make atm (and clip) modular + try_module_get()
Date: Wed, 5 Mar 2003 12:52:31 -0300	[thread overview]
Message-ID: <20030305125230.B525@almesberger.net> (raw)
In-Reply-To: <200303051528.h25FSqGi006413@locutus.cmf.nrl.navy.mil>; from chas@locutus.cmf.nrl.navy.mil on Wed, Mar 05, 2003 at 10:28:52AM -0500

chas williams wrote:
> sk->receieve_queue i suspect -- more on that later) while the skb are
> moved to copy.  i am afraid i dont know much about how the clip driver
> operates.

What's happening there is that new CLIP connections start as normal
native ATM VCs, owned by atmarpd. When atmarpd clears them for IP
traffic, all the data that has been queued so far (i.e. any ATMARP
messages, and any IP - typically I'd expect to find a SYN there)
is removed from the native ATM VC's queue, and fed into the non-ATM
part of the stack, for de-encapsulation, etc.

Note that ATMARP will be delivered again to the "native ATM" VC's
queue, because that's how atmarpd receives ATMARP messages.

Figure 6 of http://www.almesberger.net/cv/papers/atm_on_linux.ps
shows the overall design (some details have changed since then,
though).

- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, Buenos Aires, Argentina         wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/

  parent reply	other threads:[~2003-03-05 15:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-03 22:20 [PATCH][ATM] make atm (and clip) modular + try_module_get() chas williams
2003-03-03 22:26 ` chas williams
2003-03-04  0:28 ` Kai Germaschewski
2003-03-05 14:43   ` chas williams
2003-03-05 15:58     ` Kai Germaschewski
2003-03-05 16:05       ` chas williams
2003-03-05 16:11         ` Kai Germaschewski
2003-03-05 16:24           ` chas williams
2003-03-05 16:40             ` Kai Germaschewski
2003-03-05 16:26       ` Roman Zippel
2003-03-04  2:07 ` Werner Almesberger
2003-03-05 14:47   ` chas williams
2003-03-05 14:31     ` David S. Miller
2003-03-05 15:08       ` chas williams
2003-03-05 14:53         ` David S. Miller
2003-03-05 15:28           ` chas williams
2003-03-05 15:12             ` David S. Miller
2003-03-05 15:43               ` chas williams
2003-03-05 15:52             ` Werner Almesberger [this message]
2003-03-06 20:44               ` chas williams
2003-03-06 21:02                 ` Werner Almesberger
2003-03-06 23:36                   ` chas williams

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030305125230.B525@almesberger.net \
    --to=wa@almesberger.net \
    --cc=chas@locutus.cmf.nrl.navy.mil \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).