lkml.org 
[lkml]   [2000]   [Jan]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [RFC] change in /proc/devices
Date
From
> > I think perhaps we need a module_lock that forbids just module load/unload
> > when its held. A reader/writer lock with the unload as the writer and
> > the rest as readers ?
>
> IMO I have a better variant. I'm doing an equivalent of routing for the
> device numbers. I.e. maintain a tree of devno blocks. The lowest layer

You are solving only a tiny fraction of the problem. The block/char device
case is far from the entire problem that solving the module problem seperately
might be a good idea ?

Alan


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

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