Files
linux/drivers
NeilBrown eea1bf384e md: Fix is_mddev_idle test (again).
There are two problems with is_mddev_idle.

1/ sync_io is 'atomic_t' and hence 'int'.  curr_events and all the
   rest are 'long'.
   So if sync_io were to wrap on a 64bit host, the value of
   curr_events would go very negative suddenly, and take a very
   long time to return to positive.

   So do all calculations as 'int'.  That gives us plenty of precision
   for what we need.

2/ To initialise rdev->last_events we simply call is_mddev_idle, on
   the assumption that it will make sure that last_events is in a
   suitable range.  It used to do this, but now it does not.
   So now we need to be more explicit about initialisation.

Signed-off-by: NeilBrown <neilb@suse.de>
2009-03-31 14:27:02 +11:00
..
2009-01-08 16:29:41 +00:00
2009-02-18 17:41:38 -08:00
2009-02-18 15:37:56 -08:00
2009-01-29 18:04:43 -08:00
2009-03-04 21:49:14 +10:00
2009-03-05 16:10:58 +01:00
2009-02-26 10:32:31 -08:00
2009-01-15 16:39:40 -08:00
2009-03-31 14:27:02 +11:00
2009-02-27 16:26:22 -08:00
2009-01-09 03:39:43 -05:00
2009-02-02 19:53:02 +03:00
2009-02-11 14:25:36 -08:00
2009-02-18 15:37:56 -08:00