From mboxrd@z Thu Jan  1 00:00:00 1970
From: Al Viro <viro@ZenIV.linux.org.uk>
Subject: Re: [RFC][PATCHv3] List per-process file descriptor consumption when
 hitting file-max
Date: Wed, 13 Jan 2010 22:44:59 +0000
Message-ID: <20100113224459.GA21934@ZenIV.linux.org.uk>
References: <28675.1248957636@turing-police.cc.vt.edu>
 <1263202687-18529-1-git-send-email-virtuoso@slind.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Valdis.Kletnieks@vt.edu, linux-fsdevel@vger.kernel.org,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org
To: Alexander Shishkin <virtuoso@slind.org>
Return-path: <linux-kernel-owner+glk-linux-kernel-3=40m.gmane.org-S932210Ab0AMWpF@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <1263202687-18529-1-git-send-email-virtuoso@slind.org>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

On Mon, Jan 11, 2010 at 11:38:07AM +0200, Alexander Shishkin wrote:
> When a file descriptor limit is hit, display the top consumers of
> descriptors so that it is possible to identify and fix those which
> leak them.
> 
> Two new sysctl tunables are introduced:
>   * file-max-consumers -- number of processes to display (defaults
>     to 10);
>   * file-max-rate-limit -- time interval between subsequent dumps
>     (defaults to 10 seconds).

That *still* doesn't answer the most important question: what for?