From: Tao Ma <tao.ma@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH v2] ocfs2: make ocfs2_adjust_resv_from_alloc simple.
Date: Mon, 26 Apr 2010 14:45:36 +0800 [thread overview]
Message-ID: <4BD53690.9030508@oracle.com> (raw)
In-Reply-To: <20100423220342.GC8330@mail.oracle.com>
Joel Becker wrote:
> On Thu, Apr 08, 2010 at 04:33:02PM +0800, Tao Ma wrote:
>> When we allocate some bits from the reservation, we always
>> allocate from the r_start(see ocfs2_resmap_resv_bits).
>> So there should be no sense for checking between r_start
>> and start. And I don't think we will change this behaviour
>> somehow later by allocating from some bits after r_start.
>> Why not make ocfs2_adjust_resv_from_alloc simple now?
>>
>> So the only chance we have to adjust the reservation is that
>> we haven't reached the end. With this patch, the function is
>> more readable.
>>
>> Note:
>> btw, this patch also fixes an original bug in the function
>> which I haven't found before.
>> if (end < ocfs2_resv_end(resv))
>> rhs = end - ocfs2_resv_end(resv);
>> This code is of course buggy. ;)
>>
>> Cc: Mark Fasheh <mfasheh@suse.com>
>> Signed-off-by: Tao Ma <tao.ma@oracle.com>
>
> This patch is now in the 'merge-window' branch of ocfs2.git.
thanks, joel.
btw, you still miss another patch which Mark has acked for the merge-window.
http://oss.oracle.com/pipermail/ocfs2-devel/2010-April/006250.html
Regards,
Tao
prev parent reply other threads:[~2010-04-26 6:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 7:40 [Ocfs2-devel] [PATCH] ocfs2: make ocfs2_adjust_resv_from_alloc simple Tao Ma
2010-04-07 21:24 ` Mark Fasheh
2010-04-07 23:47 ` Tao Ma
2010-04-08 8:33 ` [Ocfs2-devel] [PATCH v2] " Tao Ma
2010-04-23 21:44 ` Mark Fasheh
2010-04-23 22:03 ` Joel Becker
2010-04-26 6:45 ` Tao Ma [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=4BD53690.9030508@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).