From: Jeff Moyer <jmoyer@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: akpm@linux-foundation.org, zach.brown@oracle.com,
linux-aio@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] aio: invalidate async directio writes
Date: Wed, 18 Jun 2008 15:45:28 -0400 [thread overview]
Message-ID: <x49abhiy1bb.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <20080618182223.GA14851@infradead.org> (Christoph Hellwig's message of "Wed, 18 Jun 2008 14:22:23 -0400")
Christoph Hellwig <hch@infradead.org> writes:
> On Wed, Jun 18, 2008 at 02:09:51PM -0400, Jeff Moyer wrote:
>> + /* For async O_DIRECT writes, we need to invalidate the
>> + * page cache after the write completes. Kick off a
>> + * workqueue to do this and issue the completion in process
>> + * context.
>> + */
>> + if (dio->rw == READ) {
>> + int ret = dio_complete(dio, dio->iocb->ki_pos, 0);
>> + aio_complete(dio->iocb, ret, 0);
>> + kfree(dio);
>> + } else {
>> + unsigned long flags;
>> + spin_lock_irqsave(&iocb_completion_list_lock, flags);
>> + list_add(&dio->done_list, &iocb_completion_list);
>> + spin_unlock_irqrestore(&iocb_completion_list_lock, flags);
>> + schedule_work(&aio_complete_work);
>> + }
>
> Can we please move all these aio_complete calls to user context? Having
> AIO contexts completing from irq context is a major pain for complex
> filesystems like XFS.
Can you help me understand why this is a pain? I'm having trouble
making the connection.
Thanks!
Jeff
next prev parent reply other threads:[~2008-06-18 19:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 18:09 Jeff Moyer
2008-06-18 18:22 ` Christoph Hellwig
2008-06-18 19:45 ` Jeff Moyer [this message]
2008-06-18 19:48 ` Christoph Hellwig
2008-06-19 7:51 ` Peter Zijlstra
2008-06-19 13:50 ` Jeff Moyer
2008-06-19 13:58 ` Peter Zijlstra
2008-06-19 14:05 ` Jeff Moyer
2008-06-19 17:50 ` Zach Brown
2008-06-19 17:23 ` Zach Brown
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=x49abhiy1bb.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--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
all inboxes | Powered by JetHome®