From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: kosaki.motohiro@jp.fujitsu.com,
Daniel Lowengrub <lowdanie@gmail.com>,
linux-mm@kvack.org, Ingo Molnar <mingo@elte.hu>,
a.p.zijlstra@chello.nl, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] mm: use list.h for vma list
Date: Thu, 12 Mar 2009 17:32:49 +0900 (JST) [thread overview]
Message-ID: <20090312172619.43BA.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <200903112254.56764.nickpiggin@yahoo.com.au>
> On Wednesday 11 March 2009 20:55:48 Daniel Lowengrub wrote:
> > Use the linked list defined list.h for the list of vmas that's stored
> > in the mm_struct structure. Wrapper functions "vma_next" and
> > "vma_prev" are also implemented. Functions that operate on more than
> > one vma are now given a list of vmas as input.
>
> I'd love to be able to justify having a doubly linked list for vmas...
> It's easier than managing singly linked lists by hand :) So if you have
> such a good increase with lookups, it might be a good idea. I wouldn't
> like to see vm_area_struct go above 192 bytes on any config if possible
> though.
Currently, sizeof(struct vm_area_struct) on x86_64 is 176.
if we assume 32byte cache-line, 176byte is 6 cache-line.
then, making coubly linked list don't cause d-cache pollution.
Therefore, We can merge this patch after some cleanups.
(of cource, your opining cleanups is obiously necessary...)
--
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:[~2009-03-12 8:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 9:55 Daniel Lowengrub
2009-03-11 10:40 ` Alexey Dobriyan
2009-03-11 10:52 ` Ingo Molnar
2009-03-11 11:54 ` Nick Piggin
2009-03-11 13:25 ` Daniel Lowengrub
2009-03-12 3:00 ` Nick Piggin
2009-03-12 8:32 ` KOSAKI Motohiro [this message]
2009-03-12 9:58 ` Peter Zijlstra
2009-04-02 9:56 ` Daniel Lowengrub
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=20090312172619.43BA.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lowdanie@gmail.com \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
/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