From: "J.A. Magallon" <jamagallon@able.es>
To: Benjamin LaHaise <bcrl@redhat.com>
Cc: Marc-Christian Petersen <mcp@linux-systeme.de>,
linux-aio@kvack.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@elte.hu>
Subject: Re: AIO together with SMPtimers-A0 oops and freezing
Date: Wed, 7 Aug 2002 00:35:50 +0200 [thread overview]
Message-ID: <20020806223550.GC2733@werewolf.able.es> (raw)
In-Reply-To: <20020806160724.A19564@redhat.com>; from bcrl@redhat.com on Tue, Aug 06, 2002 at 22:07:24 +0200
On 2002.08.06 Benjamin LaHaise wrote:
>On Mon, Aug 05, 2002 at 07:20:29PM +0200, Marc-Christian Petersen wrote:
>> Hi Ben, Hi Ingo,
>
>> 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.
>
Hmm, I forgot to comment, but I apply smptimers on top of latest -aa, that
includes aio (is it different implementation?), and the kernel works fine.
--
J.A. Magallon \ Software is like sex: It's better when it's free
mailto:jamagallon@able.es \ -- Linus Torvalds, FSF T-shirt
Linux werewolf 2.4.19-jam0, Mandrake Linux 9.0 (Cooker) for i586
gcc (GCC) 3.2 (Mandrake Linux 9.0 3.2-0.2mdk)
next prev parent reply other threads:[~2002-08-06 22:32 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 [this message]
2002-08-06 23:14 ` Benjamin LaHaise
2002-08-06 23:34 ` J.A. Magallon
2002-08-09 20:03 ` Marc-Christian Petersen
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=20020806223550.GC2733@werewolf.able.es \
--to=jamagallon@able.es \
--cc=bcrl@redhat.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcp@linux-systeme.de \
--cc=mingo@elte.hu \
/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.