Messages in this thread | | | Date | Mon, 27 Dec 2004 14:23:50 -0800 | From | "David S. Miller" <> | Subject | Re: PATCH: kmalloc packet slab |
| |
On Mon, 27 Dec 2004 18:17:32 +0100 Patrick McHardy <kaber@trash.net> wrote:
> Alan Cox wrote: > > The networking world runs in 1514 byte packets pretty much all the time. > > This adds a 1620 byte slab for such objects and is one of the internally > > generated Red Hat patches we use on things like Fedora Core 3. Original: > > Arjan van de Ven. > > > > Signed-off-by: Alan Cox <alan@redhat.com> > > Why 1620 bytes ? Most drivers allocate packet_size + 2 bytes. > dev_alloc_skb adds another 16 bytes, finally alloc_skb adds > sizeof(struct skb_shared_info). So we get: > > (32bit): 1514b + 2b + 16b + 160b = 1692b > (64bit): 1514b + 2b + 16b + 312b = 1844b > > On paths using alloc_skb instead of dev_alloc_skb it's 16 bytes > less, but 1620 bytes is still too small for full-sized packets.
Absolutely, there is no way this patch actually helps for full sized frames. Another thing in the above equations is that on output you have to add in MAX_TCP_HEADER which is 128 + MAX_HEADER. MAX_HEADER is variable sized based upon which link layer support is built into the kernel.
Even on input, many ethernet device drivers add in their own amounts to the size for DMA and cache-line alignment.
So this special slab would never be used on output even if it got the base equations correct.
If we are really going to do something like this, it should be calculated properly and be determined per-interface type as netdevs are registered.
Special casing ethernet is just rediculious. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |