From: matt@codeblueprint.co.uk (Matt Fleming)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] efi: stub: use a pool allocation for the cmdline
Date: Wed, 15 Apr 2015 10:55:06 +0100 [thread overview]
Message-ID: <20150415095506.GA4804@codeblueprint.co.uk> (raw)
In-Reply-To: <CAKv+Gu-KHpSWLKOgA7UW8C6L1-K3dOieNmF2=qq_t5N73u3Spg@mail.gmail.com>
On Fri, 10 Apr, at 07:14:34PM, Ard Biesheuvel wrote:
>
> It is not such a big deal: the memory is reclaimed anyway, I was just
> trying to reduce the fragmentation a bit, and trying to avoid
> efi_xxx_alloc() which are substantially heavier than calling
> allocate_pool() or allocate_pages() directly.
Out of curiosity, do you have any runtime numbers to backup the claim
that allocate_*() is substantially more lightweight?
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2015-04-15 9:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 12:56 [PATCH] efi: stub: use a pool allocation for the cmdline Ard Biesheuvel
2015-04-10 16:43 ` Roy Franz
2015-04-10 17:14 ` Ard Biesheuvel
2015-04-11 0:44 ` Roy Franz
2015-04-15 9:55 ` Matt Fleming [this message]
2015-04-15 10:01 ` Ard Biesheuvel
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=20150415095506.GA4804@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=linux-arm-kernel@lists.infradead.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).