From: Mitchell Blank Jr <mitch@sfgoth.com>
To: Maksim Krasnyanskiy <maxk@qualcomm.com>
Cc: Robert Love <rml@tech9.net>,
fisaksen@bewan.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spinlock not locked when unlocking in atm_dev_register
Date: Fri, 1 Mar 2002 15:06:09 -0800 [thread overview]
Message-ID: <20020301150609.A89500@sfgoth.com> (raw)
In-Reply-To: <20020301163936.7FA725F963@postfix2-2.free.fr> <20020301163936.7FA725F963@postfix2-2.free.fr> <1015020950.11295.25.camel@phantasy> <5.1.0.14.2.20020301143010.0d552be8@mail1.qualcomm.com>
In-Reply-To: <5.1.0.14.2.20020301143010.0d552be8@mail1.qualcomm.com>; from maxk@qualcomm.com on Fri, Mar 01, 2002 at 02:32:24PM -0800
Maksim Krasnyanskiy wrote:
> btw ATM locking seems to be messed up. Is anybody working on that ?
Yes, pretty badly. What we (the atm folks) really need to do for 2.5 is
rewrite a lot of code. The current driver model predates SMP in the kernel
and it's pretty much impossible to make a driver 100% SMP correct (although,
in practice, you can get pretty close and keep the races pretty tiny)
Really a lot of the driver model needs to be rethought.
As for maintainership I readily admit I haven't spent nearly as much time
as I would have liked on the ATM stuff in the last year or so. Too much
other work to do, etc. I'm really hoping to get some free time to play
with stuff in the next couple months... There are others actively working
on stuff. Particularly Paul Schroeder at IBM did a lot of good work on
the (long-suffering) userland tools.
Anyway I have been thinking that we should start kicking around ideas for
the next-generation ATM code. I'd recommend interested parties subscribe
to the linux-atm-general mailing list:
http://lists.sourceforge.net/lists/listinfo/linux-atm-general
-Mitch
prev parent reply other threads:[~2002-03-01 23:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 17:46 [PATCH] spinlock not locked when unlocking in atm_dev_register Frode Isaksen
2002-03-01 22:15 ` Robert Love
2002-03-04 8:29 ` Frode Isaksen
2002-03-04 18:58 ` Robert Love
2002-03-01 22:32 ` Maksim Krasnyanskiy
2002-03-01 22:35 ` Robert Love
2002-03-01 22:38 ` David S. Miller
2002-03-01 22:48 ` How to get kernel data using /proc system? Lei Wang
2002-03-02 0:28 ` [PATCH] spinlock not locked when unlocking in atm_dev_register Maksim Krasnyanskiy
2002-03-01 23:06 ` Mitchell Blank Jr [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=20020301150609.A89500@sfgoth.com \
--to=mitch@sfgoth.com \
--cc=fisaksen@bewan.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
--cc=rml@tech9.net \
/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