From: Keith Owens <kaos@ocs.com.au>
To: Jeff Garzik <jgarzik@mandrakesoft.mandrakesoft.com>,
Donald Becker <becker@scyld.com>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [RFC] Configuring synchronous interfaces in Linux
Date: Mon, 04 Dec 2000 07:41:06 +1100 [thread overview]
Message-ID: <4910.975876066@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Mon, 04 Dec 2000 07:29:10 +1100." <4778.975875350@ocs3.ocs-net>
On Mon, 04 Dec 2000 07:29:10 +1100,
Keith Owens <kaos@ocs.com.au> wrote:
>On Sun, 3 Dec 2000 07:43:01 -0600 (CST),
>Jeff Garzik <jgarzik@mandrakesoft.mandrakesoft.com> wrote:
>>On Sun, 3 Dec 2000, Keith Owens wrote:
>>> If you go down this path, please add a standard performance monitoring
>>> method to query the current capacity of an interface.
>>Well, ethtool interface supports reporting media selection as well as
>>[re]setting media setting. I dunno if we could report what capacity
>>an interface is handling without adding code to hot paths...
>
>You calculate the capacity during ifconfig up or during speed change.
>That is not on the hot path.
Replying to my own mail, I just realised it was ambiguous. By "current
capacity" I mean the maximum capacity of the link based on the current
settings. We can get capacity _used_ from the byte counters, we do not
have a figure for maximum capacity.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-03 21:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-30 19:16 [RFC] Configuring synchronous interfaces in Linux Ivan Passos
2000-12-01 9:01 ` Francois romieu
2000-12-01 10:32 ` Chris Wedgwood
2000-12-01 11:00 ` Christoph Hellwig
2000-12-01 12:30 ` Xavier Bestel
2000-12-01 12:07 ` Russell King
2000-12-01 13:00 ` Francois Romieu
2000-12-02 16:09 ` Donald Becker
2000-12-02 18:59 ` Chris Wedgwood
2000-12-02 19:07 ` Jeff Garzik
2000-12-02 19:46 ` Russell King
2000-12-02 20:02 ` Philip Blundell
2000-12-03 5:47 ` Chris Wedgwood
2000-12-03 11:10 ` Philip Blundell
2000-12-03 11:27 ` Russell King
2000-12-03 0:20 ` Keith Owens
2000-12-03 13:43 ` Jeff Garzik
2000-12-03 20:29 ` Keith Owens
2000-12-03 20:41 ` Keith Owens [this message]
2000-12-02 19:48 ` Donald Becker
2000-12-07 8:44 ` Chris Wedgwood
2000-12-01 13:44 ` Philip Blundell
2000-12-01 12:15 ` Francois Romieu
2000-12-01 13:14 ` Bogdan Costescu
2000-12-01 16:26 ` Francois Desloges
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=4910.975876066@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=becker@scyld.com \
--cc=jgarzik@mandrakesoft.mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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