From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: sgruszka@redhat.com, romieu@fr.zoreil.com, netdev@vger.kernel.org
Subject: Re: [PATCH] net: introduce alloc_skb_order0
Date: Sat, 16 Oct 2010 11:53:42 -0700 (PDT) [thread overview]
Message-ID: <20101016.115342.71098036.davem@davemloft.net> (raw)
In-Reply-To: <1286831867.30423.80.camel@edumazet-laptop>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Mon, 11 Oct 2010 23:17:47 +0200
> [PATCH net-next] r8169: use 50% less ram for RX ring
>
> Using standard skb allocations in r8169 leads to order-3 allocations (if
> PAGE_SIZE=4096), because NIC needs 16383 bytes, and skb overhead makes
> this bigger than 16384 -> 32768 bytes per "skb"
>
> Using kmalloc() permits to reduce memory requirements of one r8169 nic
> by 4Mbytes. (256 frames * 16Kbytes). This is fine since a hardware bug
> requires us to copy incoming frames, so we build real skb when doing
> this copy.
>
> Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
Applied.
next prev parent reply other threads:[~2010-10-16 18:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 14:25 [PATCH 1/2] r8169: allocate with GFP_KERNEL flag when able to sleep Stanislaw Gruszka
2010-10-08 14:25 ` [PATCH 2/2] r8169: use device model DMA API Stanislaw Gruszka
2010-10-09 7:57 ` Eric Dumazet
2010-10-09 16:17 ` David Miller
2010-10-08 14:52 ` [PATCH 1/2] r8169: allocate with GFP_KERNEL flag when able to sleep Stanislaw Gruszka
2010-10-08 15:04 ` Eric Dumazet
2010-10-08 16:03 ` Stanislaw Gruszka
2010-10-08 16:27 ` Eric Dumazet
2010-10-09 15:59 ` [PATCH] net: introduce alloc_skb_order0 Eric Dumazet
2010-10-11 15:55 ` Stanislaw Gruszka
2010-10-11 16:05 ` Eric Dumazet
2010-10-11 21:17 ` Eric Dumazet
2010-10-16 18:53 ` David Miller [this message]
2010-10-11 16:03 ` [PATCH 1/2] r8169: allocate with GFP_KERNEL flag when able to sleep Christoph Lameter
2010-10-11 16:07 ` Eric Dumazet
2010-10-11 16:14 ` Christoph Lameter
2010-10-09 7:54 ` Eric Dumazet
2010-10-09 16:17 ` 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=20101016.115342.71098036.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
--cc=sgruszka@redhat.com \
/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).