Messages in this thread | | | Date | Tue, 17 Apr 2001 16:25:32 -0500 (CDT) | From | Jesse Pollard <> | Subject | RE: IP Acounting Idea for 2.5 |
| |
--------- Received message begins Here ---------
> > Jesse Pollard replies: > to Leif Sawyer who wrote: > >> Besides, what would be gained in making the counters RO, if > >> they were cleared every time the module was loaded/unloaded? > > > > 1. Knowlege that the module was reloaded. > > 2. Knowlege that the data being measured is correct > > 3. Having reliable measures > > 4. being able to derive valid statistics > > .... > > Good. Now that we have valid objectives to reach, which of these > are NOT met by making the fixes entirely in userspace, say by > incorporating a wrapper script to ensure that no external applications > can flush the table counters? > > They're still all met, right?
Nope - some of the applications that may be purchased do not have to go through the scripts to reset the counters. They just need access to the counters, and reset is built into the applications. This violates all 4 objectives.
> And we haven't had to fill the kernel with more cruft.
Removing/no-oping the reset code would make the module SMALLER, and simpler.
------------------------------------------------------------------------- Jesse I Pollard, II Email: pollard@navo.hpc.mil
Any opinions expressed are solely my own. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |