From: Jeff Liu <jeff.liu@oracle.com>
To: Dave Chinner <david@fromorbit.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfsprogs: code sync up for log space reservation
Date: Fri, 17 May 2013 20:04:05 +0800 [thread overview]
Message-ID: <51961CB5.4060101@oracle.com> (raw)
In-Reply-To: <20130517105253.GU24635@dastard>
Hi Dave,
On 05/17/2013 06:52 PM, Dave Chinner wrote:
> On Fri, May 17, 2013 at 05:21:03PM +0800, Jeff Liu wrote:
>> Hello,
>>
>> Here is a patch to sync up the kernel code changes regarding log space reservation
>> to the xfsprogs.
>>
>> There have a couple of differences between the kernel and the user space.
>> 1) A few transaction reservation item related to dquot are not synced because they
>> are not being used in xfsprogs.
>> 2) In xfs_log_rlimit.c, the xfs_log_validate_logspace() is not copied and the xfs_mkfs.c
>> still use the default validate_log_space() to check the given log size.
>
> Hi Jeff,
>
> Just as a heads up, this is going to have conflicts with the CRC
> patchset that I'm planning on posting in a few minutes. How do you
> want to resolve them?
>
> From my perspective it's easier if we rebase your patch on top of my
> patchset. If we go the other way around, I'll have to rebase 10-20
> patches that your patch has conflicts with....
Sure. It's ok to me since I only need to rebase one big patch. :)
Thanks,
-Jeff
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-05-17 12:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 9:21 [PATCH] xfsprogs: code sync up for log space reservation Jeff Liu
2013-05-17 10:52 ` Dave Chinner
2013-05-17 12:04 ` Jeff Liu [this message]
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=51961CB5.4060101@oracle.com \
--to=jeff.liu@oracle.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox