From: Jeff Garzik <jgarzik@pobox.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: netdev@oss.sgi.com, akpm@zip.com.au
Subject: Network interface synchronization docs
Date: Mon, 02 Dec 2002 22:33:20 -0500 [thread overview]
Message-ID: <3DEC2600.2070306@pobox.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 673 bytes --]
I just updated Documentation/networking/netdevices.txt locally to the
attached file, which describes the synchronization rules for net drivers
in the 2.4.x and 2.5.x kernels. (Astute readers will notice a striking
similarity to 2.2.x locking rules as well)
Comments and corrections to the attached doc requested. I realize it's
not much right now, but this is core info I want to make sure is
correct, and that everyone agrees on.
Thanks to Robert Olsson for a pointer about dev->poll().
Future notes: this doc will hopefully expand in time to describe not
only the netdevice API but also standard ethernet and net driver
practices. Patches welcome!
Jeff
[-- Attachment #2: netdevices.txt --]
[-- Type: text/plain, Size: 1053 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:
Synchronization: rtnl_lock() semaphore.
Context: process
dev->stop:
Synchronization: rtnl_lock() semaphore.
Context: process
Notes: netif_running() is guaranteed false when this is called
dev->do_ioctl:
Synchronization: rtnl_lock() semaphore.
Context: process
dev->get_stats:
Synchronization: dev_base_lock rwlock.
Context: nominally process, but don't sleep inside an rwlock
dev->hard_start_xmit:
Synchronization: dev->xmit_lock spinlock.
Context: BHs disabled
dev->tx_timeout:
Synchronization: dev->xmit_lock spinlock.
Context: BHs disabled
dev->set_multicast_list:
Synchronization: dev->xmit_lock spinlock.
Context: BHs disabled
dev->poll:
Synchronization: __LINK_STATE_RX_SCHED bit in dev->state. See
dev_close code and comments in net/core/dev.c for more info.
Context: softirq
reply other threads:[~2002-12-03 3:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3DEC2600.2070306@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).