public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nikanth Karthikesan <knikanth@suse.de>
To: Zach Brown <zach.brown@oracle.com>
Cc: linux-aio@kvack.org, linux-kernel@vger.kernel.org,
	Benjamin LaHaise <bcrl@kvack.org>, Jeff Moyer <jmoyer@redhat.com>
Subject: Re: [PATCH] aio: aio_complete() will never be called in interrupt context
Date: Wed, 2 Jul 2008 10:30:42 +0530	[thread overview]
Message-ID: <200807021030.43009.knikanth@suse.de> (raw)
In-Reply-To: <486A8A92.6050200@oracle.com>

On Wednesday 02 July 2008 01:20:42 Zach Brown wrote:
> > I did not do any specific testing. Just ran multiple instances of a
> > file-copy utility that uses aio and a bit of Chris Mason's aio-stress.
>
> Are you running these tests under a kernel with lockdep enabled?
>

Yes. I have CONFIG_LOCKDEP_SUPPORT=y and did not get any warning messages.

> > p.s: Is the archives of the linux-aio list available somewhere? The URL
> > in the mail footer seems to be unavailable.
>
> The very first google hit for 'linux-aio mailing list archive' works:
>
>   http://marc.info/?l=linux-aio
>

Thanks and sorry for the noise.

But it would be nice if the link in the mail footer(www.kvack.org/aio) is 
changed to an active link or removed. The link redirects to 
www.kvack.org/~blah/aio/ which returns 404

Thanks
Nikanth Karthikesan

  reply	other threads:[~2008-07-02  4:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-26  4:00 [PATCH] aio: aio_complete() will never be called in interrupt context Nikanth Karthikesan
2008-06-27 13:11 ` Jeff Moyer
2008-06-30  5:51   ` Nikanth Karthikesan
2008-06-30 17:43 ` Zach Brown
2008-07-01  8:29   ` Nikanth Karthikesan
2008-07-01 19:50     ` Zach Brown
2008-07-02  5:00       ` Nikanth Karthikesan [this message]
2008-07-02 16:38         ` Zach Brown
2008-07-02 17:59           ` Benjamin LaHaise

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=200807021030.43009.knikanth@suse.de \
    --to=knikanth@suse.de \
    --cc=bcrl@kvack.org \
    --cc=jmoyer@redhat.com \
    --cc=linux-aio@kvack.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zach.brown@oracle.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