From: Jeff Garzik <jeff@garzik.org>
To: Don Fry <pcnet32@verizon.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH ] pcnet32: Fix PCnet32 performance bug on non-coherent architecutres
Date: Tue, 06 Mar 2007 06:15:22 -0500 [thread overview]
Message-ID: <45ED4D4A.3020004@garzik.org> (raw)
In-Reply-To: <20070306021309.GB7139@verizon.net>
Don Fry wrote:
> The PCnet32 driver always passed the the size of the largest possible packet
> to the pci_dma_sync_single_for_cpu and pci_dma_sync_single_for_device.
> This results in a fairly large "colateral damage" in the caches and makes
> the flush operation itself much slower. On a system with a 40MHz CPU this
> patch increases network bandwidth by about 12%.
>
> Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
> Acked-by: Don Fry <pcnet32@verizon.net>
applied
prev parent reply other threads:[~2007-03-06 11:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 2:13 [PATCH ] pcnet32: Fix PCnet32 performance bug on non-coherent architecutres Don Fry
2007-03-06 11:15 ` Jeff Garzik [this message]
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=45ED4D4A.3020004@garzik.org \
--to=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=pcnet32@verizon.net \
/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;
as well as URLs for NNTP newsgroup(s).