[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4846067C.1020807@sngx.net>
Date: Tue, 03 Jun 2008 22:05:32 -0500
From: James Cammarata <jimi@...x.net>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
CC: Bill Fink <billfink@...dspring.com>, linux-kernel@...r.kernel.org,
Linux Netdev List <netdev@...r.kernel.org>
Subject: Re: [PATCH] net: add ability to clear stats via ethtool - e1000/pcnet32
> I used to work in a large ISP - it was a huge concern then and was
> enforced and managed by the less effective 'do you like your kneecaps'
> approach to permissions.
I work at a large ISP now, and you're absolutely right. You don't just go
around resetting interface counters on backbone routers for the hell of it,
and we never do it without customer permission while troubleshooting an
issue with a connection, that is why I said I thought it was a non-argument.
There seems to be an irrational fear of counter-based anarchy here.
> Its basically impossible to write a correct non-racy application which
> zeros kernel statistics and then measures the change, because you cannot
> know another application did the same while you were running.
>
> This is the most basic and blindingly obvious stuff. You should not be
> able to zero the kernel stats just because you can't work perl.
I've already said I'd drop the issue 4+ days ago, and that I'd be more
than happy to do it in userland as you suggested, my point was simply that
adding it to only one userland tool will lead to inconsistencies. It is not
an issue of being able to "work perl" or not.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists