From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH, needs a new owner] XFS misc patches
Date: Thu, 19 Feb 2009 14:34:03 -0500 [thread overview]
Message-ID: <20090219193403.GA22736@infradead.org> (raw)
In-Reply-To: <49939FDA.6090401@sgi.com>
On Thu, Feb 12, 2009 at 03:04:42PM +1100, Mark Goodwin wrote:
>
> Series of 12 patches, originally by Dave Chinner. These will need
> forward porting to top-of-tree and careful review. See the description
> in each individual patch for details of each patch.
>
> 01/12 readpage-unwritten-mapping
Is there any other reason for this except for the slight cleanup?
Looks goodish to me and I'll throw it into my QA queue.
> 02/12 xfs-fix-log-io-latency
> 03/12 xfs-use-meta-io-for-async-metadata
Whered did we get stuck on these? IIRC there was some sort of
regression on either the AS or deadlinke scheduler, right?
> 04/12 xfs-inval-page-fixup
Looks good to me, but not really useful until we actually have back
tracing in some useable tree..
> 05/12 xfs-iolock-on-page-mkwrite
Do we have a testcase for those races?
> 06/12 xfs-non-block-writes-when-frozen
We don't actually ever set O_NDELAY for regular files, so this can't
actually be triggered.
> 07/12 xfs-non-block-setattr-size-when-frozen
I wonder if we should do these kinds of things higher up, e.g. in the
vfsmount writer count API in the VFS.
> 08/12 xfs-inode-search
Interesting idea, but really wants some refactoring of the surrounding
code first..
> 09/12 xfs-v2-inodes-default
Do we really care? There shouldn't be any Linux filesystems with v1
inodes in the wild.
> 10/12 xfs-inode-writeback-checking
b_io_callback is now in the CRC patch series, and we could add
additional checking there. Must say I don't really like the string
buffer on stack in that path.
> 11/12 xfs-inode-swap
Yeah, we need to revisit this eventually. Big qustions is what we want
to do with symlinks in an xfs_reno or shrinkfs using this ioctl.
> 12/12 xfs-increase-iclogs
Interesting idea. But 2MB is much larger than the current log buffer
window..
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-02-19 19:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 4:04 [PATCH, needs a new owner] XFS misc patches Mark Goodwin
2009-02-12 17:49 ` Eric Sandeen
2009-02-19 19:34 ` Christoph Hellwig [this message]
2009-02-20 0:17 ` 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=20090219193403.GA22736@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 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.