[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <201101142244.21117.rjw@sisk.pl>
Date: Fri, 14 Jan 2011 22:44:20 +0100
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Ben Hutchings <benh@...ian.org>, Michael Tokarev <mjt@....msk.ru>,
David Woodhouse <dwmw2@...radead.org>,
Johannes Berg <johannes.berg@...el.com>,
"Greg Kroah-Hartman" <gregkh@...e.de>,
Francois Romieu <romieu@...zoreil.com>,
David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
Jarek KamiĆski <jarek@...o.eu.org>,
Hayes <hayeswang@...ltek.com>
Subject: Re: [PATCH] r8169: keep firmware in memory.
On Friday, January 14, 2011, Linus Torvalds wrote:
> On Fri, Jan 14, 2011 at 8:30 AM, Ben Hutchings <benh@...ian.org> wrote:
> >
> > This is something I started to implement, but never got finished. I
> > don't think it can be done without an API change, though, as we need
> > to know when to drop firmware from the cache. But perhaps this could
> > be done with a hook in the device-driver binding code.
>
> Or just associate the firmware with a module?
>
> So if the firmware gets loaded, it stays in memory until the module is unloaded?
>
> And this all would only be the case if CONFIG_PM is set, so you'd not
> waste memory unnecessarily.
Alternatively, a suspend/hibernate notifier can be used for that I think.
They are called before the freezing and after the thawing of user space, so the
the PM_POST_SUSPEND or PM_POST_RESTORE notification can easily cause the
firmare(s) to be dropped from memory.
Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists