From: David Miller <davem@davemloft.net>
To: jesse.brandeburg@gmail.com
Cc: jmerkey@soleranetworks.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: e1000 driver 2.6.18 - how to waste processor cycles
Date: Wed, 08 Nov 2006 18:43:53 -0800 (PST) [thread overview]
Message-ID: <20061108.184353.106435332.davem@davemloft.net> (raw)
In-Reply-To: <4807377b0611081701i26ee7ce0k1f822dbbe52c2c8@mail.gmail.com>
From: "Jesse Brandeburg" <jesse.brandeburg@gmail.com>
Date: Wed, 8 Nov 2006 17:01:44 -0800
> If you can show that it is faster to use pci_dma_sync_single_for_cpu
> and friends I'd be glad to take a patch.
The problem is if you don't recycle the buffer and really unmap,
you'll flush twice. That can potentially be expensive.
next prev parent reply other threads:[~2006-11-09 2:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45524E3A.7080301@soleranetworks.com>
2006-11-09 1:01 ` e1000 driver 2.6.18 - how to waste processor cycles Jesse Brandeburg
2006-11-09 2:43 ` David Miller [this message]
2006-11-09 8:46 ` Jeffrey V. Merkey
2006-11-09 22:45 ` Jesse Brandeburg
2006-11-09 22:49 ` Jeff V. Merkey
2006-11-09 22:54 ` Jeff V. Merkey
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=20061108.184353.106435332.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jesse.brandeburg@gmail.com \
--cc=jmerkey@soleranetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).