From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Higdon Date: Tue, 11 Jul 2006 18:37:54 +0000 Subject: Re: [PATCH] ia64: change usermode HZ to 250 Message-Id: <20060711183754.GB734242@sgi.com> List-Id: References: <617E1C2C70743745A92448908E030B2A27FC5F@scsmsx411.amr.corp.intel.com> <1151578928.23785.0.camel@localhost.localdomain> <44A3AFFB.2000203@sgi.com> <1151578513.3122.22.camel@laptopd505.fenrus.org> <20060708001427.GA723842@sgi.com> <1152340963.3120.0.camel@laptopd505.fenrus.org> <20060710202228.GA732959@sgi.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: David Mosberger-Tang Cc: Arjan van de Ven , Jes Sorensen , Alan Cox , "Luck, Tony" , John Daiker , John Hawkes , Tony Luck , Andrew Morton , linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org, Jack Steiner , Dan Higgins On Mon, Jul 10, 2006 at 09:01:53PM -0600, David Mosberger-Tang wrote: > Note that Alan didn't claim that *all* (Linux-supported) architectures > expose a constant user HZ, only the "mainstream" ones. I won't get > into the debate as to what qualifies as "mainstream", but clearly IA64 > does not (and should not) expose a constant value, since there were no > legacy-binary-issue and we chose to insist that apps should uses > sysconf() or equivalent if they need to know the clocktick. > > --david Okay. So what do you think about changing the value in param.h from 1024, so that it matches the new common value of 250, or is it best just to leave it at 1024 and let applications that use it get the wrong result? jeremy