From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Steven_Snyder@3com.com, linux-kernel@vger.kernel.org
Subject: Re: Porting Linux v2.2.x Ethernet driver to v2.4.x?
Date: Thu, 09 Nov 2000 13:12:45 -0500 [thread overview]
Message-ID: <3A0AE91D.AC074BAE@mandrakesoft.com> (raw)
In-Reply-To: <88256992.00632296.00@hqoutbound.ops.3com.com> <3A0AE88D.FCA19A5A@mandrakesoft.com>
[-- Attachment #1: Type: text/plain, Size: 252 bytes --]
...and the attached document, referred to in the previous mail. :) I
think I posted this recently, but it's small so a repost is no big deal.
--
Jeff Garzik |
Building 1024 | Would you like a Twinkie?
MandrakeSoft |
[-- Attachment #2: netdevices.txt --]
[-- Type: text/plain, Size: 742 bytes --]
Network Devices, the Kernel, and You!
Introduction
============
The following is a random collection of documentation regarding
network devices.
struct net_device synchronization rules
=======================================
dev->open:
Locking: Inside rtnl_lock() semaphore.
Sleeping: OK
dev->stop:
Locking: Inside rtnl_lock() semaphore.
Sleeping: OK
dev->do_ioctl:
Locking: Inside rtnl_lock() semaphore.
Sleeping: OK
dev->get_stats:
Locking: Inside dev_base_lock spinlock.
Sleeping: NO
dev->hard_start_xmit:
Locking: Inside dev->xmit_lock spinlock.
Sleeping: NO
dev->tx_timeout:
Locking: Inside dev->xmit_lock spinlock.
Sleeping: NO
dev->set_multicast_list:
Locking: Inside dev->xmit_lock spinlock.
Sleeping: NO
next prev parent reply other threads:[~2000-11-09 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-09 18:01 Porting Linux v2.2.x Ethernet driver to v2.4.x? Steven_Snyder
2000-11-09 18:10 ` Jeff Garzik
2000-11-09 18:12 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-09 18:10 Dunlap, Randy
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=3A0AE91D.AC074BAE@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=Steven_Snyder@3com.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