From: Nick Piggin <npiggin@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Nick Piggin <npiggin@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [patch] i386: pageattr remove __put_page
Date: Thu, 19 Jan 2006 15:13:00 +0100 [thread overview]
Message-ID: <20060119141300.GE958@wotan.suse.de> (raw)
In-Reply-To: <20060118190028.7047ade2.akpm@osdl.org>
On Wed, Jan 18, 2006 at 07:00:28PM -0800, Andrew Morton wrote:
> Nick Piggin <npiggin@suse.de> wrote:
> >
> > Stop using __put_page and page_count in i386 pageattr.c
> >
>
> who, where, what, why, when?? The patch appears to ascribe some special
> significance to page->private, but you don't tell us what it is. And if
> that's not obvious from reading the patch, it won't be obvious to people
> who are later reading the code.
>
> iow: you owe us a nice comment, please.
>
OK sure, I'll redo it.
> >
> > Index: linux-2.6/arch/i386/mm/pageattr.c
> > ===================================================================
> > --- linux-2.6.orig/arch/i386/mm/pageattr.c
> > +++ linux-2.6/arch/i386/mm/pageattr.c
> > @@ -51,6 +51,9 @@ static struct page *split_large_page(uns
> > if (!base)
> > return NULL;
> >
> > + SetPagePrivate(base);
> > + page_private(base) = 0;
>
> A "function call" as an lval give me hiccups. Use set_page_private(p, v),
> please.
>
Hmm yes of course. That makes it pretty ugly.
> > address = __pa(address);
> > addr = address & LARGE_PAGE_MASK;
> > pbase = (pte_t *)page_address(base);
> > @@ -143,11 +146,12 @@ __change_page_attr(struct page *page, pg
> > return -ENOMEM;
> > set_pmd_pte(kpte,address,mk_pte(split, ref_prot));
> > kpte_page = split;
> > - }
> > - get_page(kpte_page);
> > + }
> > + page_private(kpte_page)++;
>
> Ditto, really. If we're going to be nice about this it should be
>
> set_page_private(page, page_private(page) + 1);
>
> > + page_private(kpte_page)--;
>
> Ditto.
>
>
> Or we just forget about page_private() and go back to using page->private -
> page_private() was rather a stopgap thing.
>
Could we? We can do anonymous unions now, right?
next prev parent reply other threads:[~2006-01-19 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 15:04 Nick Piggin
2006-01-19 3:00 ` Andrew Morton
2006-01-19 14:13 ` Nick Piggin [this message]
2006-01-19 21:56 ` Andrew Morton
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=20060119141300.GE958@wotan.suse.de \
--to=npiggin@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®