From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Tobias Ringstrom <tori@tellus.mine.nu>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [CFT] dmfe.c network driver update for 2.4
Date: Thu, 16 Nov 2000 16:56:22 -0500 [thread overview]
Message-ID: <3A145806.FF5F0066@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0011162241450.23936-100000@svea.tellus>
Tobias Ringstrom wrote:
> On Wed, 15 Nov 2000, Jeff Garzik wrote:
> > Tobias Ringstrom wrote:
> > > I have updated the dmfe.c network driver for 2.4.0-test by adding proper
> > > locking (I hope), and also made transmission much efficient.
> > Would you mind creating a separate patch that -just- correcting the SMP
> > safety? That makes it much easier to review and apply, and then we can
> > consider the other changes...
> Such a patch will appear shortly. I and Frank Davis are currently merging
> our patches for dmfe.c.
Thanks a bunch.
> [Actually, I just added reasonable locks while my main goal was to improve
> performance. I did not realize that there was such a strong need for SMP
> safety (since it has been broken in that regard for a long time, without
> anyone fixing it).]
The kernel driver APIs are designed so that SMP and UP cases are equally
high-performance, and portable beyond the x86 platform.
Pretty much all ISA and PCI drivers need to be portable and SMP safe...
if not so, it's a bug. That said, there is certainly more motivation to
make a popular PCI driver is SMP safe than an older ISA driver. And
portability is [IMHO] less of a priority than SMP safety, though it
depends on the hardware being supported.
Regards,
Jeff
--
Jeff Garzik |
Building 1024 | The chief enemy of creativity is "good" sense
MandrakeSoft | -- Picasso
-
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/
next prev parent reply other threads:[~2000-11-16 22:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-15 20:34 [CFT] dmfe.c network driver update for 2.4 Tobias Ringstrom
2000-11-15 20:49 ` Frank Davis
2000-11-15 22:21 ` Jeff Garzik
2000-11-16 21:50 ` Tobias Ringstrom
2000-11-16 21:56 ` Jeff Garzik [this message]
2000-11-17 9:20 ` Tobias Ringstrom
2000-11-17 22:28 ` Frank Davis
2000-11-17 22:30 ` Jeff Garzik
2000-11-19 0:05 ` Tobias Ringstrom
2000-11-19 0:10 ` Jeff Garzik
2000-11-21 13:42 ` Peter Samuelson
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=3A145806.FF5F0066@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tori@tellus.mine.nu \
/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