From: Zoltan Menyhart <Zoltan.Menyhart_AT_bull.net@nospam.org>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Who owns those locks ?
Date: Tue, 08 Jun 2004 17:38:54 +0200 [thread overview]
Message-ID: <40C5DD8E.8DD37D16@nospam.org> (raw)
In-Reply-To: 200406080905.52673.bjorn.helgaas@hp.com
Bjorn Helgaas wrote:
>
> On Tuesday 08 June 2004 2:03 am, Zoltan Menyhart wrote:
> > - You keep my code, it is correct for a memory size up to 16 Tbytes.
>
> Many if not most large machines have sparse address spaces,
> so you may have memory at an address that will cause a
> problem even if the actual amount of memory is much smaller.
>
> The main point is that I wouldn't want a time bomb that
> will silently fail when somebody happens to boot on such
> a machine. Whether that's avoided by a "miraculous" bit,
> throwing away problem pages at boot-time, avoiding task
> allocation at specific addresses, etc., is secondary.
I see.
No use to make it too much complicated.
There is always the option CONFIG_DEBUG_SPINLOCK.
On our no-more-than-512-Gbyte-machine, this small stuff
"saved my life" twice.
I just wanted to share it...
Regards,
Zoltán
next prev parent reply other threads:[~2004-06-08 15:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 9:56 Who owns those locks ? Zoltan Menyhart
2004-05-13 18:43 ` Anton Blanchard
2004-06-03 17:39 ` Bjorn Helgaas
2004-06-07 8:58 ` Zoltan Menyhart
2004-06-07 15:06 ` Bjorn Helgaas
2004-06-08 8:03 ` Zoltan Menyhart
2004-06-08 15:05 ` Bjorn Helgaas
2004-06-08 15:38 ` Zoltan Menyhart [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-12 10:25 Luck, Tony
2004-05-12 11:06 ` Zoltan Menyhart
2004-05-12 11:43 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=40C5DD8E.8DD37D16@nospam.org \
--to=zoltan.menyhart_at_bull.net@nospam.org \
--cc=Zoltan.Menyhart@bull.net \
--cc=bjorn.helgaas@hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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