From: Mingming <cmm@us.ibm.com>
To: Jan Kara <jack@suse.cz>
Cc: Theodore Tso <tytso@mit.edu>,
linux-ext4@vger.kernel.org, Eric Sandeen <sandeen@redhat.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [PATCH 2/2 V3] allow direct IO to fallocate and holes
Date: Wed, 09 Sep 2009 13:51:02 -0700 [thread overview]
Message-ID: <1252529462.19097.170.camel@mingming-laptop> (raw)
In-Reply-To: <20090907215746.GA11748@duck.suse.cz>
On Mon, 2009-09-07 at 23:57 +0200, Jan Kara wrote:
> Hi Minming,
>
> the patch looks cleaner now.
>
Hi Jan
Thanks for your review:)
> On Thu 03-09-09 17:44:50, Mingming wrote:
> > Index: linux-2.6.31-rc4/fs/ext4/inode.c
> > ===================================================================
> > --- linux-2.6.31-rc4.orig/fs/ext4/inode.c
> > +++ linux-2.6.31-rc4/fs/ext4/inode.c
> ...
> > +#define DIO_AIO 0x1
> This flag isn't set anywhere...
>
> > +static void ext4_free_io_end(ext4_io_end_t *io)
> > +{
> > + kfree(io);
> > +}
> > +
> > +/*
> > + * IO write completion for unwritten extents.
> > + *
> > + * check a range of space and convert unwritten extents to written.
> > + */
> > +static void ext4_end_dio_unwritten(struct work_struct *work)
> > +{
> > + ext4_io_end_t *io = container_of(work, ext4_io_end_t, work);
> > + struct inode *inode = io->inode;
> > + loff_t offset = io->offset;
> > + size_t size = io->size;
> > + int ret = 0;
> > + int aio = io->flag & DIO_AIO;
> > +
> > + if (aio)
> > + mutex_lock(&inode->i_mutex);
> > + if (offset + size <= i_size_read(inode))
> > + ret = ext4_convert_unwritten_extents(inode, offset, size);
> > +
> > + if (ret < 0)
> > + printk(KERN_EMERG "%s: failed to convert unwritten"
> > + "extents to written extents, error is %d\n",
> > + __func__, ret);
> > +
> > + ext4_free_io_end(io);
> > + if (aio)
> > + mutex_unlock(&inode->i_mutex);
> > +}
> > +
> > +static ext4_io_end_t *ext4_init_io_end (struct inode *inode, unsigned int flag)
> > +{
> > + ext4_io_end_t *io = NULL;
> > +
> > + io = kmalloc(sizeof(*io), GFP_NOFS);
> > +
> > + if (io) {
> > + io->inode = inode;
> You should __iget() the inode here and iput() it in the end IO handler at
> least in the AIO case so that the inode remains pinned in memory.
>
I just tried to add this, but hit some errors. I will dig more.
> > + io->flag = flag;
> > + io->offset = 0;
> > + io->size = 0;
> > + io->error = 0;
> > + INIT_WORK(&io->work, ext4_end_dio_unwritten);
> > + }
> > +
> > + return io;
> > +}
> > +
> > +static void ext4_end_io_dio(struct kiocb *iocb, loff_t offset,
> > + ssize_t size, void *private)
> > +{
> > + ext4_io_end_t *io_end = iocb->private;
> > + struct workqueue_struct *wq;
> > +
> > + /* if not hole or unwritten extents, just simple return */
> > + if (!io_end || !size || !iocb->private)
> > + return;
> > + io_end->offset = offset;
> > + io_end->size = size;
> > + wq = EXT4_SB(io_end->inode->i_sb)->dio_unwritten_wq;
> > +
> > + /* We need to convert unwritten extents to written */
> > + queue_work(wq, &io_end->work);
> > +
> > + if (is_sync_kiocb(iocb))
> > + flush_workqueue(wq);
> You have spaces instead of tabs above.
>
> I think fsync() still won't work correctly since it can happen user sees
> AIO completed, calls fsync() that completes,
hmm, does fsync() ensure user sees AIO data completed?
> but the conversion of extents
> still has not happened because the conversion thread as not run yet.
> The simple solution would be so flush_workqueue() from ext4_sync_fs()
> and ext4_fsync(). But that would needlessly make fsync() wait for
> conversion in unrelated files. More sophisticated solution would be to
> attach io_end structures to the inode and do the work described by them
> in ext4_fsync() (ext4_sync_fs() is fine doing flush_workqueue() since it
> has to do all the work anyway). But in this solution you would have to be
> careful to avoid races of fsync() and the completion thread.
Yeah maybe link the list of io_end structures to the inode, and use a
lock to protect that link... All AIO related issues (including ext3)
seems should addressed in another patch, you agree? Or we should address
them here?
Mingming
> Besides these problems the patch looks good.
>
> Honza
next prev parent reply other threads:[~2009-09-09 20:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 0:44 [PATCH 2/2 V3] allow direct IO to fallocate and holes Mingming
2009-09-07 21:57 ` Jan Kara
2009-09-09 20:51 ` Mingming [this message]
2009-09-10 7:57 ` Aneesh Kumar K.V
2009-09-10 8:54 ` Jan Kara
2009-09-10 20:17 ` Mingming
2009-09-14 11:25 ` Jan Kara
2009-09-18 22:29 ` Mingming
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=1252529462.19097.170.camel@mingming-laptop \
--to=cmm@us.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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