All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jes Sorensen <jes@sgi.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
	John Daiker <jdaiker@osdl.org>, John Hawkes <hawkes@sgi.com>,
	Arjan van de Ven <arjan@infradead.org>,
	Tony Luck <tony.luck@gmail.com>, Andrew Morton <akpm@osdl.org>,
	linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jack Steiner <steiner@sgi.com>, Dan Higgins <djh@sgi.com>,
	Jeremy Higdon <jeremy@sgi.com>
Subject: Re: [PATCH] ia64: change usermode HZ to 250
Date: Thu, 29 Jun 2006 11:34:59 +0000	[thread overview]
Message-ID: <1151580899.23785.7.camel@localhost.localdomain> (raw)
In-Reply-To: <44A3AFFB.2000203@sgi.com>

Ar Iau, 2006-06-29 am 12:48 +0200, ysgrifennodd Jes Sorensen:
> > No need, all current mainstream architectures expose a constant user HZ.
> 
> But you are still going to have the issue where someone installs their
> own kernel and apps will break because of this? Getting the distros to
> stop publishing a constant HZ is probably the right solution, but more
> difficult :(

Read what I said - "all current mainstream architectures expose a
constant user HZ".

The HZ used by the kernel is independant of the HZ seen for /proc etc




WARNING: multiple messages have this Message-ID (diff)
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jes Sorensen <jes@sgi.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
	John Daiker <jdaiker@osdl.org>, John Hawkes <hawkes@sgi.com>,
	Arjan van de Ven <arjan@infradead.org>,
	Tony Luck <tony.luck@gmail.com>, Andrew Morton <akpm@osdl.org>,
	linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jack Steiner <steiner@sgi.com>, Dan Higgins <djh@sgi.com>,
	Jeremy Higdon <jeremy@sgi.com>
Subject: Re: [PATCH] ia64: change usermode HZ to 250
Date: Thu, 29 Jun 2006 12:34:59 +0100	[thread overview]
Message-ID: <1151580899.23785.7.camel@localhost.localdomain> (raw)
In-Reply-To: <44A3AFFB.2000203@sgi.com>

Ar Iau, 2006-06-29 am 12:48 +0200, ysgrifennodd Jes Sorensen:
> > No need, all current mainstream architectures expose a constant user HZ.
> 
> But you are still going to have the issue where someone installs their
> own kernel and apps will break because of this? Getting the distros to
> stop publishing a constant HZ is probably the right solution, but more
> difficult :(

Read what I said - "all current mainstream architectures expose a
constant user HZ".

The HZ used by the kernel is independant of the HZ seen for /proc etc




  parent reply	other threads:[~2006-06-29 11:34 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-27 22:01 [PATCH] ia64: change usermode HZ to 250 hawkes
2006-06-27 22:01 ` hawkes
2006-06-27 22:26 ` Luck, Tony
2006-06-27 22:26   ` Luck, Tony
2006-06-27 23:09   ` Lee Revell
2006-06-27 23:09     ` Lee Revell
2006-06-28  8:43   ` Arjan van de Ven
2006-06-28  8:43     ` Arjan van de Ven
2006-06-28 10:47     ` Alan Cox
2006-06-28 10:47       ` Alan Cox
2006-06-28 10:34       ` Arjan van de Ven
2006-06-28 10:34         ` Arjan van de Ven
2006-06-28 14:46         ` Christoph Lameter
2006-06-28 14:46           ` Christoph Lameter
2006-06-28  8:39 ` Arjan van de Ven
2006-06-28  8:39   ` Arjan van de Ven
2006-06-28 15:43   ` John Hawkes
2006-06-28 15:43     ` John Hawkes
2006-06-28 16:21     ` Alan Cox
2006-06-28 16:21       ` Alan Cox
2006-06-28 16:11       ` John Daiker
2006-06-28 16:11         ` John Daiker
2006-06-28 16:50         ` Alan Cox
2006-06-28 16:50           ` Alan Cox
2006-06-28 17:36 ` Luck, Tony
2006-06-28 17:36   ` Luck, Tony
2006-06-29  9:37   ` Jes Sorensen
2006-06-29  9:37     ` Jes Sorensen
2006-06-29 10:46     ` Alan Cox
2006-06-29 11:02       ` Alan Cox
2006-06-29 10:48       ` Jes Sorensen
2006-06-29 10:48         ` Jes Sorensen
2006-06-29 10:55         ` Arjan van de Ven
2006-06-29 10:55           ` Arjan van de Ven
2006-06-29 12:56           ` Jes Sorensen
2006-06-29 12:56             ` Jes Sorensen
2006-07-08  0:14           ` Jeremy Higdon
2006-07-08  0:14             ` Jeremy Higdon
2006-07-08  2:51             ` Tony Luck
2006-07-08  2:51               ` Tony Luck
2006-07-08  6:42             ` Arjan van de Ven
2006-07-08  6:42               ` Arjan van de Ven
2006-07-08 13:07               ` David Mosberger-Tang
2006-07-08 13:07                 ` David Mosberger-Tang
2006-07-10 20:22                 ` Jeremy Higdon
2006-07-10 20:22                   ` Jeremy Higdon
2006-07-11  3:01                   ` David Mosberger-Tang
2006-07-11  3:01                     ` David Mosberger-Tang
2006-07-11  9:53                     ` Alan Cox
2006-07-11 10:10                       ` Alan Cox
2006-07-11 18:37                     ` Jeremy Higdon
2006-07-11 18:37                       ` Jeremy Higdon
2006-07-12  2:02                       ` David Mosberger-Tang
2006-07-12  2:02                         ` David Mosberger-Tang
2006-06-29 11:34         ` Alan Cox [this message]
2006-06-29 11:34           ` Alan Cox
2006-06-29 14:09 ` Albert Cahalan
2006-06-29 14:09   ` Albert Cahalan
2006-07-09 19:18 ` Luck, Tony
2006-07-09 19:18   ` Luck, Tony

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=1151580899.23785.7.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=djh@sgi.com \
    --cc=hawkes@sgi.com \
    --cc=jdaiker@osdl.org \
    --cc=jeremy@sgi.com \
    --cc=jes@sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steiner@sgi.com \
    --cc=tony.luck@gmail.com \
    --cc=tony.luck@intel.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 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.