Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752944AbaJBV1U (ORCPT ); Thu, 2 Oct 2014 17:27:20 -0400 Received: from mail-pa0-f44.google.com ([209.85.220.44]:63944 "EHLO mail-pa0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751965AbaJBV1T (ORCPT ); Thu, 2 Oct 2014 17:27:19 -0400 Date: Thu, 2 Oct 2014 14:27:03 -0700 From: Stephen Hemminger To: ebiederm@xmission.com (Eric W. Biederman) Cc: Alexey Dobriyan , Nicolas Dichtel , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, davem@davemloft.net, akpm@linux-foundation.org, rui.xiang@huawei.com, viro@zeniv.linux.org.uk, oleg@redhat.com, gorcunov@openvz.org, kirill.shutemov@linux.intel.com, grant.likely@secretlab.ca, tytso@mit.edu, Thierry Herbelot Subject: Re: [RFC PATCH linux 2/2] fs/proc: use a hash table for the directory entries Message-ID: <20141002142703.10325f4f@urahara> In-Reply-To: <87h9zmji3q.fsf@x220.int.ebiederm.org> References: <20131003.150947.2179820478039260398.davem@davemloft.net> <1412263501-6572-1-git-send-email-nicolas.dichtel@6wind.com> <1412263501-6572-3-git-send-email-nicolas.dichtel@6wind.com> <87h9zmpcz5.fsf@x220.int.ebiederm.org> <20141002200639.GA3497@p183.telecom.by> <87h9zmji3q.fsf@x220.int.ebiederm.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 02 Oct 2014 14:07:37 -0700 ebiederm@xmission.com (Eric W. Biederman) wrote: > Alexey Dobriyan writes: > > > On Thu, Oct 02, 2014 at 11:01:50AM -0700, Eric W. Biederman wrote: > >> Nicolas Dichtel writes: > >> > >> > From: Thierry Herbelot > >> > > >> > The current implementation for the directories in /proc is using a single > >> > linked list. This is slow when handling directories with large numbers of > >> > entries (eg netdevice-related entries when lots of tunnels are opened). > >> > > >> > This patch enables multiple linked lists. A hash based on the entry name is > >> > used to select the linked list for one given entry. > >> > > >> > The speed creation of netdevices is faster as shorter linked lists must be > >> > scanned when adding a new netdevice. > >> > >> Is the directory of primary concern /proc/net/dev/snmp6 ? > >> > >> Unless I have configured my networking stack weird by mistake that > >> is the only directory under /proc/net that grows when we add an > >> interface. > >> > >> I just want to make certain I am seeing the same things that you are > >> seeing. > >> > >> I feel silly for overlooking this directory when the rest of the > >> scalability work was done. > > > > Slowdown comes from "duplicate name" check: > > > > for (tmp = dir->subdir; tmp; tmp = tmp->next) > > if (strcmp(tmp->name, dp->name) == 0) { > > WARN(1, "proc_dir_entry '%s/%s' already registered\n", > > dir->name, dp->name); > > break; > > } > > > > Removal can be made O(1) after switching to doubly-linked list. > > Yes. There is the however unfortunate fact that proc directories exist > to be used. If we don't switch to a better data structure than a linked > list the actual use will then opening of the files under > /proc/net/dev/snmp6/ will become O(N^2). Which doesn't help much > (assuming those files are good for something). > > If those files aren't actually useful we should just make registering > them a config option. Deprecate them strongly and let only people who > need extreme backwards compatibility enable them. Net-snmp uses them (agent/mibgroup/mibII/kernel_linux.c) -- 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/