From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Memory Management <linux-mm@kvack.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH 2/3] higher order watermarks
Date: Fri, 05 Nov 2004 12:06:21 +1100 [thread overview]
Message-ID: <418AD20D.4000201@yahoo.com.au> (raw)
In-Reply-To: <20041104095545.GA7902@logos.cnet>
Marcelo Tosatti wrote:
> Hi Nick!
>
> On Thu, Nov 04, 2004 at 11:20:54PM +1100, Nick Piggin wrote:
>
>>So now what we need to do in order to calculate, say the amount of memory
>>that will satisfy order-2 *and above* (this is important) is the following:
>>
>> z->free_pages - (order[0].nr_free << 0) - (order[1].nr_free << 1)
>
>
> Shouldnt that be then
>
> free_pages -= z->free_area[o].nr_free << o;
>
> instead of the current
>
> free_pages -= z->free_area[order].nr_free << o;
>
> No?
>
Yes, you're absolutely right. Sorry, this is what you were getting
at all along :P
>
>>to find order-3 and above, you also need to subtract (order[2].nr_free <<
>>2).
>>
>>I quite liked this method because it has progressively less cost on lower
>>order allocations, and for order-0 we don't need to do any calculation.
>
>
> OK, now I get it. The only think which bugs me is the multiplication of
> values with different meanings.
>
Yeah it's wrong, of course. Good catch, thanks.
If you would care to send a patch Marcelo? I don't have a recent
-mm on hand at the moment. Would that be alright?
Thanks,
Nick
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-11-05 1:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 8:00 [PATCH 0/3] teach kswapd about higher order allocations Nick Piggin
2004-10-27 8:00 ` [PATCH 1/3] keep count of free areas Nick Piggin
2004-10-27 8:02 ` [PATCH 2/3] higher order watermarks Nick Piggin
2004-10-27 8:02 ` [PATCH 3/3] teach kswapd about higher order areas Nick Piggin
2004-10-27 8:13 ` Nick Piggin
2004-11-04 8:57 ` [PATCH 2/3] higher order watermarks Marcelo Tosatti
2004-11-04 12:20 ` Nick Piggin
2004-11-04 9:55 ` Marcelo Tosatti
2004-11-05 1:06 ` Nick Piggin [this message]
2004-11-04 22:47 ` Marcelo Tosatti
2004-11-05 2:08 ` Andrew Morton
2004-11-05 2:14 ` Nick Piggin
2004-11-04 10:02 ` Marcelo Tosatti
2004-11-05 1:12 ` Nick Piggin
2004-11-10 16:23 ` Marcelo Tosatti
2004-11-11 1:41 ` Nick Piggin
2004-11-11 10:18 ` Marcelo Tosatti
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=418AD20D.4000201@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=linux-mm@kvack.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=torvalds@osdl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.