From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: Dave Hansen <dave@sr71.net>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel ML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>
Subject: Re: [Patch:003/004] wait_table and zonelist initializing for memory hotadd (wait_table initialization)
Date: Fri, 07 Apr 2006 12:10:15 +0900 [thread overview]
Message-ID: <20060407104859.EBED.Y-GOTO@jp.fujitsu.com> (raw)
In-Reply-To: <1144361104.9731.190.camel@localhost.localdomain>
> On Wed, 2006-04-05 at 20:01 +0900, Yasunori Goto wrote:
> >
> > +#ifdef CONFIG_MEMORY_HOTPLUG
> > static inline unsigned long wait_table_size(unsigned long pages)
> > {
> > unsigned long size = 1;
> > @@ -1803,6 +1804,17 @@ static inline unsigned long wait_table_s
> >
> > return max(size, 4UL);
> > }
> > +#else
> > +/*
> > + * XXX: Because zone size might be changed by hot-add,
> > + * It is hard to determin suitable size for wait_table as
> > traditional.
> > + * So, we use maximum size now.
> > + */
> > +static inline unsigned long wait_table_size(unsigned long pages)
> > +{
> > + return 4096UL;
> > +}
> > +#endif
>
> Sorry for the slow response. My IBM email is temporarily dead.
>
> Couple of things.
>
> First, is there anything useful that prepending UL to the constants does
> to the functions? It ends up looking a little messy to me.
I would like to show that it is max size of original wait_table_size().
Original one uses 4096UL for it.
> Also, I thought you were going to put a big fat comment on there about
> doing it correctly in the future. It would also be nice to quantify the
> wasted space in terms of bytes, just so that people get a feel for it.
Hmmm. Ok.
> Oh, and wait_table_size() needs a unit. wait_table_size_bytes() sounds
> like a winner to me.
This size doesn't mean bytes. It is hash table entry size.
So, wait_table_hash_size() or wait_table_entry_size() might be better.
Thanks.
--
Yasunori Goto
WARNING: multiple messages have this Message-ID (diff)
From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: Dave Hansen <dave@sr71.net>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel ML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>
Subject: Re: [Patch:003/004] wait_table and zonelist initializing for memory hotadd (wait_table initialization)
Date: Fri, 07 Apr 2006 12:10:15 +0900 [thread overview]
Message-ID: <20060407104859.EBED.Y-GOTO@jp.fujitsu.com> (raw)
In-Reply-To: <1144361104.9731.190.camel@localhost.localdomain>
> On Wed, 2006-04-05 at 20:01 +0900, Yasunori Goto wrote:
> >
> > +#ifdef CONFIG_MEMORY_HOTPLUG
> > static inline unsigned long wait_table_size(unsigned long pages)
> > {
> > unsigned long size = 1;
> > @@ -1803,6 +1804,17 @@ static inline unsigned long wait_table_s
> >
> > return max(size, 4UL);
> > }
> > +#else
> > +/*
> > + * XXX: Because zone size might be changed by hot-add,
> > + * It is hard to determin suitable size for wait_table as
> > traditional.
> > + * So, we use maximum size now.
> > + */
> > +static inline unsigned long wait_table_size(unsigned long pages)
> > +{
> > + return 4096UL;
> > +}
> > +#endif
>
> Sorry for the slow response. My IBM email is temporarily dead.
>
> Couple of things.
>
> First, is there anything useful that prepending UL to the constants does
> to the functions? It ends up looking a little messy to me.
I would like to show that it is max size of original wait_table_size().
Original one uses 4096UL for it.
> Also, I thought you were going to put a big fat comment on there about
> doing it correctly in the future. It would also be nice to quantify the
> wasted space in terms of bytes, just so that people get a feel for it.
Hmmm. Ok.
> Oh, and wait_table_size() needs a unit. wait_table_size_bytes() sounds
> like a winner to me.
This size doesn't mean bytes. It is hash table entry size.
So, wait_table_hash_size() or wait_table_entry_size() might be better.
Thanks.
--
Yasunori Goto
--
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:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-04-07 3:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-05 10:57 [Patch:000/004] wait_table and zonelist initializing for memory hotadd Yasunori Goto
2006-04-05 10:57 ` Yasunori Goto
2006-04-05 11:01 ` [Patch:001/004] wait_table and zonelist initializing for memory hotadd (change to meminit for build_zonelist) Yasunori Goto
2006-04-05 11:01 ` Yasunori Goto
2006-04-05 11:01 ` [Patch:002/004] wait_table and zonelist initializing for memory hotadd (add return code for init_current_empty_zone) Yasunori Goto
2006-04-05 11:01 ` Yasunori Goto
2006-04-05 11:01 ` [Patch:003/004] wait_table and zonelist initializing for memory hotadd (wait_table initialization) Yasunori Goto
2006-04-05 11:01 ` Yasunori Goto
2006-04-06 22:05 ` Dave Hansen
2006-04-06 22:05 ` Dave Hansen
2006-04-07 3:10 ` Yasunori Goto [this message]
2006-04-07 3:10 ` Yasunori Goto
2006-04-07 3:12 ` Dave Hansen
2006-04-07 3:12 ` Dave Hansen
2006-04-05 11:01 ` [Patch:004/004] wait_table and zonelist initializing for memory hotadd (update zonelists) Yasunori Goto
2006-04-05 11:01 ` Yasunori Goto
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=20060407104859.EBED.Y-GOTO@jp.fujitsu.com \
--to=y-goto@jp.fujitsu.com \
--cc=akpm@osdl.org \
--cc=dave@sr71.net \
--cc=linux-kernel@vger.kernel.org \
--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 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.