From: "Jeffrey V. Merkey" <jmerkey@soleranetworks.com>
To: Jesse Brandeburg <jesse.brandeburg@gmail.com>
Cc: "Jeff V. Merkey" <jmerkey@soleranetworks.com>,
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: Thu, 09 Nov 2006 01:46:52 -0700 [thread overview]
Message-ID: <4552EAFC.5060400@soleranetworks.com> (raw)
In-Reply-To: <4807377b0611081701i26ee7ce0k1f822dbbe52c2c8@mail.gmail.com>
Jesse Brandeburg wrote:
> 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.
In the case I am referring to, the memory is already mapped with a
previous call, which means it may be getting
mapped twice.
Jeff
>
> 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
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2006-11-09 7:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 21:38 e1000 driver 2.6.18 - how to waste processor cycles Jeff V. Merkey
2006-11-09 1:01 ` Jesse Brandeburg
2006-11-09 2:43 ` David Miller
2006-11-09 8:46 ` Jeffrey V. Merkey [this message]
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=4552EAFC.5060400@soleranetworks.com \
--to=jmerkey@soleranetworks.com \
--cc=jesse.brandeburg@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.