From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/2] xfs: patches for 3.2
Date: Fri, 30 Sep 2011 14:45:01 +1000 [thread overview]
Message-ID: <1317357903-26947-1-git-send-email-david@fromorbit.com> (raw)
These are the two patches I have outstanding for 3.2. I've dropped
the xfsbufd changes from the series as Christoph and I have been
discussing ways to change metadata writeback that make the xfsbufd
redundant. Hence there's no need to change it now...
I've dropped all the interface changes from the xfs buf allocation
code change, simplifying it lots, and fixed the problems reported
with it. I've also fixed a bug in the AIL log force reduction patch
that caused the AIL to get stuck when pinned buffers caused the
stuck processing to loop.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2011-09-30 4:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 4:45 Dave Chinner [this message]
2011-09-30 4:45 ` [PATCH 1/2] xfs: Don't allocate new buffers on every call to _xfs_buf_find Dave Chinner
2011-09-30 15:27 ` Christoph Hellwig
2011-10-04 21:30 ` Alex Elder
2011-09-30 4:45 ` [PATCH 2/2] xfs: reduce the number of log forces from tail pushing 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=1317357903-26947-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