All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: chas@locutus.cmf.nrl.navy.mil
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][ATM] add reference counting to atm_dev
Date: Fri, 16 May 2003 13:44:06 -0700 (PDT)	[thread overview]
Message-ID: <20030516.134406.74725937.davem@redhat.com> (raw)
In-Reply-To: <200305161605.h4GG5fGi018381@locutus.cmf.nrl.navy.mil>

   From: chas williams <chas@locutus.cmf.nrl.navy.mil>
   Date: Fri, 16 May 2003 12:05:41 -0400
   
   true.  however, i think i would like to do both at once.  but it seems 
   like just replacing atm_dev_lock with rtnl would probably be enough
   for right now.
   
You still need to have a spinlock to guard the actual insert/delete
from the list so that readers don't see inconsistent data.

Really, look at how netdevices are managed, searched, etc.

   >Ok, I'll apply this.  But long term we really need to clean out
   >the cobwebs here, use RTNL, do solid module refcounting etc.
   
   are you referring to the other bits of linux-atm like br2684, lane,
   mpoa, pppoatm or something else?
   
The whole ATM stack needs to be doing sane things in this area, yes.

  reply	other threads:[~2003-05-16 20:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14 20:20 [PATCH][ATM] add reference counting to atm_dev chas williams
2003-05-14 20:36 ` David S. Miller
2003-05-14 22:16   ` chas williams
2003-05-15  4:30     ` David S. Miller
2003-05-15 14:39       ` chas williams
2003-05-15 20:10         ` David S. Miller
2003-05-15 20:20           ` chas williams
2003-05-16  0:14             ` David S. Miller
2003-05-16 16:05               ` chas williams
2003-05-16 20:44                 ` David S. Miller [this message]
2003-05-16  0:19             ` David S. Miller
2003-05-14 20:59 ` Greg KH
2003-05-14 21:02   ` David S. Miller
2003-05-14 21:57     ` Greg KH
2003-05-14 22:21   ` chas williams
2003-05-15  5:20     ` Greg KH
2003-05-15 14:32       ` chas williams
2003-05-15 19:09         ` Greg KH
2003-05-15 19:17           ` chas williams
2003-05-20 12:25             ` Duncan Sands
2003-05-16  0:12         ` David S. Miller
2003-05-16 14:40         ` Duncan Sands
2003-05-16 15:39           ` chas williams
2003-05-16 18:48             ` Francois Romieu
2003-05-22 17:59   ` Linux 2.4 scheduler is RTOS-alike? Ming Lei
2003-05-22 20:01   ` Ming Lei
2003-05-22 20:37     ` Elladan
2003-05-22 20:47     ` Elladan

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=20030516.134406.74725937.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=chas@locutus.cmf.nrl.navy.mil \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.