From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: bogdan.costescu@iwr.uni-heidelberg.de (Bogdan Costescu)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
mark@somanetworks.com (Mark Frazer),
jgarzik@mandrakesoft.com (Jeff Garzik),
zaitcev@redhat.com (Pete Zaitcev),
linux-kernel@vger.kernel.org (Linux Kernel Mailing List),
netdev@oss.sgi.com
Subject: Re: [PATCH] support for Cobalt Networks (x86 only) systems (for
Date: Sat, 2 Jun 2001 17:15:02 +0100 (BST) [thread overview]
Message-ID: <E156E3K-0001sJ-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.LNX.4.33.0106021007290.22222-100000@kenzo.iwr.uni-heidelberg.de> from "Bogdan Costescu" at Jun 02, 2001 10:20:26 AM
> > keeps beating it. You don't even need maliciousness for this, synchronization
> > effects and locking on the file will ensure it gets you in the end
>
> Sure, but as I already wrote, you can detect that something is wrong. Then
> shoot the person!
How does that solve the problem ?
> > fstat() mtime. That seems easy enough
>
> This only answered the first part of the question: when. How do you pass
> the "how long" info ?
> Does the same applies for the MII ioctl case ?
The mtime tells you exactly that.
> Caching means that the driver (I don't think that it can be done at
> higher levels) has to keep track of accesses to all MII interfaces (yes,
> there can be more than one on a NIC) and all of their registers. One
I disagree. A non priviledged app should not be able to poke around in MII
registers anyway. So you only have to cache the generic state of the link.
> each MII register access. Another solution is to have each register start
> its own cache timer.
You don't need timers.
> OTOH, ioctl rate limiting can be done at higher level and you need only
> one timer per netdevice. So, it's done once and all net drivers benefit
> from it.
You don't need any timers if you are caching. Zilch nada none. You know the
last time a query came in. The mtime lets the app know the last time the value
was modified.
Alan
next prev parent reply other threads:[~2001-06-02 16:17 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.991383180.28261.linux-kernel2news@redhat.com>
2001-06-01 2:47 ` [PATCH] support for Cobalt Networks (x86 only) systems (for real this time) Tim Hockin
2001-06-01 8:10 ` Jeff Garzik
2001-06-01 8:46 ` [PATCH] support for Cobalt Networks (x86 only) systems (for real this Alan Cox
2001-06-01 8:58 ` [PATCH] support for Cobalt Networks (x86 only) systems (for real this time) Pete Zaitcev
2001-06-01 12:03 ` Bogdan Costescu
2001-06-01 12:20 ` [PATCH] support for Cobalt Networks (x86 only) systems (for realthis time) Jeff Garzik
2001-06-01 12:51 ` [PATCH] support for Cobalt Networks (x86 only) systems (for realthis Alan Cox
2001-06-01 12:56 ` Jeff Garzik
2001-06-01 12:58 ` Alan Cox
2001-06-01 13:06 ` Bogdan Costescu
2001-06-01 13:15 ` [PATCH] support for Cobalt Networks (x86 only) systems (forrealthis Jeff Garzik
2001-06-01 13:39 ` Bogdan Costescu
2001-06-01 14:14 ` jamal
2001-06-01 14:30 ` Bogdan Costescu
2001-06-02 14:49 ` jamal
2001-06-03 12:09 ` Bogdan Costescu
2001-06-04 18:43 ` Jeff Garzik
2001-06-04 19:08 ` jamal
2001-06-01 13:19 ` David S. Miller
2001-06-01 14:02 ` Bogdan Costescu
2001-06-01 14:19 ` [PATCH] support for Cobalt Networks (x86 only) systems (for Alan Cox
2001-06-01 14:37 ` Mark Frazer
2001-06-01 14:37 ` Alan Cox
2001-06-01 14:45 ` Mark Frazer
2001-06-01 14:46 ` Bogdan Costescu
2001-06-01 17:37 ` Alan Cox
2001-06-02 8:20 ` Bogdan Costescu
2001-06-02 16:15 ` Alan Cox [this message]
2001-06-02 19:10 ` MII access (was [PATCH] support for Cobalt Networks (x86 only) systems) Bogdan Costescu
2001-06-02 19:25 ` MII access (was [PATCH] support for Cobalt Networks (x86 only) Alan Cox
2001-06-02 21:36 ` Bogdan Costescu
2001-06-02 21:37 ` Alan Cox
2001-06-03 11:59 ` Bogdan Costescu
2001-06-03 12:11 ` Jeff Garzik
2001-06-05 9:07 ` Bogdan Costescu
2001-06-10 2:07 ` eepro100 security fix [was: Re: MII access] Andrey Savochkin
2001-06-01 15:13 ` [PATCH] support for Cobalt Networks (x86 only) systems (for Bogdan Costescu
2001-06-02 22:04 ` [PATCH] support for Cobalt Networks (x86 only) systems (for realthis Jamie Lokier
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=E156E3K-0001sJ-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bogdan.costescu@iwr.uni-heidelberg.de \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@somanetworks.com \
--cc=netdev@oss.sgi.com \
--cc=zaitcev@redhat.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
all inboxes | Powered by JetHome®