From: "Luciano A. Stertz" <luciano@tteng.com.br>
To: linux-mm@kvack.org
Subject: [Fwd: vma list in struct address_space]
Date: Wed, 21 Jul 2004 13:44:22 -0300 [thread overview]
Message-ID: <40FE9D66.3070709@tteng.com.br> (raw)
Hi,
I sent this message to kernelnewbies but receive no replay. May you
please help me?
Thanks,
Luciano
====================================================
I have a doubt about the address_space struct.
I understand that struct address_space contains lists of the virtual
memory area instances that refers to the inode controlled by this
address_space.
Up to kernel 2.6.6, it was clear to me from the struct declaration that
there were two lists, i_mmap was the list of private (created with
MAP_PRIVATE) mappings and i_mmap_shared the list of shared (created with
MAP_SHARED).
On kernel 2.6.7, however, I couldn't undestand the lists:
struct prio_tree_root i_mmap; /* tree of private
mappings */
struct list_head i_mmap_nonlinear;/*list VM_NONLINEAR
mappings */
i_mmap seems to be still listing private mappings, but i_mmap_shared
was removed and i_mmap_nonlinear added.
If I create a shared linear mapping, will it be kept in any of these lists?
Or maybe the i_mmap comment is misleading, and now i_mmap maps linear vmas?
TIA,
Luciano Stertz
--
Luciano A. Stertz
luciano@tteng.com.br
T&T Engenheiros Associados Ltda
http://www.tteng.com.br
Fone/Fax (51) 3224 8425
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/kernelnewbies/
FAQ: http://kernelnewbies.org/faq/
--
Luciano A. Stertz
luciano@tteng.com.br
T&T Engenheiros Associados Ltda
http://www.tteng.com.br
Fone/Fax (51) 3224 8425
--
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:"aart@kvack.org"> aart@kvack.org </a>
reply other threads:[~2004-07-21 16:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=40FE9D66.3070709@tteng.com.br \
--to=luciano@tteng.com.br \
--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.