public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Tinguely <tinguely@sgi.com>
To: Brian Foster <bfoster@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH v4 1/6] xfs: reorganize xfs_iomap_prealloc_size to remove indentation
Date: Fri, 22 Feb 2013 12:22:52 -0600	[thread overview]
Message-ID: <5127B77C.9030709@sgi.com> (raw)
In-Reply-To: <5127B438.8080707@redhat.com>

On 02/22/13 12:08, Brian Foster wrote:
> On 02/22/2013 12:07 PM, Mark Tinguely wrote:
>> On 02/20/13 09:10, Brian Foster wrote:
>>> The majority of xfs_iomap_prealloc_size() executes within the
>>> check for lack of default I/O size. Reverse the logic to remove the
>>> extra indentation.
>>>
>>> Signed-off-by: Brian Foster<bfoster@redhat.com>
>>> Reviewed-by: Dave Chinner<dchinner@redhat.com>
>>> Reviewed-by: Ben Myers<bpm@sgi.com>
>>> ---
>>>    fs/xfs/xfs_iomap.c |   63
>>> ++++++++++++++++++++++++++-------------------------
>>>    1 files changed, 32 insertions(+), 31 deletions(-)
>>>
>>> diff --git a/fs/xfs/xfs_iomap.c b/fs/xfs/xfs_iomap.c
>>> index 912d83d..d914419 100644
>>> --- a/fs/xfs/xfs_iomap.c
>>> +++ b/fs/xfs/xfs_iomap.c
>>> @@ -381,42 +381,43 @@ xfs_iomap_prealloc_size(
>>>        int            nimaps)
>>>    {
>>>        xfs_fsblock_t        alloc_blocks = 0;
>>> +    int            shift = 0;
>>> +    int64_t            freesp;
>>
>> ...
>>
>>> +    freesp = mp->m_sb.sb_fdblocks;
>>
>> ...
>>
>>> +    /*
>>> +     * If we are still trying to allocate more space than is
>>> +     * available, squash the prealloc hard. This can happen if we
>>> +     * have a large file on a small filesystem and the above
>>> +     * lowspace thresholds are smaller than MAXEXTLEN.
>>> +     */
>>> +    while (alloc_blocks>= freesp)
>>> +        alloc_blocks>>= 4;
>>
>>
>> Hi Brian, I am looking at your speculative preallocation quota
>> throttling series.
>>
>> I know this code is from commit 4d559a3b. would this not be bad of
>> freesp == 0?
>>
>
> Thanks. Hmm, I guess if freesp is 0 we'd hit an infinite loop
> (irrespective of this patchset). We could change the comparison to>,
> but I think the following would be more clear:
>
> 	while (alloc_blocks&&  alloc_blocks>= freesp)
> 		alloc_blocks>>= 4;
>
> Thoughts? I'll send out a one-liner to bat around if that looks
> reasonable. Good catch.
>
> Brian
>
>> --Mark.


That looks reasonable to me.

Thanks,

--Mark.

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

  reply	other threads:[~2013-02-22 18:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-20 15:10 [PATCH v4 0/6] speculative preallocation quota throttling Brian Foster
2013-02-20 15:10 ` [PATCH v4 1/6] xfs: reorganize xfs_iomap_prealloc_size to remove indentation Brian Foster
2013-02-22 17:07   ` Mark Tinguely
2013-02-22 18:08     ` Brian Foster
2013-02-22 18:22       ` Mark Tinguely [this message]
2013-02-20 15:10 ` [PATCH v4 2/6] xfs: push rounddown_pow_of_two() to after prealloc throttle Brian Foster
2013-02-20 15:10 ` [PATCH v4 3/6] xfs: pass xfs_dquot to xfs_qm_adjust_dqlimits() instead of xfs_disk_dquot_t Brian Foster
2013-02-20 15:10 ` [PATCH v4 4/6] xfs: xfs_dquot prealloc throttling watermarks and low free space Brian Foster
2013-02-20 15:10 ` [PATCH v4 5/6] xfs: add quota-driven speculative preallocation throttling Brian Foster
2013-02-25 21:44   ` Mark Tinguely
2013-02-25 22:14     ` Dave Chinner
2013-02-25 22:38       ` Mark Tinguely
2013-02-20 15:10 ` [PATCH v4 6/6] xfs: xfs_iomap_prealloc_size() tracepoint Brian Foster
2013-02-22 20:09 ` [PATCH v4 0/6] speculative preallocation quota throttling Mark Tinguely
2013-02-23  1:50   ` Dave Chinner
     [not found] ` <512BC90A.4090206@sgi.com>
2013-02-25 20:47   ` Brian Foster

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=5127B77C.9030709@sgi.com \
    --to=tinguely@sgi.com \
    --cc=bfoster@redhat.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