On Sunday April 30, [email protected] wrote:
> NeilBrown <[email protected]> wrote:
> >
> >
> > When a md array has been idle (no writes) for 20msecs it is marked as
> > 'clean'. This delay turns out to be too short for some real
> > workloads. So increase it to 200msec (the time to update the metadata
> > should be a tiny fraction of that) and make it sysfs-configurable.
> >
> >
> > ...
> >
> > + safe_mode_delay
> > + When an md array has seen no write requests for a certain period
> > + of time, it will be marked as 'clean'. When another write
> > + request arrive, the array is marked as 'dirty' before the write
> > + commenses. This is known as 'safe_mode'.
> > + The 'certain period' is controlled by this file which stores the
> > + period as a number of seconds. The default is 200msec (0.200).
> > + Writing a value of 0 disables safemode.
> > +
>
> Why not make the units milliseconds? Rename this to safe_mode_delay_msecs
> to remove any doubt.
Because umpteen years ago when I was adding thread-usage statistics to
/proc/net/rpc/nfsd I used milliseconds and Linus asked me to make it
seconds - a much more "obvious" unit. See Email below.
It seems very sensible to me.
...
> > + msec = simple_strtoul(buf, &e, 10);
> > + if (e == buf || (*e && *e != '\n'))
> > + return -EINVAL;
> > + msec = (msec * 1000) / scale;
> > + if (msec == 0)
> > + mddev->safemode_delay = 0;
> > + else {
> > + mddev->safemode_delay = (msec*HZ)/1000;
> > + if (mddev->safemode_delay == 0)
> > + mddev->safemode_delay = 1;
> > + }
> > + return len;
>
> And most of that goes away.
Maybe it could go in a library :-?
NeilBrown
------------------------------------------------------------
From: Linus Torvalds <[email protected]>
To: Neil Brown <[email protected]>
cc: [email protected]
Subject: Re: PATCH knfsd - stats tidy up.
Date: Tue, 18 Jul 2000 12:21:12 -0700 (PDT)
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Tue, 18 Jul 2000, Neil Brown wrote:
>
> The following patch converts jiffies to milliseconds for output, and
> also makes the number wrap predicatably at 1,000,000 seconds
> (approximately one fortnight).
If no programs depend on the format, I actually prefer format changes like
this to be of the "obvious" kind. One such obvious kind is the format
0.001
which obviously means 0.001 seconds.
And yes, I'm _really_ sorry that a lot of the old /proc files contain
jiffies. Lazy. Ugly. Bad. Much of it my bad.
Doing 0.001 doesn't mean that you have to use floating point, in fact
you've done most of the work already in your ms patch, just splitting
things out a bit works well:
/* gcc knows to combine / and % - generate one "divl" */
unsigned int sec = time / HZ, msec = time % HZ;
msec = (msec * 1000) / HZ;
sprintf(" %d.%03d", sec, msec)
(It's basically the same thing you already do, except it doesn't
re-combine the seconds and milliseconds but just prints them out
separately.. And it has the advantage that if you want to change it to
microseconds some day, you can do so very trivially without breaking the
format. Plus it's readable as hell.)
Linus
-
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]
