public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <andrewm@uow.edu.au>
To: safemode <safemode@voicenet.com>
Cc: William Montgomery <william@opinicus.com>,
	Andrea Arcangeli <andrea@suse.de>,
	linux-kernel@vger.kernel.org
Subject: Re: lowlatency 2.2.19
Date: Tue, 05 Jun 2001 11:20:05 +1000	[thread overview]
Message-ID: <3B1C33C5.AB6C8CD0@uow.edu.au> (raw)
In-Reply-To: <Pine.LNX.3.96.1010604173410.5728A-100000@thing2.opinicus.com>, <Pine.LNX.3.96.1010604173410.5728A-100000@thing2.opinicus.com> <01060420580802.31206@psuedomode>

safemode wrote:
> 
> this is just a general question about low latency patches on 2.2,   I
> remember hearing about low latency patches for 2.4 not playing well with X
> 4.x, is this true for 2.2 low latency patches as well?

Yes, it would be the case.

Some video cards have a PCI cheat-mode in which they keep
the PCI bus busy until they are ready to accept new
commands, rather forcing a retry.  Figures of up to
twenty milliseconds have been mentioned.  Your X server
*may* support the `PCIRetry' config option which will
defeat this.

Info:

http://www.lib.uaa.alaska.edu/linux-kernel/archive/2001-Week-02/1566.html
http://www.zefiro.com/vgakills.txt
http://www.zdnet.com/pcmag/news/trends/t980619a.htm
http://www.research.microsoft.com/~mbj/papers/tr-98-29.html

-

  reply	other threads:[~2001-06-05  1:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-03 14:38 lowlatency 2.2.19 William Montgomery
2001-06-04 12:56 ` Andrea Arcangeli
2001-06-04 21:42   ` William Montgomery
2001-06-05  0:58     ` safemode
2001-06-05  1:20       ` Andrew Morton [this message]
2001-06-07 11:05         ` Pierre Etchemaite
2001-06-05  3:23       ` William Montgomery

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=3B1C33C5.AB6C8CD0@uow.edu.au \
    --to=andrewm@uow.edu.au \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=safemode@voicenet.com \
    --cc=william@opinicus.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