public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Kent Yoder <key@austin.ibm.com>
Cc: linux-kernel@vger.kernel.org, marcelo@conectiva.com.br
Subject: Re: [PATCH] IBM Lanstreamer bugfixes (round 3)
Date: Mon, 04 Mar 2002 12:04:37 -0500	[thread overview]
Message-ID: <3C83A925.F93BF448@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0203041023580.11065-100000@janetreno.austin.ibm.com>

Kent Yoder wrote:
> 
>   Jeff,
> 
>         I have a feeling you're talking about this section:
> 
> >  pci_write_config_byte (pdev, PCI_CACHE_LINE_SIZE, cls);
> >  pci_read_config_word (pdev, PCI_COMMAND, &pcr);
> >
> >  /* Turn off Fast B2B enable */
> >  pcr &= ~PCI_COMMAND_FAST_BACK;
> >  /* Turn on SERR# enable and others */
> >  pcr |= (PCI_COMMAND_SERR | PCI_COMMAND_INVALIDATE | PCI_COMMAND_PARITY |
> >          PCI_COMMAND_IO   | PCI_COMMAND_MEMORY);
> >
> >  pci_write_config_word (pdev, PCI_COMMAND, pcr);
> >  pci_read_config_word (pdev, PCI_COMMAND, &pcr);
> 
>   Basically, this section exists from a time when I had no idea why the
> card was behaving badly, so I was trying everything :-).
> 
>   So, after revisiting them, I see that setting cache line size to 0 and
> then using memory write and invalidate doesn't make any sense.  I'm thinking
> both can just be dropped, since I haven't seen any change in performance on
> the machines I've made netperf runs with (a constant 14.7 Mb/s) after
> changing these.

I agree to the first part :)

Set cache line size just like drivers/net/acenic.c does, and enable
memory-write-invalidate...

	Jeff


-- 
Jeff Garzik      |
Building 1024    |
MandrakeSoft     | Choose life.

  reply	other threads:[~2002-03-04 17:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-15 21:44 [PATCH] IBM Lanstreamer bugfixes (round 3) Kent Yoder
2002-02-16 11:12 ` Jeff Garzik
2002-03-04 16:51   ` Kent Yoder
2002-03-04 17:04     ` Jeff Garzik [this message]
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
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=3C83A925.F93BF448@mandrakesoft.com \
    --to=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