[lkml]   [2000]   [Nov]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Locking Between User Context and Soft IRQs in 2.4.0
On Sat, Nov 04, 2000 at 04:45:33AM -0500, Jeff Garzik wrote:
> > * What about dev->open and dev->stop ?
> Sleep all you want, we'll leave the light on for ya.

... but make sure you have no module unload races (or at least not too
huge holes, some are probably unavoidable with the current network
driver interface, e.g. without moving module count management a bit up).
This means you should do MOD_INC_USE_COUNT very early at least to
minimize the windows (and DEC_USE_COUNT very late)

> dev->do_ioctl:
> Locking: Inside rtnl_lock() semaphore.
> Sleeping: OK

Just make sure you lock against your interrupt and xmit threads.

> Locking: Inside dev->xmit_lock spinlock.
> Sleeping: NO[1]
> NOTE [1]: On principle, you should not sleep when a spinlock is held.
> However, since this spinlock is per-net-device, we only block ourselves
> if we sleep, so the effect is mitigated.

Sounds like dangerous advice.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:45    [W:0.112 / U:0.248 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site