All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, acme@conectiva.com.br
Subject: Re: + net-uninline-skb_put.patch added to -mm tree
Date: Mon, 6 Nov 2006 14:57:57 -0800	[thread overview]
Message-ID: <20061106145757.8f59caa8.akpm@osdl.org> (raw)
In-Reply-To: <20061106.144233.23011532.davem@davemloft.net>

On Mon, 06 Nov 2006 14:42:33 -0800 (PST)
David Miller <davem@davemloft.net> wrote:

> From: akpm@osdl.org
> Date: Fri, 03 Nov 2006 14:18:29 -0800
> 
> > Subject: net: uninline skb_put()
> > From: Andrew Morton <akpm@osdl.org>
> > 
> > It has 34 callsites for a total of 2650 bytes.
> > 
> > Cc: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
> > Signed-off-by: Andrew Morton <akpm@osdl.org>
> 
> A more accurate figure would probably be:
> 
> davem@sunset:~/src/GIT/net-2.6$ git grep skb_put | grep -v __skb_put | wc -l
> 1167
> 
> :-)

True.  I'm not sure what .config Arnaldo was using..

> Half of the cost of this interface are the assertions, which while
> useful are obviously over the top for such an oft-used routine in
> packet processing.
> 
> Without the assertion checks it's merely:
> 
> 	unsigned char *tmp = skb->tail;
> 	skb->tail += len;
> 	skb->len  += len;
> 	return tmp;
> 
> And even with 1167 call sites that is definitely something which
> should be inlined.

Yes.

Tricky.  I guess one suitable approach would be to create a standalone
skb-debugging config option.  There's quite a lot of debug stuff in there
which could be made conditional on that option.

But otoh, skb-debugging finds bugs.

  reply	other threads:[~2006-11-06 22:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200611032218.kA3MITih003548@shell0.pdx.osdl.net>
2006-11-06 22:42 ` + net-uninline-skb_put.patch added to -mm tree David Miller
2006-11-06 22:57   ` Andrew Morton [this message]
2006-11-07  0:45     ` Arnaldo Carvalho de Melo

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=20061106145757.8f59caa8.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=acme@conectiva.com.br \
    --cc=davem@davemloft.net \
    --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 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.