mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: akpm@linux-foundation.org
Cc: John Stultz <johnstul@us.ibm.com>,
	maglyx@gmail.com, clemens@ladisch.de,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [patch 1/3] hpet: factor timer allocate from open
Date: Fri, 23 Jul 2010 15:07:36 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1007231500180.2616@localhost.localdomain> (raw)
In-Reply-To: <201007202223.o6KMNDZl021345@imap1.linux-foundation.org>

On Tue, 20 Jul 2010, akpm@linux-foundation.org wrote:

> From: Magnus Lynch <maglyx@gmail.com>
> 
> The current implementation of the /dev/hpet driver couples opening the
> device with allocating one of the (scarce) timers (aka comparators).  This
> is a limitation in that the main counter may be valuable to applications
> seeking a high-resolution timer who have no use for the interrupt
> generating functionality of the comparators.

And how exactly does this patch provide such functionality ? There is
no interface which allows you to access the counter itself. All what
this patch does is removing the allocation from open() and sprinkle
the allocation all over the place for _ZERO_ benefit.

I really have a hard time to understand why anything would open
/dev/hpet just to do nothing with it.

Thanks,

	tglx

       reply	other threads:[~2010-07-23 13:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201007202223.o6KMNDZl021345@imap1.linux-foundation.org>
2010-07-23 13:07 ` Thomas Gleixner [this message]
2010-07-26  6:20   ` Clemens Ladisch
2010-07-26 20:36   ` Mag

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=alpine.LFD.2.00.1007231500180.2616@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=clemens@ladisch.de \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maglyx@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome