LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com> To: Hugh Dickins <hugh@veritas.com> Cc: Robin Holt <holt@sgi.com>, "Kawai, Hidehiro" <hidehiro.kawai.ez@hitachi.com>, Andrew Morton <akpm@osdl.org>, kernel list <linux-kernel@vger.kernel.org>, Pavel Machek <pavel@ucw.cz>, Alan Cox <alan@lxorguk.ukuu.org.uk>, Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>, sugita <yumiko.sugita.yf@hitachi.com>, Satoshi OSHIMA <soshima@redhat.com>, "Hideo AOKI@redhat" <haoki@redhat.com> Subject: Re: [PATCH 3/4] coredump: ELF-FDPIC: enable to omit anonymous shared memory Date: Tue, 06 Mar 2007 18:13:33 +0000 [thread overview] Message-ID: <3378.1173204813@redhat.com> (raw) In-Reply-To: <Pine.LNX.4.64.0703051843030.10272@blonde.wat.veritas.com> Hugh Dickins <hugh@veritas.com> wrote: > > > Under precisely what NOMMU conditions? > > > > CONFIG_MMU=n. > > Believe it or not, I had just about grasped that subtlety. I was > rather expecting some helpful response along the lines of "we share > all the vmas across a fork" or "whenever we go to allocate a vma, we > look to see if there's already an isomorphic vma which we can share" > or something like that. But don't worry about it, the source is > there for me to look at whenever. Any VMAs that can be shared are, as a general rule. It works this way because shared MAP_PRIVATE read-only file data (such as a segment of an ELF executable) is stored in a kmalloc()'d buffer attached to the VMA. The lifetime of this buffer is handled by the VMA, and the buffer is not part of the pagecache. Maybe it could be; that'd make the ramfs handling more consistent with normal file handling. Such things as mappable chardevs do get separate VMA's, but those don't own the backing store. That's configured through the BDI information in the address_space. > > I can if it makes you happier. It's not strictly necessary, but it does > > make the struct smaller which is good. > > No, it doesn't really make me any happier: I expect that if I look any > deeper, I'll just find plenty more to worry about there. Good. I was hoping someone else would review it. > I have the impression, now reinforced by your defensive posture, *shrug* I was trying to keep the VMA as little changed as possible and add as little extra to it as possible. > that NOMMU is a hack that squeamish outsiders had better not look too deeply > into: Anyone that squeamish should avoid the full MMU VM like the plague then - it's way way worse. NOMMU is considerably simpler. Yes, some liberties have to be taken, but there's no avoiding that as there's no MMU available. I've tried to take as few as possible, and I've managed to make sure almost all the functionality afforded by the MMU kernels is available. > so long as it mostly works for those who need it to work, we'd probably just > be wasting your time anyway. *shrug* as you wish. David
next prev parent reply other threads:[~2007-03-06 18:15 UTC|newest] Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-02-16 13:34 [PATCH 0/4] coredump: core dump masking support v3 Kawai, Hidehiro 2007-02-16 13:39 ` [PATCH 1/4] coredump: add an interface to control the core dump routine Kawai, Hidehiro 2007-02-16 13:40 ` [PATCH 2/4] coredump: ELF: enable to omit anonymous shared memory Kawai, Hidehiro 2007-02-16 13:41 ` [PATCH 3/4] coredump: ELF-FDPIC: " Kawai, Hidehiro 2007-02-16 13:42 ` [PATCH 4/4] coredump: documentation for proc entry Kawai, Hidehiro 2007-02-16 15:05 ` [PATCH 3/4] coredump: ELF-FDPIC: enable to omit anonymous shared memory David Howells 2007-02-16 16:50 ` Robin Holt 2007-02-16 20:09 ` David Howells 2007-03-02 16:55 ` Hugh Dickins 2007-03-03 14:10 ` David Howells 2007-03-05 19:04 ` Hugh Dickins 2007-03-06 18:13 ` David Howells [this message] 2007-03-09 14:12 ` Move to unshared VMAs in NOMMU mode? David Howells 2007-03-12 20:50 ` Robin Getz 2007-03-13 10:14 ` David Howells 2007-03-15 21:20 ` Hugh Dickins 2007-03-15 22:47 ` David Howells 2007-03-19 19:23 ` Eric W. Biederman 2007-03-20 11:06 ` David Howells 2007-03-20 16:48 ` Eric W. Biederman 2007-03-20 19:12 ` David Howells 2007-03-20 19:51 ` David Howells 2007-03-21 16:11 ` David Howells 2007-03-03 14:25 ` [PATCH] NOMMU: Hide vm_mm in NOMMU mode David Howells 2007-02-20 9:45 ` [PATCH 3/4] coredump: ELF-FDPIC: enable to omit anonymous shared memory Kawai, Hidehiro 2007-02-20 10:58 ` David Howells 2007-02-20 12:56 ` Robin Holt 2007-02-21 10:00 ` Kawai, Hidehiro 2007-02-21 11:33 ` David Howells 2007-02-21 11:54 ` Robin Holt 2007-02-22 5:33 ` Kawai, Hidehiro 2007-02-22 11:47 ` David Howells 2007-02-16 15:08 ` [PATCH 0/4] coredump: core dump masking support v3 David Howells 2007-02-20 9:48 ` Kawai, Hidehiro 2007-02-24 3:32 ` Markus Gutschke 2007-02-24 11:39 ` Pavel Machek 2007-03-01 12:35 ` Kawai, Hidehiro 2007-03-01 18:16 ` Markus Gutschke 2007-02-24 10:02 ` David Howells 2007-02-24 20:01 ` Markus Gutschke 2007-02-26 11:49 ` David Howells 2007-02-26 12:01 ` Pavel Machek 2007-02-26 12:42 ` David Howells 2007-03-02 4:41 [PATCH 0/4] coredump: core dump masking support v4 Kawai, Hidehiro 2007-03-02 4:50 ` [PATCH 3/4] coredump: ELF-FDPIC: enable to omit anonymous shared memory Kawai, Hidehiro
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=3378.1173204813@redhat.com \ --to=dhowells@redhat.com \ --cc=akpm@osdl.org \ --cc=alan@lxorguk.ukuu.org.uk \ --cc=haoki@redhat.com \ --cc=hidehiro.kawai.ez@hitachi.com \ --cc=holt@sgi.com \ --cc=hugh@veritas.com \ --cc=linux-kernel@vger.kernel.org \ --cc=masami.hiramatsu.pt@hitachi.com \ --cc=pavel@ucw.cz \ --cc=soshima@redhat.com \ --cc=yumiko.sugita.yf@hitachi.com \ /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: linkBe 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).