From: Andrew Morton <akpm@zip.com.au>
To: Daniel Phillips <phillips@arcor.de>
Cc: Rik van Riel <riel@conectiva.com.br>,
Linus Torvalds <torvalds@transmeta.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch 1/13] minimal rmap
Date: Sun, 21 Jul 2002 19:40:05 -0700 [thread overview]
Message-ID: <3D3B7085.DADED6F@zip.com.au> (raw)
In-Reply-To: E17Uuti-0004PT-00@starship
Daniel Phillips wrote:
>
> ...
> I think Andrew also mentioned he sees a lot of buffers sitting around
> in the morning. His strip-buffers-immediately hack would kill that
> one dead.
Nope. It was all inodes and dentries.
`buffermem' accounting went away in 2.5 altogether. And the
zillions-of-buffer_heads problems should be greatly improved
because a) they're half the size of 2.4's bhs and b) we
no longer attach buffer_heads for reads.
-
next prev parent reply other threads:[~2002-07-22 2:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-17 5:29 [patch 1/13] minimal rmap Andrew Morton
2002-07-17 8:24 ` Russell King
2002-07-17 12:10 ` Rik van Riel
2002-07-17 12:21 ` Rik van Riel
2002-07-17 17:57 ` Daniel Phillips
2002-07-17 18:11 ` Robert Love
2002-07-17 18:26 ` Daniel Phillips
2002-07-17 20:37 ` Rik van Riel
2002-07-17 20:42 ` Robert Love
2002-07-17 20:46 ` Daniel Phillips
2002-07-17 20:48 ` Robert Love
2002-07-17 19:31 ` Rik van Riel
2002-07-17 19:38 ` Daniel Phillips
2002-07-17 19:41 ` Rik van Riel
2002-07-17 19:55 ` Daniel Phillips
2002-07-17 20:04 ` Rik van Riel
2002-07-17 20:13 ` Daniel Phillips
2002-07-17 20:25 ` Rik van Riel
2002-07-17 20:25 ` Rik van Riel
2002-07-17 20:36 ` Daniel Phillips
2002-07-17 20:39 ` Rik van Riel
2002-07-17 20:50 ` Dave Jones
2002-07-17 20:53 ` Robert Love
2002-07-22 2:40 ` Andrew Morton [this message]
2002-07-17 19:42 ` Robert Love
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=3D3B7085.DADED6F@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@arcor.de \
--cc=riel@conectiva.com.br \
--cc=torvalds@transmeta.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.