From: Zach Brown <zach.brown@oracle.com>
To: Nikanth Karthikesan <knikanth@suse.de>
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: Mon, 30 Jun 2008 10:43:26 -0700 [thread overview]
Message-ID: <48691B3E.5040402@oracle.com> (raw)
In-Reply-To: <200806260930.59836.knikanth@suse.de>
Nikanth Karthikesan wrote:
> aio_complete() is never called from interrupt context. It is called from user
> context or worker threads. Remove disabling interrupts and for kmap_atomic use
> KM_USER slots instead of KM_IRQ slots.
How are you testing these patches?
- z
next prev parent reply other threads:[~2008-06-30 17:43 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 [this message]
2008-07-01 8:29 ` Nikanth Karthikesan
2008-07-01 19:50 ` Zach Brown
2008-07-02 5:00 ` Nikanth Karthikesan
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=48691B3E.5040402@oracle.com \
--to=zach.brown@oracle.com \
--cc=bcrl@kvack.org \
--cc=jmoyer@redhat.com \
--cc=knikanth@suse.de \
--cc=linux-aio@kvack.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