linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: John Richard Moser <nigelenki@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why does the kernel need a gig of VM?
Date: Fri, 28 Jan 2005 14:44:54 -0600	[thread overview]
Message-ID: <41FAA446.5090704@nortelnetworks.com> (raw)
In-Reply-To: <41FA9B37.1020100@comcast.net>

John Richard Moser wrote:

> So what's the layout of that top 1G?  What's it all used for?  Is there
> some obscene restriction of 1G of shared memory or something that gets
> mapped up there?
> 
> How much does it need, and why?  What, if anything, is variable and
> likely to do more than 10 or 15 megs of variation?

I'm guessing the high runners in the variable category are likely to be 
the page cache, all kinds of in-flight IO buffers, and such.

Chris

  parent reply	other threads:[~2005-01-29 16:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-28 20:06 Why does the kernel need a gig of VM? John Richard Moser
2005-01-28 20:42 ` Josh Boyer
2005-01-28 20:48   ` John Richard Moser
2005-02-01 15:15     ` Bill Davidsen
2005-01-28 21:42   ` Oliver Neukum
2005-01-28 20:44 ` Chris Friesen [this message]
2005-01-29  1:32 ` Andy Isaacson

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=41FAA446.5090704@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nigelenki@comcast.net \
    /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).