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/2] xfs: couple of patches for 3.9
Date: Mon, 11 Feb 2013 16:05:00 +1100	[thread overview]
Message-ID: <1360559102-20432-1-git-send-email-david@fromorbit.com> (raw)

Hi folks,

These are a couple of patches I have in my queue that are should be
OK for the 3.9 cycle. The first is a fixed version of the
specualtive preallocation sparse file handling improvement - it now
does what it claims to do. :)

The second is a re-organisation of xfs_bmap.c, I got sick of having
to jump all over the file when trying to work on a small part of the
code, so I rearranged the code into a more sane layout. It's a big
patch, but it doesn't change any code except to remove the forward
declarations of various functions. It's not a big deal if nobody
wants this, but I find the re-organised layout much easier to deal
with, and potentially points at ways that big file can be split up
if we want to...

Cheers,

Dave.

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

             reply	other threads:[~2013-02-11  5:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-11  5:05 Dave Chinner [this message]
2013-02-11  5:05 ` [PATCH 1/2] xfs: limit speculative prealloc size on sparse files Dave Chinner
2013-02-11 22:00   ` Mark Tinguely
2013-02-12 13:35   ` Brian Foster
2013-02-14 23:31   ` Ben Myers
2013-02-11  5:05 ` [PATCH 2/2] xfs: rearrange some code in xfs_bmap for better locality Dave Chinner
2013-02-11 22:43   ` Mark Tinguely
2013-02-12  1:36     ` 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=1360559102-20432-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