From: "KOSAKI Motohiro" <kosaki.motohiro@jp.fujitsu.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "Yu, Fenghua" <fenghua.yu@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-ia64@vger.kernel.org,
"Hidetoshi Seto" <seto.hidetoshi@jp.fujitsu.com>,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: [2.6.25-rc5-mm1][regression] ia64: hackbench doesn't finish >12 hour
Date: Sat, 5 Apr 2008 14:03:03 +0900 [thread overview]
Message-ID: <2f11576a0804042203w128d6108i58498e6b86ab87d3@mail.gmail.com> (raw)
In-Reply-To: <1FE6DD409037234FAB833C420AA843EC01011FE8@orsmsx424.amr.corp.intel.com>
> I've just pushed a new version of this patch into my test tree (so
> it will show up in -mm and linux-next when they pull and rebuild).
> It now uses the Piggin/Wilcox "spinaphore" primitives. It passes
> all my tests, and some runs of "hackbench" that tried to match the
> tests that failed before at Fujitsu by forcing moderate amounts of
> swapping.
Great!
prev parent reply other threads:[~2008-04-05 5:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-17 11:18 KOSAKI Motohiro
2008-03-17 11:51 ` KOSAKI Motohiro
2008-03-17 16:09 ` Luck, Tony
2008-03-17 23:43 ` KOSAKI Motohiro
2008-03-17 17:38 ` Luck, Tony
2008-03-17 23:44 ` KOSAKI Motohiro
2008-03-18 0:36 ` Yu, Fenghua
2008-03-18 0:47 ` KOSAKI Motohiro
2008-03-19 0:14 ` Yu, Fenghua
2008-03-19 23:23 ` Peter Zijlstra
2008-03-19 23:50 ` [2.6.25-rc5-mm1][regression] ia64: hackbench doesn't finish>12 hour Yu, Fenghua
2008-03-20 3:39 ` [2.6.25-rc5-mm1][regression] ia64: hackbench doesn't finish >12 hour Luming Yu
2008-03-20 4:51 ` KOSAKI Motohiro
2008-03-20 16:04 ` [2.6.25-rc5-mm1][regression] ia64: hackbench doesn't finish>12 hour Luck, Tony
2008-03-20 16:16 ` Peter Zijlstra
2008-03-20 17:23 ` [2.6.25-rc5-mm1][regression] ia64: hackbench doesn't finish>12hour Luck, Tony
2008-04-04 23:52 ` [2.6.25-rc5-mm1][regression] ia64: hackbench doesn't finish >12 hour Luck, Tony
2008-04-05 5:03 ` KOSAKI Motohiro [this message]
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=2f11576a0804042203w128d6108i58498e6b86ab87d3@mail.gmail.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=fenghua.yu@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seto.hidetoshi@jp.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®