public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Stephen Hemminger <shemminger@linux-foundation.org>,
	Jeff Garzik <jeff@garzik.org>, Mike Houston <mikeserv@bmts.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.22-rc2
Date: Tue, 22 May 2007 10:54:12 -0700	[thread overview]
Message-ID: <46532E44.4000701@zytor.com> (raw)
In-Reply-To: <alpine.LFD.0.98.0705212153220.3890@woody.linux-foundation.org>

Linus Torvalds wrote:
> 
> I can't really see that being a real problem in this day and age of PCI-X 
> etc, but it _used_ to be a possible issue a decade ago. Maybe you've found 
> a case where it matters even on modern hardware? We occasionally used to 
> set the PCI latency timer to make people happy.
> 
> (Not that I'm convinced it even has any semantic meaning on a modern PCI 
> system..)
> 

The PCI latency counters matter as long as you're talking a PCI or PCI-X
bus.  It matters not one iota on anything that pretends to be a PCI bus
but isn't, i.e. PCI Express, HyperTransport, etc.

	-hpa

  parent reply	other threads:[~2007-05-22 17:55 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-19  5:17 Linux 2.6.22-rc2 Linus Torvalds
2007-05-19  6:54 ` Andrey Borzenkov
2007-05-19 14:28 ` [BUG: 2.6.22-rc2] SLAB doesn't like usb_get_configuration() Indan Zupancic
     [not found]   ` <6101e8c40705190950jb093d65l611995895a182ec0@mail.gmail.com>
2007-05-19 16:51     ` Fwd: " oliver pinter
2007-05-19 18:20   ` Christoph Lameter
2007-05-19 19:33     ` Greg KH
2007-05-19 22:10       ` Indan Zupancic
2007-05-20 12:57 ` Linux 2.6.22-rc2: make -j makes it unresponsive Rafael J. Wysocki
2007-05-20 13:01   ` Krzysztof Halasa
2007-05-20 13:23     ` Rafael J. Wysocki
2007-05-20 21:05 ` Linux 2.6.22-rc2 Mike Houston
2007-05-21 15:45   ` Stephen Hemminger
2007-05-21 17:10     ` Mike Houston
2007-05-21 17:37       ` Stephen Hemminger
2007-05-22  2:58         ` Mike Houston
2007-05-22  4:31           ` Stephen Hemminger
2007-05-22  4:36             ` Jeff Garzik
2007-05-22  4:42               ` Stephen Hemminger
2007-05-22  5:04                 ` Linus Torvalds
2007-05-22 17:19                   ` Stephen Hemminger
2007-05-22 17:54                   ` H. Peter Anvin [this message]
2007-05-22 22:14             ` Mike Houston
2007-05-23  0:00               ` Linus Torvalds
2007-05-23  0:29                 ` Stephen Hemminger
2007-05-23  1:53                   ` Linus Torvalds
2007-05-23 14:58                     ` Stephen Hemminger
2007-05-23 17:39                 ` Mike Houston
2007-05-23 17:46                   ` Linus Torvalds
2007-05-23 18:04                     ` Stephen Hemminger
2007-05-24 18:26                     ` Mike Houston
2007-05-24 22:08                       ` sky2/pci issues on Gigabyte Stephen Hemminger
2007-05-24 22:48                         ` Linus Torvalds
2007-05-24 23:04                           ` Stephen Hemminger
2007-05-25  0:01                             ` Mike Houston

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=46532E44.4000701@zytor.com \
    --to=hpa@zytor.com \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikeserv@bmts.com \
    --cc=shemminger@linux-foundation.org \
    --cc=torvalds@linux-foundation.org \
    /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