Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964984AbWEBVd4 (ORCPT ); Tue, 2 May 2006 17:33:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964985AbWEBVdz (ORCPT ); Tue, 2 May 2006 17:33:55 -0400 Received: from soundwarez.org ([217.160.171.123]:28876 "EHLO soundwarez.org") by vger.kernel.org with ESMTP id S964984AbWEBVdz (ORCPT ); Tue, 2 May 2006 17:33:55 -0400 Date: Tue, 2 May 2006 23:33:52 +0200 From: Kay Sievers To: Greg KH Cc: Kyle Moffett , Michael Holzheu , akpm@osdl.org, schwidefsky@de.ibm.com, penberg@cs.helsinki.fi, ioe-lkml@rameria.de, joern@wohnheim.fh-wedel.de, linux-kernel@vger.kernel.org Subject: Re: [PATCH] s390: Hypervisor File System Message-ID: <20060502213352.GA18192@vrfy.org> References: <8A7D2F4D-5A05-4C93-B514-03268CAA9201@mac.com> <20060429215501.GA9870@kroah.com> <4237705F-E1B2-46CF-BE66-EFB77F68EC42@mac.com> <20060501203815.GE19423@kroah.com> <2DBA690E-B11A-478E-B2E0-0529F4CE45A9@mac.com> <20060502040053.GA14413@kroah.com> <20060502052341.GD11150@vrfy.org> <20060502053703.GA12992@kroah.com> <20060502114603.GA14568@vrfy.org> <20060502212845.GA30957@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060502212845.GA30957@kroah.com> User-Agent: Mutt/1.5.11+cvs20060126 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1495 Lines: 30 On Tue, May 02, 2006 at 02:28:45PM -0700, Greg KH wrote: > On Tue, May 02, 2006 at 01:46:03PM +0200, Kay Sievers wrote: > > On Mon, May 01, 2006 at 10:37:03PM -0700, Greg KH wrote: > > > On Tue, May 02, 2006 at 07:23:41AM +0200, Kay Sievers wrote: > > > > If the count of values handled in a transaction is not to high and it > > > > makes sense to group these values logically, why not just create an > > > > attribute group for every transaction, which creates dummy attributes > > > > to fill the values in, and use an "action" file in that group, that > > > > commits all the values at once to whatever target? That should fit into > > > > the ioctl use pattern, right? > > > > > > That's what configfs can handle easier. I think the issue is getting > > > stuff from the kernel in one atomic snapshot (all the different file > > > values from the same point in time.) > > > > Sure, but just like an ioctl, the kernel could return the values after > > writing to the "action" file in the dummy attributes. That would be > > something like a snapshot, right? > > Yes, but where would the buffer be to return the data to on a write? In > the data that the user passed to write? In the "dummy attribute", allocated by the device instance. 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/