From: Andrew Morton <akpm@zip.com.au>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch-2.5.8-pre] swapinfo accounting
Date: Wed, 10 Apr 2002 17:48:49 -0700 [thread overview]
Message-ID: <3CB4DD71.DED82F57@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0204101755170.25409-100000@dragon.pdx.osdl.net>
"Randy.Dunlap" wrote:
>
> It looks to me like mm/swapfile.c::si_swapinfo()
> shouldn't be adding nr_to_be_unused to total_swap_pages
> or nr_swap_pages for return in val->freeswap and
> val->totalswap.
whee, an si_swapinfo() maintainer.
Your function sucks :) I'm spending 15 CPU-seconds
in there during a kernel build. The problem appears
to be that a fix from 2.4 hasn't been propagated
forward.
2.4 has:
if (swap_info[i].flags != SWP_USED)
and 2.5 has:
if (!(swap_info[i].flags & SWP_USED))
and I think the 2.4 version will fix the accounting
problem you're seeing?
(I haven't checked whather it's the _right_ fix, but
it looks like it'll make it go away?)
-
next prev parent reply other threads:[~2002-04-11 1:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-11 1:20 [patch-2.5.8-pre] swapinfo accounting Randy.Dunlap
2002-04-11 0:48 ` Andrew Morton [this message]
2002-04-11 3:52 ` rddunlap
2002-04-11 15:15 ` Hugh Dickins
2002-04-11 17:18 ` Randy.Dunlap
2002-04-11 1:46 ` Mike Fedyk
2002-04-11 3:57 ` rddunlap
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=3CB4DD71.DED82F57@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@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