Re: [RFC] firmware load: defer request_firmware during early boot and resume
From: Linus Torvalds
Date: Sun Jul 22 2012 - 15:46:30 EST
On Sun, Jul 22, 2012 at 5:58 AM, Borislav Petkov <bp@xxxxxxxxx> wrote:
> Question: is there any other reason
> [besides maybe embedded people who care about each single Kb of memory
> on the system]
> why we don't make this cache/uncache firmware thing *implicit*? That is,
> load it once at driver open time and keep it in memory during the whole
> driver's lifetime. And this all taken care of by the driver core, btw.
So some firmware is a *lot* more than "a few kB". We're talking
hundreds of kB, sometimes more. And to make matters worse, we keep it
in memory with vmalloc(), which is a limited resource on 32-bit
systems. So it can actually be worse than just the memory use itself.
Also, as you already mentioned, there's the "cache coherency" issue.
There are real advantages to reloading the firmware occasionally,
because it might have changed on disk. So..
I do think we might want to consider it, although I do suspect that we
do want to throw it out because of the problems with infinite caches.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/