All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre Etchemaite <petchema@concept-micro.com>
To: Andrew Morton <andrewm@uow.edu.au>
Cc: linux-kernel@vger.kernel.org, Andrea Arcangeli <andrea@suse.de>,
	William Montgomery <william@opinicus.com>,
	safemode <safemode@voicenet.com>
Subject: Re: lowlatency 2.2.19
Date: Thu, 07 Jun 2001 13:05:35 +0200 (CEST)	[thread overview]
Message-ID: <XFMail.20010607130535.petchema@concept-micro.com> (raw)
In-Reply-To: <3B1C33C5.AB6C8CD0@uow.edu.au>


Le 05-Jun-2001, Andrew Morton écrivait :
> 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.

Just FYI (I think it's S3 Virge specific, but maybe not), I solved my RX
packets loss on my ADSL interface after I read the message

        http://www.xfree86.org/pipermail/xpert/2000-November/003402.html

and used

Section "Device"
        Identifier      "Generic Video Card"
        Driver          "s3virge"
        Option "fpm_vram"
        Option "fifo_aggressive"
        Option "pci_burst" "on"
        Option "pci_retry" "on"
        Option "XaaNoCPUToScreenColorExpandFill"
EndSection

in my XFConfig-4.

(The whole thread seems to be worth a read.)

Best regards,
Pierre.


-- 
We are the dot in 0.2 Kb/s

  reply	other threads:[~2001-06-07 11:06 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
2001-06-07 11:05         ` Pierre Etchemaite [this message]
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=XFMail.20010607130535.petchema@concept-micro.com \
    --to=petchema@concept-micro.com \
    --cc=andrea@suse.de \
    --cc=andrewm@uow.edu.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.