From: Chandra Seetharaman <sekharan@us.ibm.com>
To: YAMAMOTO Takashi <yamamoto@valinux.co.jp>
Cc: ckrm-tech@lists.sourceforge.net, linux-mm@kvack.org
Subject: Re: [ckrm-tech] [PATCH 4/6] CKRM: Add guarantee support for mem controller
Date: Thu, 30 Jun 2005 11:11:44 -0700 [thread overview]
Message-ID: <1120155104.14910.36.camel@linuxchandra> (raw)
In-Reply-To: <1120110730.479552.4689.nullmailer@yamt.dyndns.org>
On Thu, 2005-06-30 at 14:52 +0900, YAMAMOTO Takashi wrote:
> > +static inline void
> > +ckrm_clear_page_class(struct page *page)
> > +{
> > + struct ckrm_zone *czone = page_ckrmzone(page);
> > + if (czone == NULL)
> > + return;
> > + sub_use_count(czone->memcls, 0, page_zonenum(page), 1);
> > + kref_put(&czone->memcls->nr_users, memclass_release);
> > + set_page_ckrmzone(page, NULL);
> > }
>
> are you sure if it's safe?
> this function is called with zone->lock held,
> and memclass_release calls kfree.
i don't understand why you think it is a problem to call kfree with lock
held( i agree calling kmalloc with wait flag when a lock is being held
is not correct).
>
> YAMAMOTO Takashi
--
----------------------------------------------------------------------
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-06-30 18:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 22:25 Chandra Seetharaman
2005-06-30 5:52 ` [ckrm-tech] " YAMAMOTO Takashi
2005-06-30 18:11 ` Chandra Seetharaman [this message]
2005-06-30 18:23 ` Dave Hansen
2005-06-30 18:53 ` Chandra Seetharaman
2005-06-30 19:02 ` Dave Hansen
2005-06-30 19:21 ` Chandra Seetharaman
2005-06-30 19:29 ` Dave Hansen
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=1120155104.14910.36.camel@linuxchandra \
--to=sekharan@us.ibm.com \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=linux-mm@kvack.org \
--cc=yamamoto@valinux.co.jp \
/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