mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: pjd@fred001.dynip.com
To: jgarzik@mandrakesoft.com (Jeff Garzik)
Cc: key@austin.ibm.com (Kent Yoder),
	linux-kernel@vger.kernel.org, marcelo@conectiva.com.br
Subject: Re: [PATCH] IBM Lanstreamer bugfixes (round 3)
Date: Tue, 5 Mar 2002 09:59:05 -0500 (EST)	[thread overview]
Message-ID: <200203051459.g25Ex5x02563@fred.cambridge.ma.us> (raw)
In-Reply-To: <3C83C698.25D28157@mandrakesoft.com> from "Jeff Garzik" at Mar 04, 2002 02:10:16 PM

Jeff Garzik wrote:
> 
> MWI -does- make a difference in performance, though you may need to
> check lanstreamer docs to see if there is a chip-specific MWI bit you
> need to enable, over and above the PCI_COMMAND bit.

My experience - which is 2-3 years old now - is that many BIOSes will
enable MWI for you.  Which makes it very easy to forget to do this,
and then have it discovered by your customers who have machines that
don't set MWI...

............................................................................
 Peter Desnoyers 
 162 Pleasant St.         (617) 661-1979          pjd@fred.cambridge.ma.us
 Cambridge, Mass. 02139


  reply	other threads:[~2002-03-05 15:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-15 21:44 Kent Yoder
2002-02-16 11:12 ` Jeff Garzik
2002-03-04 16:51   ` Kent Yoder
2002-03-04 17:04     ` Jeff Garzik
2002-03-04 17:27       ` David Dillow
2002-03-04 17:46         ` Jeff Garzik
2002-03-04 18:45           ` David Dillow
2002-03-04 18:52             ` Jeff Garzik
2002-03-04 19:02               ` David Dillow
2002-03-04 19:12                 ` Jeff Garzik
2002-03-04 18:58       ` Kent Yoder
2002-03-04 19:10         ` Jeff Garzik
2002-03-05 14:59           ` pjd [this message]
2002-03-05 15:37           ` Kent Yoder
  -- strict thread matches above, loose matches on Subject: below --
2002-02-04 17:16 Kent Yoder

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=200203051459.g25Ex5x02563@fred.cambridge.ma.us \
    --to=pjd@fred001.dynip.com \
    --cc=jgarzik@mandrakesoft.com \
    --cc=key@austin.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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®