From: Eric Dumazet <dada1@cosmosbay.com>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH][SOCK]: shrink struct sock
Date: Fri, 04 May 2007 08:10:15 +0200 [thread overview]
Message-ID: <463ACE47.6080807@cosmosbay.com> (raw)
In-Reply-To: <20070504041101.GA27519@ghostprotocols.net>
Arnaldo Carvalho de Melo a écrit :
>
> [acme@mica linux-2.6]$ pahole -C sk_buff_head net/core/sock.o
> struct sk_buff_head {
> struct sk_buff * next; /* 0 8 */
> struct sk_buff * prev; /* 8 8 */
> __u32 qlen; /* 16 4 */
> spinlock_t lock; /* 20 8 */
> }; /* size: 32, cachelines: 1 */
> /* padding: 4 */
> /* last cacheline: 32 bytes */
Hum, maybe not enough tea this morning, but I always thought spinlock_t size
was 4 bytes....
next prev parent reply other threads:[~2007-05-04 6:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 4:11 [PATCH][SOCK]: shrink struct sock Arnaldo Carvalho de Melo
2007-05-04 4:22 ` David Miller
2007-05-04 10:17 ` Ian McDonald
2007-05-04 6:10 ` Eric Dumazet [this message]
2007-05-04 11:24 ` Arnaldo Carvalho de Melo
2007-05-04 12:24 ` Eric Dumazet
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=463ACE47.6080807@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=acme@ghostprotocols.net \
--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 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).