Messages in this thread | | | Date | Sun, 25 Apr 2010 09:37:11 -0700 | From | Greg KH <> | Subject | Re: request_firmware API exhaust memory |
| |
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?
thanks,
greg k-h
| |