From: Simon Kirby <sim@hostway.ca>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: XFS read hangs in 3.1-rc10
Date: Wed, 16 Nov 2011 11:56:43 -0800 [thread overview]
Message-ID: <20111116195643.GF24411@hostway.ca> (raw)
In-Reply-To: <20111104210324.GB14983@infradead.org>
On Fri, Nov 04, 2011 at 05:03:24PM -0400, Christoph Hellwig wrote:
> Sorry Simon,
>
> I haven't really been able to get back to this as fast as I wanted to
> do. Can you do another run and check if the patch still helps your
> issue even if you remove the xfs_log_force line?
Hello!
Sorry for the delay in testing.
Yes, everything looks fine even with the xfs_log_force line from your
patch commented out. So, the changes in xfs_reclaim_inode() are just the
set_bit(XBT_FORCE_FLUSH) and wake_up_process(), relative to 3.1.
Simon-
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Simon Kirby <sim@hostway.ca>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: XFS read hangs in 3.1-rc10
Date: Wed, 16 Nov 2011 11:56:43 -0800 [thread overview]
Message-ID: <20111116195643.GF24411@hostway.ca> (raw)
In-Reply-To: <20111104210324.GB14983@infradead.org>
On Fri, Nov 04, 2011 at 05:03:24PM -0400, Christoph Hellwig wrote:
> Sorry Simon,
>
> I haven't really been able to get back to this as fast as I wanted to
> do. Can you do another run and check if the patch still helps your
> issue even if you remove the xfs_log_force line?
Hello!
Sorry for the delay in testing.
Yes, everything looks fine even with the xfs_log_force line from your
patch commented out. So, the changes in xfs_reclaim_inode() are just the
set_bit(XBT_FORCE_FLUSH) and wake_up_process(), relative to 3.1.
Simon-
next prev parent reply other threads:[~2011-11-16 19:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 22:42 XFS read hangs in 3.1-rc10 Simon Kirby
2011-10-20 22:42 ` Simon Kirby
2011-10-21 13:22 ` Christoph Hellwig
2011-10-21 13:22 ` Christoph Hellwig
2011-10-21 20:28 ` Simon Kirby
2011-10-21 20:28 ` Simon Kirby
2011-10-24 8:22 ` Christoph Hellwig
2011-10-24 8:22 ` Christoph Hellwig
2011-10-25 20:07 ` Simon Kirby
2011-10-25 20:07 ` Simon Kirby
2011-10-26 11:25 ` Christoph Hellwig
2011-10-26 11:25 ` Christoph Hellwig
2011-11-04 21:03 ` Christoph Hellwig
2011-11-04 21:03 ` Christoph Hellwig
2011-11-16 19:56 ` Simon Kirby [this message]
2011-11-16 19:56 ` Simon Kirby
2011-11-20 15:32 ` Christoph Hellwig
2011-11-20 15:32 ` Christoph Hellwig
2011-11-28 19:05 ` Simon Kirby
2011-11-28 19:05 ` Simon Kirby
2011-11-28 19:55 ` Christoph Hellwig
2011-11-28 19:55 ` Christoph Hellwig
2011-11-28 21:01 ` Ben Myers
2011-11-28 21:01 ` Ben Myers
2011-10-21 20:29 ` Markus Trippelsdorf
2011-10-21 20:29 ` Markus Trippelsdorf
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=20111116195643.GF24411@hostway.ca \
--to=sim@hostway.ca \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.