From: David Miller <davem@davemloft.net>
To: akinobu.mita@gmail.com
Cc: netdev@vger.kernel.org, mporter@kernel.crashing.org,
alexandre.bounine@idt.com
Subject: Re: [PATCH] rionet: fix page allocation order of rionet_active
Date: Sun, 01 Apr 2012 23:17:58 -0400 (EDT) [thread overview]
Message-ID: <20120401.231758.636936187534240046.davem@davemloft.net> (raw)
In-Reply-To: <1333105306-2601-1-git-send-email-akinobu.mita@gmail.com>
From: Akinobu Mita <akinobu.mita@gmail.com>
Date: Fri, 30 Mar 2012 20:01:46 +0900
> rionet_active is allocated from the page allocator and the allocation
> order is calculated on the assumption that the page size is 4KB, so it
> wastes memory on more than 4K page systems.
>
> Signed-off-by: Akinobu Mita <akinobu.mita@gmail.com>
Applied, thanks.
prev parent reply other threads:[~2012-04-02 3:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 11:01 [PATCH] rionet: fix page allocation order of rionet_active Akinobu Mita
2012-04-02 3:17 ` David Miller [this message]
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=20120401.231758.636936187534240046.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akinobu.mita@gmail.com \
--cc=alexandre.bounine@idt.com \
--cc=mporter@kernel.crashing.org \
--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).