lkml.org 
[lkml]   [2000]   [Nov]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Module open() problems, Linux 2.4.0
Date
From
> > I suppose. Look at what you just stated! This means that a reported
> > value is now worthless.
>
> Correct. And it was always worthless.

Right. The module "use count" is not a use count, it's a lock count.

E.g. a driver may well increase this counter on open and then again
when in a particular ioctl routine, if this situation isn't already
locked right by the kernel. This can happen when a driver has more
than one access point from user space, look at slip_open() in slip.c
from 2.2.

> It's the same de-facto standard as bogo-mips ~= CPU MHz. It was so,
> but it was neither intended nor documented so.

Remember the Landmark Test and those silly CPU-speed displays
configured to show "Landmark MHz"? :-)

Olaf
-
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/

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