public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Wilson" <defiler@null.net>
To: <linux-kernel@vger.kernel.org>
Subject: Re: Which is better at vm, and why? 2.2 or 2.4
Date: Sat, 13 Oct 2001 15:28:23 -0400	[thread overview]
Message-ID: <02ca01c1541d$391c5f30$c800000a@Artifact> (raw)
In-Reply-To: <20011013141709.L249@localhost> <Pine.LNX.4.33L.0110131526500.2847-100000@imladris.rielhome.conectiva> <20011013144220.P249@localhost> <20011013145341.R249@localhost>

----- Original Message -----
From: "Patrick McFarland" <unknown@panax.com>
To: "Rik van Riel" <riel@conectiva.com.br>
Cc: <linux-kernel@vger.kernel.org>
Sent: Saturday, October 13, 2001 2:53 PM
Subject: Re: Which is better at vm, and why? 2.2 or 2.4

>Also, I'd like to say about the documentation...
>
><quote>
>Currently, these files are in /proc/sys/vm:
>- bdflush
>- buffermem
>- freepages
>- kswapd
>- overcommit_memory
>- page-cluster
>- pagecache
>- pagetable_cache
></quote>
>
>but a simple ls of /proc/sys/vm reports:
>bdflush  kswapd  overcommit_memory  page-cluster  pagetable_cache
>
>Shouldnt the documentation be updated, seeing for the fact it was written
in the 2.2.10 days?

I must be confused.. What kernel are you running?
This is on 2.4.8-ac9:
[root@aeon /root]# ls /proc/sys/vm
bdflush    freepages  max_map_count  min-readahead      pagecache
pagetable_cache
buffermem  kswapd     max-readahead  overcommit_memory  page-cluster




  parent reply	other threads:[~2001-10-13 19:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-13 17:02 Which is better at vm, and why? 2.2 or 2.4 Patrick McFarland
2001-10-13 17:16 ` Alan Cox
2001-10-13 18:06   ` M. Edward Borasky
2001-10-13 18:17     ` Patrick McFarland
2001-10-13 18:29       ` Rik van Riel
2001-10-13 18:42         ` Patrick McFarland
2001-10-13 18:53           ` Patrick McFarland
2001-10-13 18:58             ` Rik van Riel
2001-10-13 19:04               ` Patrick McFarland
2001-10-13 19:10                 ` Rik van Riel
2001-10-13 19:28             ` Wilson [this message]
2001-10-13 20:12               ` [solid]
2001-10-13 20:21               ` Patrick McFarland
2001-10-13 19:17           ` Rik van Riel
2001-10-13 18:37       ` M. Edward Borasky
2001-10-20  0:38     ` Daniel Phillips
2001-10-20  1:05       ` Robert Love
2001-10-20 19:56         ` Mike Fedyk
2001-10-20 20:03           ` Robert Love
2001-10-13 17:48 ` Mark Hahn
2001-10-13 21:29   ` Mike Fedyk
2001-10-13 21:47     ` Mark Hahn
     [not found] <20011013132327.F249@localhost>
     [not found] ` <E15sSey-0003Jf-00@the-village.bc.nu>
2001-10-13 17:33   ` Patrick McFarland
     [not found]     ` <E15sSti-0003ME-00@the-village.bc.nu>
2001-10-13 17:49       ` Patrick McFarland

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='02ca01c1541d$391c5f30$c800000a@Artifact' \
    --to=defiler@null.net \
    --cc=linux-kernel@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