[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200711142203.23982.nickpiggin@yahoo.com.au>
Date: Wed, 14 Nov 2007 22:03:23 +1100
From: Nick Piggin <nickpiggin@...oo.com.au>
To: Chuck Ebbert <cebbert@...hat.com>
Cc: Paul Mackerras <paulus@...ba.org>,
David Miller <davem@...emloft.net>, hch@...radead.org,
akpm@...ux-foundation.org, gregkh@...e.de, mucci@...utk.edu,
eranian@....hp.com, wcohen@...hat.com, robert.richter@....com,
linux-kernel@...r.kernel.org, andi@...stfloor.org
Subject: Re: [perfmon] Re: [perfmon2] perfmon2 merge news
On Thursday 15 November 2007 09:56, Chuck Ebbert wrote:
> On 11/14/2007 05:17 AM, Nick Piggin wrote:
> > But in general, for special files, I guess the response is usually
> > some structured data (that is not visible at the syscall layer).
> > So I don't see a big problem to have a similarly arbitrarily
> > structured request.
>
> IOW, an ioctl.
In the same way a read of structured data from a special file
"is an" ioctl, yeah. You could implement either with an ioctl.
The main difference is they have more explicitly typed interfaces
Whether that's enough argument (and if Paul's proposal is widely
usable enough) is another question. Which I won't try to answer.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists