From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: Non-blocking inode locking in IO completion
Date: Thu, 18 Feb 2010 07:35:13 -0500 [thread overview]
Message-ID: <20100218123512.GA6016@infradead.org> (raw)
In-Reply-To: <20100217211312.GQ28392@discord.disaster>
On Thu, Feb 18, 2010 at 08:13:12AM +1100, Dave Chinner wrote:
> > The patch looks good to me - while I hate introducing random delay()
> > calls I don't really see a way around this.
>
> I thought about using queue_delayed_work(), but then the change
> became much bigger and has other side effects like increasing the
> size of the ioend structure.
Yes, now that the normal work struct and the delayed work struct are
different it would be a pain, agreed.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-02-18 12:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 5:36 [PATCH] xfs: Non-blocking inode locking in IO completion Dave Chinner
2010-02-17 19:29 ` Christoph Hellwig
2010-02-17 21:13 ` Dave Chinner
2010-02-18 12:35 ` Christoph Hellwig [this message]
2010-02-25 23:06 ` [PATCH V2] " Dave Chinner
2010-02-26 17:58 ` Alex Elder
2010-02-25 20:06 ` [PATCH] " Alex Elder
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=20100218123512.GA6016@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.com \
--cc=xfs@oss.sgi.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