From: "Daniel Lowengrub" <lowdanie@gmail.com>
To: linux-mm@kvack.org
Subject: Re: [PATCH 2.6.28 1/2] memory: improve find_vma
Date: Tue, 20 Jan 2009 18:26:52 +0200 [thread overview]
Message-ID: <8c5a844a0901200826n714e1891n23dd48208a6a6746@mail.gmail.com> (raw)
In-Reply-To: <20090120072659.B0A6.KOSAKI.MOTOHIRO@jp.fujitsu.com>
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
> Hi
>
>> - /* linked list of VM areas per task, sorted by address */
>> + /* doubly linked list of VM areas per task, sorted by address */
>> struct vm_area_struct *vm_next;
>> + struct vm_area_struct *vm_prev;
>
> if you need "doublly linked list", why don't you use list.h?
list.h implements a circular linked list which is harder to integrate
into the existing code which in many places uses the fact that the
last element in the list points to null. First I want to check if it's
a good idea in general, if it is then I'll try to use the list.h
implementation.
Do you think that the idea is worth building on? Is there any special
reason that I'm not aware of that this wasn't done originally?
Thanks
--
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-01-20 16:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-17 17:12 [PATCH 2.6.28 1/2] memory: improve find_vma Daniel Lowengrub
2009-01-18 22:36 ` KOSAKI Motohiro
2009-01-20 16:26 ` Daniel Lowengrub [this message]
[not found] <8c5a844a0901220851g1c21169al4452825564487b9a@mail.gmail.com>
2009-01-22 17:22 ` Hugh Dickins
2009-01-22 23:00 ` Daniel Lowengrub
2009-01-22 23:13 ` Ingo Molnar
2009-01-23 11:10 ` Daniel Lowengrub
2009-01-28 21:31 ` Daniel Lowengrub
2009-01-29 14:19 ` Ingo Molnar
2009-02-01 11:19 ` Daniel Lowengrub
2009-02-01 13:00 ` Ingo Molnar
2009-02-05 11:26 ` Daniel Lowengrub
2009-02-05 19:41 ` Ingo Molnar
2009-02-05 19:51 ` Peter Zijlstra
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=8c5a844a0901200826n714e1891n23dd48208a6a6746@mail.gmail.com \
--to=lowdanie@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).