From: Tao Ma <tao.ma@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 0/2] ocfs2: make xattr work with new local alloc reservation.
Date: Fri, 18 Jun 2010 11:00:17 +0800 [thread overview]
Message-ID: <4C1AE141.60707@oracle.com> (raw)
Hi all,
The old xattr codes deem that we can allocate enough contiguous
clusters from the allocator, it works with the old local alloc
allocator. But as Mark has added reservation code to ocfs2, now it isn't
the good hypothesis any more. So these 2 patches try to let xattr work
with it.
Regards,
Tao
next reply other threads:[~2010-06-18 3:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 3:00 Tao Ma [this message]
2010-06-18 3:02 ` [Ocfs2-devel] [PATCH] ocfs2: make xattr extension work with new local alloc reservation Tao Ma
2010-07-08 18:36 ` Joel Becker
2010-07-08 18:51 ` Joel Becker
2010-07-09 3:38 ` Tao Ma
2010-07-09 8:01 ` Joel Becker
2010-06-18 3:02 ` [Ocfs2-devel] [PATCH] ocfs2: Make xattr reflink " Tao Ma
2010-06-18 3:29 ` [Ocfs2-devel] [PATCH v2] " Tao Ma
2010-07-08 19:42 ` [Ocfs2-devel] [PATCH] " Joel Becker
2010-07-09 4:03 ` Tao Ma
2010-07-08 18:27 ` [Ocfs2-devel] [PATCH 0/2] ocfs2: make xattr " Joel Becker
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=4C1AE141.60707@oracle.com \
--to=tao.ma@oracle.com \
--cc=ocfs2-devel@oss.oracle.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;
as well as URLs for NNTP newsgroup(s).