From: Eric Dumazet <dada1@cosmosbay.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 2/4]: Store retransmit queue packets in RB tree.
Date: Wed, 28 Feb 2007 21:33:50 +0100 [thread overview]
Message-ID: <45E5E72E.6070109@cosmosbay.com> (raw)
In-Reply-To: <20070228.114912.89063615.davem@davemloft.net>
David Miller a écrit :
> commit c387760826bd71103220e06ca7b0bf90a785567e
> Author: David S. Miller <davem@sunset.davemloft.net>
> Date: Tue Feb 27 16:44:42 2007 -0800
>
> [TCP]: Store retransmit queue packets in RB tree.
>
> Signed-off-by: David S. Miller <davem@davemloft.net>
>
> diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h
> index 4ff3940..b70fd21 100644
> --- a/include/linux/skbuff.h
> +++ b/include/linux/skbuff.h
> @@ -18,6 +18,7 @@
> #include <linux/compiler.h>
> #include <linux/time.h>
> #include <linux/cache.h>
> +#include <linux/rbtree.h>
>
> #include <asm/atomic.h>
> #include <asm/types.h>
> @@ -232,6 +233,8 @@ struct sk_buff {
> struct sk_buff *next;
> struct sk_buff *prev;
>
> + struct rb_node rb;
> +
> struct sock *sk;
> struct skb_timeval tstamp;
> struct net_device *dev;
I am not sure this rb_node placement is optimal. rb lookups want to access
rb_node and end_seq. They should be placed in the same cache line :)
next/prev were at the begining of sk_buff, there is no such constraint for rb
next prev parent reply other threads:[~2007-02-28 20:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 19:49 [PATCH 2/4]: Store retransmit queue packets in RB tree David Miller
2007-02-28 20:33 ` Eric Dumazet [this message]
2007-02-28 20:56 ` David Miller
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=45E5E72E.6070109@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=davem@davemloft.net \
--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.