public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@gmail.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Aucoin@Houston.RR.com, "'Linus Torvalds'" <torvalds@osdl.org>,
	"'Tim Schmielau'" <tim@physik3.uni-rostock.de>,
	"'Andrew Morton'" <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, clameter@sgi.com
Subject: Re: la la la la ... swappiness
Date: Tue, 05 Dec 2006 08:26:17 +0100	[thread overview]
Message-ID: <45751F19.9010208@gmail.com> (raw)
In-Reply-To: <45751955.8010506@yahoo.com.au>

Nick Piggin wrote:

> Aucoin wrote:

>> Ummm, shm_open, ftruncate, mmap ? Is it a trick question ? The process
>> responsible for initially setting up the shared area doesn't stay 
>> resident.
> 
> The issue is that the shm pages should show up in the active and
> inactive lists. But they aren't, and you seem to have about 1542524K
> unacconted for. Weird.
> 
> Can you try getting the output of /proc/vmstat as well?

Haven't followed along on this thread, but couldn't help notice the 
ftruncate there and some similarity to a problem I once experienced 
myself. Is ext3 involved? If so, maybe:

http://mail.nl.linux.org/linux-mm/2002-11/msg00110.html

is still or again being annoying?

Rene.


  reply	other threads:[~2006-12-05  7:27 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200612030616.kB36GYBs019873@ms-smtp-03.texas.rr.com>
2006-12-03  8:08 ` la la la la ... swappiness Andrew Morton
2006-12-03 15:40   ` Aucoin
2006-12-03 20:46     ` Tim Schmielau
2006-12-03 23:56       ` Aucoin
2006-12-04  0:57         ` Horst H. von Brand
2006-12-04  4:56         ` Andrew Morton
2006-12-04  5:13           ` Linus Torvalds
2006-12-04 17:03             ` Christoph Lameter
2006-12-04 10:43         ` Nick Piggin
2006-12-04 14:45           ` Aucoin
2006-12-04 15:04             ` Nick Piggin
2006-12-05  4:02               ` Aucoin
2006-12-05  4:46                 ` Linus Torvalds
2006-12-05  6:41                   ` Aucoin
2006-12-05  7:01                     ` Nick Piggin
2006-12-05  7:26                       ` Rene Herman [this message]
2006-12-05 13:27                         ` Aucoin
2006-12-05 13:49                           ` Rene Herman
2006-12-05 13:25                       ` Aucoin
2006-12-04 19:02 Al Boldi
  -- strict thread matches above, loose matches on Subject: below --
2006-12-04  1:54 Aucoin
2006-12-04  4:59 ` Andrew Morton
2006-12-04  7:22 ` Kyle Moffett
2006-12-04 14:39   ` Aucoin
2006-12-04 16:10     ` Chris Friesen
2006-12-04 17:07     ` Horst H. von Brand
2006-12-04 17:49       ` Aucoin
2006-12-04 18:44         ` Tim Schmielau
2006-12-04 21:28           ` Aucoin
2006-12-04 18:46         ` Horst H. von Brand
2006-12-04 21:43           ` Aucoin
2006-12-04 18:06       ` Andrew Morton
2006-12-04 18:15         ` Christoph Lameter
2006-12-04 18:38           ` Jeffrey Hundstad
2006-12-04 21:25             ` Aucoin
2006-12-04 21:43               ` Andrew Morton
2006-12-04 15:55   ` David Lang
2006-12-04 17:42     ` Aucoin
2006-12-03  6:18 Aucoin

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=45751F19.9010208@gmail.com \
    --to=rene.herman@gmail.com \
    --cc=Aucoin@Houston.RR.com \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=tim@physik3.uni-rostock.de \
    --cc=torvalds@osdl.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