Messages in this thread | | | Date | Sun, 25 Apr 2010 22:22:54 +0300 | Subject | Re: request_firmware API exhaust memory | From | Tomas Winkler <> |
| |
On Sun, Apr 25, 2010 at 7:37 PM, Greg KH <greg@kroah.com> wrote: > On Thu, Apr 22, 2010 at 01:22:51AM +0300, Tomas Winkler wrote: >> On Mon, Apr 19, 2010 at 5:59 PM, Greg KH <greg@kroah.com> wrote: >> > On Mon, Apr 19, 2010 at 03:20:34PM +0300, Tomas Winkler wrote: >> >> Lately we've been developing a device that rather more extensively >> >> used request_firmware API in load and also using pm_notifiers to load >> >> firmware. >> > >> > Do you have a pointer to your driver source anywhere that shows how you >> > are trying to use the firmware api in this manner? >> >> I've attached a very simple test driver I'm using. Just wanted to >> eliminate anything else. >> Bellow is a little script that loads and releases the firmware. My >> previous observation was wrong. >> The free memory gradually decreases regardless of number or dangling >> udevd forks, which are eventually collected if the sleep period is >> long enough ~10s. > > That sounds normal for the free memory. Kay, that's also to be expected > for the udevd forks as well, right?
Sorry maybe I was not clear what I mean that the memory will be eventually exhausted and system will crash Is this normal? Actually I less suspect now udevd as the same happens on android platform where there is no udev
Tomas -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |