From: Roman Kagan <rkagan@mail.ru>
To: usbatm@lists.infradead.org, netdev@oss.sgi.com,
linux-atm-general@lists.sourceforge.net
Subject: Re: [Linux-ATM-General] [RFC][PATCH] Very basic sysfs support for ATM devices (updated)
Date: Mon, 7 Feb 2005 12:45:18 +0300 [thread overview]
Message-ID: <20050207094517.GC2360@katya> (raw)
In-Reply-To: <200502071003.09211.duncan.sands@math.u-psud.fr>
On Mon, Feb 07, 2005 at 10:03:08AM +0100, Duncan Sands wrote:
> this is a long-standing problem with ATM device initialisation: the device
> becomes available before the struct atm_dev is initialised!
> [...]
> In the past, this race was only a theoretical
> problem for SMP machines; but with your patch it hits everyone.
Indeed. OTOH at a first glance splitting the ATM device initialisation
API into allocation and registration doesn't look a terribly difficult
thing, it would require fairly local changes in the drivers.
Unless Chas' move to struct net_device is alredy knocking on the door,
of course.
Cheers,
Roman.
prev parent reply other threads:[~2005-02-07 9:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050119174543.GA2418@katya>
2005-01-21 8:51 ` [RFC][PATCH] Very basic sysfs support for ATM devices (updated) Roman Kagan
2005-02-04 18:11 ` [Linux-ATM-General] " chas williams - CONTRACTOR
2005-02-04 18:27 ` matthieu castet
2005-02-04 18:50 ` chas williams - CONTRACTOR
2005-02-04 20:13 ` Roman Kagan
2005-02-06 1:33 ` chas williams - CONTRACTOR
2005-02-06 19:19 ` Roman Kagan
2005-02-08 15:02 ` chas williams - CONTRACTOR
2005-02-08 16:45 ` Roman Kagan
2005-02-07 9:03 ` Duncan Sands
2005-02-07 9:45 ` Roman Kagan [this message]
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=20050207094517.GC2360@katya \
--to=rkagan@mail.ru \
--cc=linux-atm-general@lists.sourceforge.net \
--cc=netdev@oss.sgi.com \
--cc=usbatm@lists.infradead.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.