From: Marc-Christian Petersen <m.c.p@gmx.net>
To: Benjamin LaHaise <bcrl@redhat.com>, Ingo Molnar <mingo@elte.hu>
Cc: linux-aio@kvack.org, linux-kernel@vger.kernel.org,
"J.A. Magallon" <jamagallon@able.es>,
Ruben Puettmann <ruben@puettmann.net>
Subject: Re: AIO together with SMPtimers-A0 oops and freezing
Date: Fri, 9 Aug 2002 22:03:00 +0200 [thread overview]
Message-ID: <200208092158.57656.m.c.p@gmx.net> (raw)
In-Reply-To: <20020806191446.E19564@redhat.com>
On Wednesday 07 August 2002 01:14, Benjamin LaHaise wrote:
Hi Benjamin,
>> Ben, I am using your AIO 20020619 patch + relevant fixes from the AIO
>> mailinglist together with your patch Ingo, SMPtimers-A0.
> Hmmm, the only problem I can see in the aio code wrt timer usage is
> the following. Does this patch make a difference? If not, I'm guessing
> that the problem is something in SMPtimers-A0 that aio happens to
> trigger. The only timer aio uses is for the timeout when waiting for an
> event, and the structure for that is put on the stack.
Perfect!! That, really small, patch makes it working perfectly. The system is
up for some hours now with stress testing Oracle without any oops() or any
other problem.
Thanks alot Ben! :-)
I'll let you know, after some days of stress testing Oracle, if it still
works. I expect it will do! :)
--
Kind regards
Marc-Christian Petersen
http://sourceforge.net/projects/wolk
PGP/GnuPG Key: 1024D/569DE2E3DB441A16
Fingerprint: 3469 0CF8 CA7E 0042 7824 080A 569D E2E3 DB44 1A16
Key available at www.keyserver.net. Encrypted e-mail preferred.
prev parent reply other threads:[~2002-08-09 20:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-05 17:20 AIO together with SMPtimers-A0 oops and freezing Marc-Christian Petersen
2002-08-06 20:07 ` Benjamin LaHaise
2002-08-06 22:35 ` J.A. Magallon
2002-08-06 23:14 ` Benjamin LaHaise
2002-08-06 23:34 ` J.A. Magallon
2002-08-09 20:03 ` Marc-Christian Petersen [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=200208092158.57656.m.c.p@gmx.net \
--to=m.c.p@gmx.net \
--cc=bcrl@redhat.com \
--cc=jamagallon@able.es \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=ruben@puettmann.net \
/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