From: Chandra Seetharaman <sekharan@us.ibm.com>
To: KUROSAWA Takahiro <kurosawa@valinux.co.jp>
Cc: ckrm-tech@lists.sourceforge.net, linux-mm@kvack.org
Subject: Re: [ckrm-tech] [PATCH 2/6] CKRM: Core framework support
Date: Fri, 20 May 2005 10:06:47 -0700 [thread overview]
Message-ID: <20050520170647.GC28304@chandralinux.beaverton.ibm.com> (raw)
In-Reply-To: <20050520022732.A6646717AE@sv1.valinux.co.jp>
On Fri, May 20, 2005 at 11:27:31AM +0900, KUROSAWA Takahiro wrote:
> Hi,
>
> On Wed, 18 May 2005 17:32:05 -0700
> Chandra Seetharaman <sekharan@us.ibm.com> wrote:
>
> > Index: linux-2612-rc3/mm/page_alloc.c
> > ===================================================================
> > --- linux-2612-rc3.orig/mm/page_alloc.c
> > +++ linux-2612-rc3/mm/page_alloc.c
> > @@ -752,7 +752,7 @@ __alloc_pages(unsigned int __nocast gfp_
> > */
> > can_try_harder = (unlikely(rt_task(p)) && !in_interrupt()) || !wait;
> >
> > - if (!ckrm_class_limit_ok(ckrm_get_mem_class(p)))
> > + if (!ckrm_class_limit_ok(ckrm_task_memclass(p)))
> > return NULL;
> >
> > zones = zonelist->zones; /* the list of zones suitable for gfp_mask */
>
> __alloc_pages() seems to look at the limit of the interrupted task
> when an interrupt handler calls __alloc_pages(). It might be better
> not to use ckrm_class_limit_ok() in in_interrupt() case, as we can't
> assume that the interrupt is caused by the interrupted task.
Sounds valid... I had it before that way, for for some other reasoning of
mine. will get it back.
>
> In can_try_harder case, how about trying to reclaim pages that belong
> to the class if !ckrm_class_limit_ok() ?
Sounds a good idea. will do it.
Thanks for your comments.
>
> Regards,
>
> --
> KUROSAWA, Takahiro
--
----------------------------------------------------------------------
Chandra Seetharaman | Be careful what you choose....
- sekharan@us.ibm.com | .......you may get it.
----------------------------------------------------------------------
--
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:[~2005-05-20 17:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 0:32 Chandra Seetharaman
2005-05-20 2:27 ` [ckrm-tech] " KUROSAWA Takahiro
2005-05-20 17:06 ` Chandra Seetharaman [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-24 22:22 Chandra Seetharaman
2005-06-25 7:49 ` [ckrm-tech] " YAMAMOTO Takashi
2005-06-27 20:50 ` Chandra Seetharaman
2005-06-29 1:22 ` YAMAMOTO Takashi
2005-06-30 18:08 ` Chandra Seetharaman
2005-06-30 18:55 ` Dave Hansen
2005-06-30 19:02 ` Chandra Seetharaman
2005-04-02 3:12 Chandra Seetharaman
2005-04-08 0:39 ` [ckrm-tech] " Dave Hansen
2005-04-08 1:34 ` Chandra Seetharaman
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=20050520170647.GC28304@chandralinux.beaverton.ibm.com \
--to=sekharan@us.ibm.com \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=kurosawa@valinux.co.jp \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox