public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@soleranetworks.com>
To: Linux kernel <linux-kernel@vger.kernel.org>
Subject: e1000 driver 2.6.18 - how to waste processor cycles
Date: Wed, 08 Nov 2006 14:38:02 -0700	[thread overview]
Message-ID: <45524E3A.7080301@soleranetworks.com> (raw)


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.

Jeff

             reply	other threads:[~2006-11-08 21:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-08 21:38 Jeff V. Merkey [this message]
2006-11-09  1:01 ` e1000 driver 2.6.18 - how to waste processor cycles Jesse Brandeburg
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=45524E3A.7080301@soleranetworks.com \
    --to=jmerkey@soleranetworks.com \
    --cc=linux-kernel@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