All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Marcin Obara <marcin_obara@users.sourceforge.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Intel Management Engine Interface
Date: Wed, 13 Aug 2008 11:18:50 -0700	[thread overview]
Message-ID: <20080813181850.GD4886@kroah.com> (raw)
In-Reply-To: <ea8d860a0808130016w646307few3cc6385caf9b1ec7@mail.gmail.com>

On Wed, Aug 13, 2008 at 08:16:02AM +0100, Marcin Obara wrote:
> 2008/8/13 Greg KH <greg@kroah.com>:
> > On Mon, Aug 11, 2008 at 09:23:01PM +0200, Marcin Obara wrote:
> >> +/* IOCTL commands */
> >> +#define IOCTL_HECI_GET_VERSION \
> >> +    _IOWR('H' , 0x0, struct heci_message_data)
> >
> > This can easily be a sysfs file, why not do that instead?
> >
> sysfs file would require additional file handle used by every userspace client.

So, is that really a great overhead?

> GET_VERSION is called frequently

Why?  Shouldn't it only be called once?

>, and sysfs file would create extra overhead.

Have you measured it?

> With ioctl - only one file handle is used, and userspace client logic
> is simpler.

But the kernel is messier and we are trying to not add any more ioctls
to it.  Especially for trivial things like the version number of the
hardware device.

> Normal flow looks like:
> 
> open
> ioctl(GET_VERSION)

Great, do an additional open/read/close here for the version, I think
you will find it pretty trivial to do :)

thanks,

greg k-h

  reply	other threads:[~2008-08-13 18:20 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17 18:27 [PATCH] Intel Management Engine Interface Marcin Obara
2008-07-18  0:00 ` Randy Dunlap
2008-07-18  5:44 ` Marcin Obara
2008-07-18 17:39   ` Marcin Obara
2008-07-18 19:23     ` Marcin Obara
2008-07-18 20:30       ` Marcin Obara
2008-07-23 18:00         ` Marcin Obara
2008-08-11 19:23           ` Marcin Obara
2008-08-12  4:53             ` Andrew Morton
2008-08-12 16:15               ` Jiri Slaby
2008-08-12 19:24                 ` Marcin Obara
2008-08-12 19:24                   ` Alan Cox
2008-08-12 21:03                   ` Arjan van de Ven
2008-08-13  0:58             ` Greg KH
2008-08-13  7:16               ` Marcin Obara
2008-08-13 18:18                 ` Greg KH [this message]
2008-08-13 19:48                   ` Marcin Obara
2008-08-14  0:23                     ` Greg KH
2008-07-18  9:27 ` Andi Kleen
2008-07-18 10:51   ` Marcin Obara
2008-07-18 11:02     ` Andi Kleen
2008-07-18 11:33       ` Marcin Obara
2008-08-06 16:56 ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2008-05-20  0:11 Anas Nashif
2008-05-20  0:28 ` Andrew Morton
2008-05-20 19:02   ` Gabriel C
2008-05-22 16:51   ` Pavel Machek
2008-05-20 15:42 ` Maxim Levitsky
2008-05-20 20:35 ` Carlos R. Mafra
2008-05-20 22:27 ` Jiri Slaby
2008-05-23  7:04 ` Pavel Machek
2007-12-11 17:32 Anas Nashif
2007-12-11 18:14 ` Andi Kleen
2007-12-11 18:38   ` Anas Nashif
2007-12-11 18:53     ` Andi Kleen
2007-12-11 19:02       ` David Miller
2007-12-11 19:47         ` Andi Kleen
2007-12-11 19:06       ` Anas Nashif
2007-12-11 19:48         ` Andi Kleen
2007-12-12 15:00         ` Mark Lord
2007-12-12 16:17           ` Andi Kleen
2007-12-12  8:48 ` Alexander E. Patrakov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080813181850.GD4886@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcin_obara@users.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.