From: "Jesse Brandeburg" <jesse.brandeburg@gmail.com>
To: "Jeff V. Merkey" <jmerkey@soleranetworks.com>
Cc: "Linux kernel" <linux-kernel@vger.kernel.org>,
"NetDEV list" <netdev@vger.kernel.org>
Subject: Re: e1000 driver 2.6.18 - how to waste processor cycles
Date: Wed, 8 Nov 2006 17:01:44 -0800 [thread overview]
Message-ID: <4807377b0611081701i26ee7ce0k1f822dbbe52c2c8@mail.gmail.com> (raw)
In-Reply-To: <45524E3A.7080301@soleranetworks.com>
included netdev...
On 11/8/06, Jeff V. Merkey <jmerkey@soleranetworks.com> wrote:
>
> Is there a good reason the skb refill routine in e1000_alloc_rx_buffers
> needs to go and touch and remap skb memory
> on already loaded descriptors/ This seems extremely wasteful of
> processor cycles when refilling the ring buffer.
>
> I note that the archtiecture has changed and is recycling buffers from
> the rx_irq routine and when the routine is called
> to refill the ring buffers, a lot of wasteful and needless calls for
> map_skb is occurring.
we have to unmap the descriptor (or at least do
pci_dma_sync_single_for_cpu / pci_dma_sync_single_for_device) because
the dma API says we can't be guaranteed the cacheable memory is
consistent until we do one of the afore mentioned pci dma ops.
we have to do *something* before we access it. Simplest path is to
unmap it and then recycle/map it.
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.
Hope this helps,
Jesse
next prev parent reply other threads:[~2006-11-09 1:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 21:38 Jeff V. Merkey
2006-11-09 1:01 ` Jesse Brandeburg [this message]
2006-11-09 2:43 ` David Miller
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=4807377b0611081701i26ee7ce0k1f822dbbe52c2c8@mail.gmail.com \
--to=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
all inboxes | Powered by JetHome®