public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/3] xfs: changes for 3.11
Date: Mon, 27 May 2013 21:39:30 +1000	[thread overview]
Message-ID: <1369654773-26391-1-git-send-email-david@fromorbit.com> (raw)

Hi folks,

three patches for the 3.11 cycle. The first two i've posted
previously to reduce buffer cache lookups for inode creation and
inode unlink.

The third is a new patch that modifies speculative preallocation to
be nicer in small file workloads. It solves anissue where a specific
workload triggers freespace fragmentation problems due to writeback
being triggered with the speculative preallocation beyond EOF
still attached to the file and then never being used.

Cheers,

Dave.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2013-05-27 11:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-27 11:39 Dave Chinner [this message]
2013-05-27 11:39 ` [PATCH 1/3] xfs: don't use speculative prealloc for small files Dave Chinner
2013-05-27 11:39 ` [PATCH 2/3] xfs: don't do IO when creating an new inode Dave Chinner
2013-05-27 11:39 ` [PATCH 3/3] xfs: xfs_ifree doesn't need to modify the inode buffer 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=1369654773-26391-1-git-send-email-david@fromorbit.com \
    --to=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