From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Stephen Boyd <stephen.boyd@linaro.org>
Cc: linux-kernel@vger.kernel.org, Ming Lei <ming.lei@canonical.com>,
Vikram Mulukutla <markivx@codeaurora.org>,
Mark Brown <broonie@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
linux-arm@lists.infradead.org
Subject: Re: [PATCH v4 0/3] request_firmware() into pre-allocated buffers
Date: Tue, 7 Jun 2016 09:45:14 +0100 [thread overview]
Message-ID: <20160607084514.GN1041@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20160607083537.28484-1-stephen.boyd@linaro.org>
And you're still doing it, after I've already pointed out that you
posted these to linux-arm and not linux-arm-kernel. By posting them
to the wrong list, you are preventing proper review of these patches,
so really these should not be merged until you've corrected that.
On Tue, Jun 07, 2016 at 01:35:34AM -0700, Stephen Boyd wrote:
> Some systems are memory constrained but they need to load very
> large firmwares. The firmware subsystem allows drivers to request
> this firmware be loaded from the filesystem, but this requires
> that the entire firmware be loaded into kernel memory first
> before it's provided to the driver. This can lead to a situation
> where we map the firmware twice, once to load the firmware into
> kernel memory and once to copy the firmware into the final
> resting place.
>
> This design creates needless memory pressure and delays loading
> because we have to copy from kernel memory to somewhere else.
> This patch sets adds support to the request firmware API to load the
> firmware directly into a pre-allocated buffer, skipping the intermediate
> copying step and alleviating memory pressure during firmware loading.
> The drawback is that we can't use the firmware caching feature because
> the memory for the firmware cache is not managed by the firmware
> layer.
>
> Patches based on v4.7-rc1.
>
> Changes since v3:
> * Rebased onto v4.7-rc1
> * Renamed enum per Mimi's comment
>
> Changes since v2:
> * Dropped DMA API changes and moved to dma coherent APIs per Catalin's
> suggestions
> * Reworked to request firmware directly into any pre-allocated buffer
> * Split off cleanup patch into patch #1 to ease review
> * Added file reading enum for reading firmware directly into buffer
>
> Changes since v1:
> * Rebased onto v4.6-rc1 (large conflicts due to movement of code from Mimi)
> * Added some CONFIG_HAS_DMA ifdefs around code that's using DMA ops
>
>
> Stephen Boyd (2):
> firmware: Consolidate kmap/read/write logic
> firmware: Support loading into a pre-allocated buffer
>
> Vikram Mulukutla (1):
> firmware: Provide infrastructure to make fw caching optional
>
> drivers/base/firmware_class.c | 183 +++++++++++++++++++++++++++++-------------
> fs/exec.c | 9 ++-
> include/linux/firmware.h | 8 ++
> include/linux/fs.h | 1 +
> 4 files changed, 142 insertions(+), 59 deletions(-)
>
> --
> 2.9.0-rc1
>
>
> _______________________________________________
> linux-arm mailing list
> linux-arm@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2016-06-07 8:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 8:35 Stephen Boyd
2016-06-07 8:35 ` [PATCH v4 1/3] firmware: Consolidate kmap/read/write logic Stephen Boyd
2016-06-07 8:35 ` [PATCH v4 2/3] firmware: Provide infrastructure to make fw caching optional Stephen Boyd
2016-06-07 8:35 ` [PATCH v4 3/3] firmware: Support loading into a pre-allocated buffer Stephen Boyd
2016-06-07 8:45 ` Russell King - ARM Linux [this message]
2016-06-07 16:47 ` [PATCH v4 0/3] request_firmware() into pre-allocated buffers Stephen Boyd
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=20160607084514.GN1041@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=linux-arm@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markivx@codeaurora.org \
--cc=ming.lei@canonical.com \
--cc=stephen.boyd@linaro.org \
--cc=zohar@linux.vnet.ibm.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
all inboxes | Powered by JetHome®