On 4/25/05, Evgeniy Polyakov <[email protected]> wrote:
> While thinking about locking schema
> with respect to sysfs files I recalled,
> why I implemented such a logic -
> now one can _always_ remove _any_ module
> [corresponding object is removed from accessible
> pathes and waits untill all exsting users are gone],
> which is very good - I really like it in networking model,
> while with whole device driver model
> if we will read device's file very quickly
> in several threads we may end up not unloading it at all.
I am sorrry, that is complete bull*. sysfs also allows removing
modules at an arbitrary time (and usually without annoying "waiting
for refcount" at that)... You just seem to not understand how driver
code works, thus the need of inventing your own schema.
BTW, I am looking at the connector code ATM and I am just amazed at
all wied refounting stuff that is going on there. what a single
actomic_dec_and_test() call without checkng reurn vaue is supposed to
do again?
--
Dmitry
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
