public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
To: lsawyer@gci.com,
	Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>,
	Ian.Stirling@tomcat.admin.navo.hpc.mil, root@mauve.demon.co.uk,
	linux-kernel@vger.kernel.org
Subject: RE: IP Acounting Idea for 2.5
Date: Tue, 17 Apr 2001 16:25:32 -0500 (CDT)	[thread overview]
Message-ID: <200104172125.QAA09568@tomcat.admin.navo.hpc.mil> (raw)

---------  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.

             reply	other threads:[~2001-04-17 21:25 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-17 21:25 Jesse Pollard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-17 23:06 IP Acounting Idea for 2.5 Leif Sawyer
2001-04-17 21:48 Leif Sawyer
2001-04-17 22:58 ` Manfred Bartz
2001-04-17 23:13   ` Alan Cox
2001-04-17 23:35     ` Manfred Bartz
2001-04-18  0:02       ` Alan Cox
2001-04-20  2:51         ` Ton Hospel
2001-05-01 23:13           ` Mark van Walraven
2001-04-18  8:16     ` Kenneth Johansson
2001-04-18 14:45       ` Jonathan Lundell
2001-04-17 19:09 Leif Sawyer
2001-04-17 19:37 ` Matti Aarnio
2001-04-18 13:49   ` Michael Clark
2001-04-17 22:32 ` Manfred Bartz
2001-04-17 18:31 Jesse Pollard
2001-04-17 16:57 Leif Sawyer
2001-04-17 12:28 Jesse Pollard
2001-04-16 23:52 Leif Sawyer
2001-04-16 22:35 Leif Sawyer
2001-04-16 23:42 ` Ian Stirling
2001-04-17  1:13 ` Manfred Bartz
2001-04-17 10:34 ` Olaf Titz
2001-04-16 21:53 David Findlay
2001-04-16  0:21 ` Michael Clark
2001-04-16  0:40 ` Mike A. Harris
2001-04-16 22:46   ` David Findlay
2001-04-16  0:50     ` Mike A. Harris
2001-04-16  1:58       ` swds.mlowe
2001-04-16  1:24     ` Matti Aarnio
2001-04-16  2:07     ` Manfred Bartz
2001-04-16  9:43       ` Russell King
2001-04-16 22:24         ` Manfred Bartz
2001-04-17 10:29         ` Olaf Titz
2001-04-17  1:43       ` Harald Welte
2001-04-17  2:37         ` Manfred Bartz
2001-04-17  6:56         ` Henning P. Schmiedehausen
2001-04-20 16:17           ` Harald Welte
2001-04-20 21:00             ` Henning P. Schmiedehausen
2001-04-16 11:21     ` Andreas Ferber
2001-04-16  2:40 ` Dax Kelson
2001-04-17  1:39 ` Harald Welte

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200104172125.QAA09568@tomcat.admin.navo.hpc.mil \
    --to=pollard@tomcat.admin.navo.hpc.mil \
    --cc=Ian.Stirling@tomcat.admin.navo.hpc.mil \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsawyer@gci.com \
    --cc=root@mauve.demon.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox