From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: clameter@sgi.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, akpm@linux-foundation.org,
nickpiggin@yahoo.com.au, ricknu-0@student.ltu.se,
magnus.damm@gmail.com
Subject: Re: [RFC][PATCH] page->mapping clarification [1/3] base functions
Date: Thu, 27 Sep 2007 06:50:46 +0900 [thread overview]
Message-ID: <20070927065046.508d33c0.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0709262015030.7064@blonde.wat.veritas.com>
On Wed, 26 Sep 2007 20:31:02 +0100 (BST)
Hugh Dickins <hugh@veritas.com> wrote:
> Would that waste a little memory? I think not with SLUB,
> but perhaps with SLOB, which packs a little tighter.
>
maybe just depends on the amount of used anon_vma and page_mapping_info etc...
I don't think a system which uses SLOB consumes such structs so much
as that memory-for-alignment is considered as "waste" of memory.
Anyway, I decided to go ahead with current container-info-per-page
implementation. If the size of page struct is problem at mainline inclusion
discussion, I'll be back.
Thanks,
-Kame
--
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:[~2007-09-26 21:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 7:43 KAMEZAWA Hiroyuki
2007-09-19 7:44 ` [RFC][PATCH] page->mapping clarification [2/3] changes in /mm KAMEZAWA Hiroyuki
2007-09-19 7:46 ` [RFC][PATCH] page->mapping clarification [3/3] changes in /fs generic KAMEZAWA Hiroyuki
2007-09-20 18:26 ` [RFC][PATCH] page->mapping clarification [1/3] base functions Christoph Lameter
2007-09-21 0:50 ` KAMEZAWA Hiroyuki
2007-09-21 17:02 ` Hugh Dickins
2007-09-21 18:42 ` KAMEZAWA Hiroyuki
2007-09-26 19:31 ` Hugh Dickins
2007-09-26 21:50 ` KAMEZAWA Hiroyuki [this message]
2007-09-21 11:48 ` Peter Zijlstra
2007-09-21 15:06 ` KAMEZAWA Hiroyuki
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=20070927065046.508d33c0.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=magnus.damm@gmail.com \
--cc=nickpiggin@yahoo.com.au \
--cc=ricknu-0@student.ltu.se \
/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