Leif Sawyer <[EMAIL PROTECTED]> writes:
> > > Jesse Pollard replies:
> > Removing/no-oping the reset code would make the module
> > SMALLER, and simpler.
> NO. Don't remove the functionality that is required.
Please explain where counter reset capability provides any
functionality that is not already available without it.
You might want to read RFC2724 ``Traffic Flow Measurement''.
Search for ``reset''.
Counter resets have always caused problems, that's why mission
critical counters never have a reset. Have you ever seen an
electricity, gas or water meter with a reset? The same reasoning
applies when you have accounting rules that are used to charge
customers for traffic volume.
> Fix your userspace applications to behave correctly. If _you_
> require your userspace applications to not clear counters, then fix
> the application.
You are confused. What would you say if a close() by another,
unrelated application closed all open descriptors for that file,
including the one you just opened? Just fix your applications?
--
Manfred Bartz
-
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/
