From: Arjan van de Ven <arjanv-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Hugh Dickins <hugh-DTz5qymZ9yRBDgjK7y7TUQ@public.gmane.org>
Cc: "Grover,
Andrew" <andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Arjan van de Ven <arjanv-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Andrew Morton <akpm-LL/9OlyS9hIAvxtiuMwx3w@public.gmane.org>,
torvalds-Lhe3bsMrZseB+jHODAdFcQ@public.gmane.org,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [BK PATCH] acpismp=force fix
Date: Mon, 23 Jun 2003 11:54:08 +0000 [thread overview]
Message-ID: <20030623115408.E23874@devserv.devel.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0306231224590.1648-100000-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>; from hugh-DTz5qymZ9yRBDgjK7y7TUQ@public.gmane.org on Mon, Jun 23, 2003 at 12:46:38PM +0100
On Mon, Jun 23, 2003 at 12:46:38PM +0100, Hugh Dickins wrote:
> Certainly reliance on "acpismp=force" should be removed if it's crept
> back in. But what should we do about "noht"? Wave a fond goodbye,
> and remove it's associated code and Documentation from 2.4 and 2.5
> trees, rely on changing the BIOS setting instead? Or bring it back
> into action?
for 2.4 it's no problem to honor it really code wise; and it's
useful for machines where you can't disable HT in the bios but where
your particular workload doesn't positively benefit from HT.
WARNING: multiple messages have this Message-ID (diff)
From: Arjan van de Ven <arjanv@redhat.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: "Grover, Andrew" <andrew.grover@intel.com>,
Arjan van de Ven <arjanv@redhat.com>,
Andrew Morton <akpm@digeo.com>,
torvalds@transmeta.com, acpi-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [BK PATCH] acpismp=force fix
Date: Mon, 23 Jun 2003 11:54:08 +0000 [thread overview]
Message-ID: <20030623115408.E23874@devserv.devel.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0306231224590.1648-100000@localhost.localdomain>; from hugh@veritas.com on Mon, Jun 23, 2003 at 12:46:38PM +0100
On Mon, Jun 23, 2003 at 12:46:38PM +0100, Hugh Dickins wrote:
> Certainly reliance on "acpismp=force" should be removed if it's crept
> back in. But what should we do about "noht"? Wave a fond goodbye,
> and remove it's associated code and Documentation from 2.4 and 2.5
> trees, rely on changing the BIOS setting instead? Or bring it back
> into action?
for 2.4 it's no problem to honor it really code wise; and it's
useful for machines where you can't disable HT in the bios but where
your particular workload doesn't positively benefit from HT.
next prev parent reply other threads:[~2003-06-23 11:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 7:43 [BK PATCH] acpismp=force fix Grover, Andrew
2003-06-23 7:43 ` Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A84725A302-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2003-06-23 7:58 ` Andrew Morton
2003-06-23 7:58 ` Andrew Morton
2003-06-23 8:01 ` Arjan van de Ven
2003-06-23 8:01 ` Arjan van de Ven
[not found] ` <1056355301.1699.6.camel-PDvaWZGbcxi0rsOeZxrteAC/G2K4zDHf@public.gmane.org>
2003-06-23 11:46 ` Hugh Dickins
2003-06-23 11:46 ` Hugh Dickins
[not found] ` <Pine.LNX.4.44.0306231224590.1648-100000-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2003-06-23 11:54 ` Arjan van de Ven [this message]
2003-06-23 11:54 ` Arjan van de Ven
-- strict thread matches above, loose matches on Subject: below --
2003-06-26 21:37 Brown, Len
2003-06-26 21:37 ` Brown, Len
[not found] ` <A5974D8E5F98D511BB910002A50A66470B981205-MgY+aF+eRfZviC08c4yzC1DQ4js95KgL@public.gmane.org>
2003-06-27 11:58 ` Hugh Dickins
2003-06-27 11:58 ` Hugh Dickins
[not found] ` <Pine.LNX.4.44.0306271221110.1197-100000-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2003-06-27 11:59 ` Arjan van de Ven
2003-06-27 11:59 ` Arjan van de Ven
2003-06-30 15:42 ` Juan Quintela
2003-06-30 15:42 ` Juan Quintela
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=20030623115408.E23874@devserv.devel.redhat.com \
--to=arjanv-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=akpm-LL/9OlyS9hIAvxtiuMwx3w@public.gmane.org \
--cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=hugh-DTz5qymZ9yRBDgjK7y7TUQ@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=torvalds-Lhe3bsMrZseB+jHODAdFcQ@public.gmane.org \
/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.