netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Don Fry <pcnet32@verizon.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] pcnet32: only allocate init_block dma consistent
Date: Fri, 09 Mar 2007 12:01:33 -0500	[thread overview]
Message-ID: <45F192ED.6060704@garzik.org> (raw)
In-Reply-To: <20070306184523.GA23268@verizon.net>

Don Fry wrote:
> The patch below moves the init_block out of the private struct and
> only allocates init block with pci_alloc_consistent. 
> 
> This has two effects:
> 
> 1. Performance increase for non cache coherent machines, because the
>    CPU only data in the private struct are now cached
> 
> 2. locks are working now for platforms, which need to have locks
>    in cached memory
> 
> Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> Acked-by: Don Fry <pcnet32@verizon.net>
> ---
>  drivers/net/pcnet32.c |   77 ++++++++++++++++++++++---------------------------
>  1 files changed, 34 insertions(+), 43 deletions(-)

applied 1-2, with included trailing whitespace noise




      parent reply	other threads:[~2007-03-09 17:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-06 18:45 [PATCH 1/2] pcnet32: only allocate init_block dma consistent Don Fry
2007-03-07  3:10 ` Ralf Baechle
2007-03-07  3:39   ` Michael K. Edwards
2007-03-07  4:21     ` Ralf Baechle
2007-03-07 16:35       ` Michael K. Edwards
2007-03-07 19:22         ` Ralf Baechle
2007-03-07 20:15           ` Michael K. Edwards
2007-03-08  1:44             ` Don Fry
2007-03-07 14:50     ` Lennart Sorensen
2007-03-09 17:01 ` 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=45F192ED.6060704@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).