From 018bee6afb0a7b9e09616a52f2f24f65fcf07322 Mon Sep 17 00:00:00 2001 From: Denis Vlasenko Date: Tue, 15 Jul 2008 22:33:13 +0000 Subject: mdev: support for serializing hotplug function old new delta mdev_main 503 647 +144 --- docs/mdev.txt | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) (limited to 'docs/mdev.txt') diff --git a/docs/mdev.txt b/docs/mdev.txt index 1a97be4ce..555c2bf61 100644 --- a/docs/mdev.txt +++ b/docs/mdev.txt @@ -95,3 +95,26 @@ properly initialize a device. Place all such firmware files into the filename of the firmware which mdev will load out of /lib/firmware/ and into the kernel via the sysfs interface. The exact filename is hardcoded in the kernel, so look there if you need to know how to name the file in userspace. + +------------ + SEQUENCING +------------ + +Kernel does not serialize hotplug events. It increments SEQNUM environmental +variable for each successive hotplug invocation. Normally, mdev doesn't care. +This may reorder hotplug and hot-unplug events, with typical symptoms of +device nodes sometimes not created as expected. + +However, if /dev/mdev.seq file is found, mdev will compare its +contents with SEQNUM. It will retry up to two seconds, waiting for them +to match. If they match exactly (not even trailing '\n' is allowed), +or if two seconds pass, mdev runs as usual, then it rewrites /dev/mdev.seq +with SEQNUM+1. + +IOW: this will serialize concurrent mdev invocations. + +If you want to activate this feature, execute "echo >/dev/mdev.seq" prior to +setting mdev to be the hotplug handler. This writes single '\n' to the file. +NB: mdev recognizes /dev/mdev.seq consisting of single '\n' characher +as a special case. IOW: this will not make your first hotplug event +to stall for two seconds. -- cgit v1.2.3