Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754345Ab0DSMfc (ORCPT ); Mon, 19 Apr 2010 08:35:32 -0400 Received: from mail-bw0-f225.google.com ([209.85.218.225]:34676 "EHLO mail-bw0-f225.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751440Ab0DSMfb convert rfc822-to-8bit (ORCPT ); Mon, 19 Apr 2010 08:35:31 -0400 MIME-Version: 1.0 In-Reply-To: References: From: Kay Sievers Date: Mon, 19 Apr 2010 14:35:13 +0200 Message-ID: Subject: Re: request_firmware API exhaust memory To: Tomas Winkler Cc: Johannes Berg , Greg KH , David Woodhouse , "Rafael J. Wysocki" , Emmanuel Grumbach , linux-kernel@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1055 Lines: 26 On Mon, Apr 19, 2010 at 14:20, 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. In some stress  testing the usage will exhaust the system > memory. First we suspected there is a memory leak in the > firwmare_class but eventually what is that udevd piles up it takes > time to collect the process. What version of the kernel, and what version of udev? > We loose ~ 500K for each > request/release_firmware iteration. You mean you lose 500k, not taken by any process? > After the stress the process table will will look something like shown below, What are these processes doing (strace)? Do they have child processes? If yes, what are they doing (strace)? Kay -- 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/