From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin LaHaise Subject: Re: [PATCH 3/7] sysfs: Keep an nlink count on sysfs directories. Date: Mon, 11 Jan 2010 20:12:45 -0500 Message-ID: <20100112011245.GM5524@kvack.org> References: <1263241315-19499-3-git-send-email-ebiederm@xmission.com> <4B4BC683.7060508@kernel.org> <20100112005308.GL5524@kvack.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Tejun Heo , Greg Kroah-Hartman , Kay Sievers , linux-kernel@vger.kernel.org, Cornelia Huck , linux-fsdevel@vger.kernel.org, Eric Dumazet , Serge Hallyn , "Eric W. Biederman" To: "Eric W. Biederman" Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Mon, Jan 11, 2010 at 05:06:53PM -0800, Eric W. Biederman wrote: > I don't see the link count as interesting enough to store more than > 16bits for it. Even with 32bits of storage for nlink sysfs would have > to have to handle the rollover case as I am doing now. So I don't > see any advantage to storing more bits. I'm not terribly concerned with what value gets returned, but rather about how long is spent calculating it. Ideally, new sysfs directory entries can be inserted in an O(1) or other reasonable order operation. I'll try to find some time to re-run my interface scaling tests with your latest changes. =ben