From: Dave Hansen <haveblue@us.ibm.com>
To: David Howells <dhowells@redhat.com>
Cc: linux-arch@vger.kernel.org
Subject: Re: [RFC][PATCH] introduce TASK_SIZE_OF() for all arches
Date: Wed, 22 Aug 2007 16:15:46 -0700 [thread overview]
Message-ID: <1187824547.16177.1352.camel@localhost> (raw)
In-Reply-To: <31048.1187773615@redhat.com>
On Wed, 2007-08-22 at 10:06 +0100, David Howells wrote:
> Dave Hansen <haveblue@us.ibm.com> wrote:
> > For the /proc/<pid>/pagemap code[1], we need to able to query how
> > much virtual address space a particular task has.
>
> How does this relate to NOMMU conditions?
Were you asking about /proc/<pid>/pagemap, or about my TASK_SIZE_OF()
macro?
/proc/<pid>/pagemap is completely implemented in task_mmu.c, so it
shouldn't show up on NOMMU systems.
As far as TASK_SIZE_OF(), it still makes sense on those systems because
they (at least m68k) still has TASK_SIZE. Was there a particular
problem you're concerned about? I'm not very intimately familiar with
the NOMMU code.
-- Dave
next prev parent reply other threads:[~2007-08-22 23:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-21 19:38 [RFC][PATCH] introduce TASK_SIZE_OF() for all arches Dave Hansen
2007-08-21 19:43 ` Matthew Wilcox
2007-08-22 17:30 ` Ralf Baechle
2007-08-22 23:10 ` Dave Hansen
2007-08-22 9:06 ` David Howells
2007-08-22 22:55 ` Dave Hansen
2007-08-22 23:50 ` Matt Mackall
2007-08-22 23:15 ` Dave Hansen [this message]
2007-08-23 9:37 ` David Howells
[not found] <20070821132038.GA22254@ff.dom.local>
[not found] ` <20070821093103.3c097d4a.randy.dunlap@oracle.com>
2007-08-21 17:35 ` RFC: drop support for gcc < 4.0 Adrian Bunk
2007-08-21 19:19 ` Andi Kleen
2007-08-21 19:54 ` Adrian Bunk
2007-08-21 20:07 ` [RFC][PATCH] introduce TASK_SIZE_OF() for all arches Matthew Wilcox
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=1187824547.16177.1352.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=dhowells@redhat.com \
--cc=linux-arch@vger.kernel.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).