From: Jeff Garzik <jgarzik@pobox.com>
To: Andrew Morton <akpm@osdl.org>
Cc: torvalds@osdl.org, benh@kernel.crashing.org,
linux-kernel@vger.kernel.org,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: page fault scalability patch V12 [0/7]: Overview and performance tests
Date: Thu, 02 Dec 2004 02:00:37 -0500 [thread overview]
Message-ID: <41AEBD95.7030804@pobox.com> (raw)
In-Reply-To: <20041201223441.3820fbc0.akpm@osdl.org>
Andrew Morton wrote:
> We need an -rc3 yet. And I need to do another pass through the
> regressions-since-2.6.9 list. We've made pretty good progress there
> recently. Mid to late December is looking like the 2.6.10 date.
another for that list, BTW:
I am currently chasing a 2.6.8->2.6.9 SATA regression, which causes
ata_piix (Intel ICH5/6/7) to not-find some SATA devices on x86-64 SMP,
but works on UP. Potentially related to >=4GB of RAM.
Details, in case anyone is interested:
Unless my code is screwed up (certainly possible), PIO data-in [using
the insw() call] seems to return all zeroes on a true-blue SMP machine,
for the identify-device command. When this happens, libata (correctly)
detects a bad id page and bails. (problem doesn't show up on single CPU
w/ HT)
What changed from 2.6.8 to 2.6.9 is
2.6.8:
bitbang ATA taskfile registers (loads command)
bitbang ATA data register (read id page)
2.6.9:
bitbang ATA taskfile registers
queue_work()
workqueue thread bitbangs ATA data register (read id page)
So I wonder if <something> doesn't like CPU 0 sending I/O traffic to the
on-board SATA PCI device, then immediately after that, CPU 1 sending I/O
traffic.
Anyway, back to debugging... :)
Jeff
next parent reply other threads:[~2004-12-02 7:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0411221457240.2970-100000@localhost.localdomain>
[not found] ` <Pine.LNX.4.58.0411221343410.22895@schroedinger.engr.sgi.com>
[not found] ` <Pine.LNX.4.58.0411221419440.20993@ppc970.osdl.org>
[not found] ` <Pine.LNX.4.58.0411221424580.22895@schroedinger.engr.sgi.com>
[not found] ` <Pine.LNX.4.58.0411221429050.20993@ppc970.osdl.org>
[not found] ` <Pine.LNX.4.58.0412011539170.5721@schroedinger.engr.sgi.com>
[not found] ` <Pine.LNX.4.58.0412011608500.22796@ppc970.osdl.org>
[not found] ` <41AEB44D.2040805@pobox.com>
[not found] ` <20041201223441.3820fbc0.akpm@osdl.org>
2004-12-02 7:00 ` Jeff Garzik [this message]
2004-12-02 7:05 ` page fault scalability patch V12 [0/7]: Overview and performance tests Benjamin Herrenschmidt
2004-12-02 7:11 ` Jeff Garzik
2004-12-02 11:16 ` Benjamin Herrenschmidt
2004-12-02 14:30 ` Andy Warner
2005-01-06 23:40 ` Jeff Garzik
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=41AEBD95.7030804@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).