[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1365516022.3887.131.camel@edumazet-glaptop>
Date: Tue, 09 Apr 2013 07:00:22 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: Paul Moore <pmoore@...hat.com>
Cc: Casey Schaufler <casey@...aufler-ca.com>,
David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
mvadkert@...hat.com, selinux@...ho.nsa.gov,
linux-security-module@...r.kernel.org
Subject: Re: [PATCH] tcp: assign the sock correctly to an outgoing SYNACK
packet
On Tue, 2013-04-09 at 09:19 -0400, Paul Moore wrote:
> As Casey already mentioned, if this isn't acceptable please help me understand
> why.
>
You see something which is not the reality. If you do such analysis,
better do it properly, because any change you are going to submit will
be doubly checked by people who really care.
sizeof(sk_buff) is not 280. (aligned to 320 because of cache line being
64)
Tell me what you have when doing :
ls -l /sys/kernel/slab/skbuff_head_cache
Do you really see
$ ls -l /sys/kernel/slab/skbuff_head_cache
lrwxrwxrwx 1 root root 0 Apr 9 06:54 /sys/kernel/slab/skbuff_head_cache -> :t-0000320
Here I get :
$ ls -l /sys/kernel/slab/skbuff_head_cache
lrwxrwxrwx 1 root root 0 Apr 9 06:54 /sys/kernel/slab/skbuff_head_cache -> :t-0000256
because sizeof(sk_buff) <= 256
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists