From: "David S. Miller" <davem@redhat.com>
To: Mitchell Blank Jr <mitch@sfgoth.com>
Cc: shemminger@osdl.org, netdev@oss.sgi.com
Subject: Re: [PATCH] skbuff more likely/unlikely
Date: Fri, 3 Oct 2003 00:19:16 -0700 [thread overview]
Message-ID: <20031003001916.570546c4.davem@redhat.com> (raw)
In-Reply-To: <20031003023431.GC42593@gaz.sfgoth.com>
On Thu, 2 Oct 2003 19:34:31 -0700
Mitchell Blank Jr <mitch@sfgoth.com> wrote:
> Stephen Hemminger wrote:
> > A couple more places where we can help by hinting the compiler
> > for 2.6.0-test6. If we are pulling off header, is is likely there;
> > and skb alloc's succeed in the normal case.
> >
> > Thought I saw an earlier similar patch, but here is my take on it.
>
> Yes, my patch from a couple weeks ago does the same thing (but also
> did a lot in skbuff.c) I haven't had a chance to rediff and test
> after the const parts went in. Do you want to adopt the rest of the
> changes?
I applied Stephen's patch here, you can post something relative
to that if you like.
prev parent reply other threads:[~2003-10-03 7:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-02 17:24 [PATCH] skbuff more likely/unlikely Stephen Hemminger
2003-10-03 2:34 ` Mitchell Blank Jr
2003-10-03 7:19 ` David S. Miller [this message]
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=20031003001916.570546c4.davem@redhat.com \
--to=davem@redhat.com \
--cc=mitch@sfgoth.com \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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).