From: Chandra Seetharaman <sekharan@us.ibm.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: YAMAMOTO Takashi <yamamoto@valinux.co.jp>,
ckrm-tech@lists.sourceforge.net, linux-mm <linux-mm@kvack.org>
Subject: Re: [ckrm-tech] [PATCH 2/6] CKRM: Core framework support
Date: Thu, 30 Jun 2005 12:02:28 -0700 [thread overview]
Message-ID: <1120158149.14910.48.camel@linuxchandra> (raw)
In-Reply-To: <1120157759.12143.64.camel@localhost>
On Thu, 2005-06-30 at 11:55 -0700, Dave Hansen wrote:
> On Thu, 2005-06-30 at 11:08 -0700, Chandra Seetharaman wrote:
> > On Wed, 2005-06-29 at 10:22 +0900, YAMAMOTO Takashi wrote:
> > > > > > + if (pud_none(*pud))
> > > > > > + return 0;
> > > > > > + BUG_ON(pud_bad(*pud));
> > > > > > + pmd = pmd_offset(pud, address);
> > > > > > + pgd_end = (address + PGDIR_SIZE) & PGDIR_MASK;
> > > > >
> > > > > why didn't you introduce class_migrate_pud?
> > > >
> > > > Because there is no list to iterate through.
> > >
> > > i don't understand what you mean.
> > > why you don't iterate pud, while you iterate pgdir and pmd?
> >
> > what i meant was that the pmd are an array and there is no array
> > w.r.t puds. correct me if i am wrong.
>
> You are wrong :)
>
> PUDs are the new level added to the pagetables for the architectures
> with larger address spaces. They are equivalent in functionality to all
> other levels, and must be treated as such in any generic code.
>
> For 2 or 3-level pagetables, they do effectively collapse down to
> nothing, but you still have to be concerned with it in generic code.
Thanks Dave/Takashi,
I will fix the code accordingly
>
> -- Dave
>
--
----------------------------------------------------------------------
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 19:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-19 0:32 Chandra Seetharaman
2005-05-20 2:27 ` [ckrm-tech] " KUROSAWA Takahiro
2005-05-20 17:06 ` 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=1120158149.14910.48.camel@linuxchandra \
--to=sekharan@us.ibm.com \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=haveblue@us.ibm.com \
--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