Date: Thu, 18 Nov 2004 10:50:11 -0800
From: Greg KH <greg@kroah.com>
To: "Gerold J. Wucherpfennig" <gjwucherpfennig@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel thoughts of a Linux user
Message-ID: <20041118185011.GA24538@kroah.com>
References: <200411181859.27722.gjwucherpfennig@gmx.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200411181859.27722.gjwucherpfennig@gmx.net>
User-Agent: Mutt/1.5.6i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1033
Lines: 26

On Thu, Nov 18, 2004 at 06:59:27PM +0100, Gerold J. Wucherpfennig wrote:
> 
> - Make sysfs optional and enable to publish kernel <-> userspace data
> especially the kernel's KObject data across the kernel's netlink interface as
> it has been summarized on www.kerneltrap.org. This will avoid the
> deadlocks sysfs does introduce when some userspace app holds an open file
> handle of an sysfs object (KObject) which is to be removed. An importrant side 
> effect for embedded systems will be that the RAM overhead introduced by sysfs
> will vaporize.

What RAM overhead?  With 2.6.10-rc2 the memory footprint of sysfs has
been drasticly shrunk.

What deadlocks are you referring to?

And the netlink interface for hotplug events is already present in the
latest kernel.

thanks,

greg k-h
-
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/