From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, xfs@oss.sgi.com
Subject: Re: [RFC PATCH 0/6] xfs: truncate vs page fault IO exclusion
Date: Thu, 8 Jan 2015 04:24:48 -0800 [thread overview]
Message-ID: <20150108122448.GA18034@infradead.org> (raw)
In-Reply-To: <1420669543-8093-1-git-send-email-david@fromorbit.com>
> This patchset passes xfstests and various benchmarks and stress
> workloads, so the real question is now:
>
> What have I missed?
>
> Comments, thoughts, flames?
Why is this done in XFS and not in generic code?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC PATCH 0/6] xfs: truncate vs page fault IO exclusion
Date: Thu, 8 Jan 2015 04:24:48 -0800 [thread overview]
Message-ID: <20150108122448.GA18034@infradead.org> (raw)
In-Reply-To: <1420669543-8093-1-git-send-email-david@fromorbit.com>
> This patchset passes xfstests and various benchmarks and stress
> workloads, so the real question is now:
>
> What have I missed?
>
> Comments, thoughts, flames?
Why is this done in XFS and not in generic code?
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC PATCH 0/6] xfs: truncate vs page fault IO exclusion
Date: Thu, 8 Jan 2015 04:24:48 -0800 [thread overview]
Message-ID: <20150108122448.GA18034@infradead.org> (raw)
In-Reply-To: <1420669543-8093-1-git-send-email-david@fromorbit.com>
> This patchset passes xfstests and various benchmarks and stress
> workloads, so the real question is now:
>
> What have I missed?
>
> Comments, thoughts, flames?
Why is this done in XFS and not in generic code?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-01-08 12:24 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 22:25 [RFC PATCH 0/6] xfs: truncate vs page fault IO exclusion Dave Chinner
2015-01-07 22:25 ` Dave Chinner
2015-01-07 22:25 ` Dave Chinner
2015-01-07 22:25 ` [RFC PATCH 1/6] xfs: introduce mmap/truncate lock Dave Chinner
2015-01-07 22:25 ` Dave Chinner
2015-01-07 22:25 ` Dave Chinner
2015-01-22 13:09 ` Brian Foster
2015-01-22 13:09 ` Brian Foster
2015-01-22 21:30 ` Dave Chinner
2015-01-22 21:30 ` Dave Chinner
2015-01-07 22:25 ` [RFC PATCH 2/6] xfs: use i_mmaplock on read faults Dave Chinner
2015-01-07 22:25 ` Dave Chinner
2015-01-07 22:25 ` [RFC PATCH 3/6] xfs: use i_mmaplock on write faults Dave Chinner
2015-01-07 22:25 ` Dave Chinner
2015-01-07 22:25 ` Dave Chinner
2015-01-07 22:25 ` [RFC PATCH 4/6] xfs: take i_mmap_lock on extent manipulation operations Dave Chinner
2015-01-07 22:25 ` Dave Chinner
2015-01-22 13:23 ` Brian Foster
2015-01-22 13:23 ` Brian Foster
2015-01-22 13:23 ` Brian Foster
2015-01-22 21:32 ` Dave Chinner
2015-01-22 21:32 ` Dave Chinner
2015-01-22 21:32 ` Dave Chinner
2015-01-07 22:25 ` [RFC PATCH 5/6] xfs: xfs_setattr_size no longer races with page faults Dave Chinner
2015-01-07 22:25 ` Dave Chinner
2015-01-07 22:25 ` Dave Chinner
2015-01-07 22:25 ` [RFC PATCH 6/6] xfs: lock out page faults from extent swap operations Dave Chinner
2015-01-07 22:25 ` Dave Chinner
2015-01-22 13:41 ` Brian Foster
2015-01-22 13:41 ` Brian Foster
2015-01-08 11:34 ` [RFC PATCH 0/6] xfs: truncate vs page fault IO exclusion Jan Kara
2015-01-08 11:34 ` Jan Kara
2015-01-08 11:34 ` Jan Kara
2015-01-08 12:24 ` Christoph Hellwig [this message]
2015-01-08 12:24 ` Christoph Hellwig
2015-01-08 12:24 ` Christoph Hellwig
2015-01-08 21:45 ` Dave Chinner
2015-01-08 21:45 ` Dave Chinner
2015-01-12 17:42 ` Jan Kara
2015-01-12 17:42 ` Jan Kara
2015-01-21 22:26 ` Dave Chinner
2015-01-21 22:26 ` Dave Chinner
2015-01-21 22:26 ` Dave Chinner
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=20150108122448.GA18034@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.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.