From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264260AbUGCK2T (ORCPT ); Sat, 3 Jul 2004 06:28:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264479AbUGCK2T (ORCPT ); Sat, 3 Jul 2004 06:28:19 -0400 Received: from aun.it.uu.se ([130.238.12.36]:64249 "EHLO aun.it.uu.se") by vger.kernel.org with ESMTP id S264260AbUGCK2S (ORCPT ); Sat, 3 Jul 2004 06:28:18 -0400 Date: Sat, 3 Jul 2004 12:28:09 +0200 (MEST) Message-Id: <200407031028.i63AS9W3018392@harpo.it.uu.se> From: Mikael Pettersson To: akpm@osdl.org Subject: Re: [PATCH][2.6.7-mm5] perfctr low-level documentation Cc: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2 Jul 2004 15:44:14 -0700, Andrew Morton wrote: >Mikael Pettersson wrote: >> >> I'm >> considering Christoph Hellwig's suggestion of moving >> the API back to /proc//, but with multiple files >> and open/read/write/mmap instead of ioctl. I believe I >> can make that work, but it would take a couple of days >> to implement properly. Please indicate if you would like >> this change or not. > >What would be the advantages of such a change? Eliminating the 6 or so new syscalls I was forced to add when nuking the old ioctl() API. There would be a /proc///perfctr/ directory with files representing the control data, counter state, general info, and auxiliary control ops. /Mikael