public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Cc: Lukas Hejtmanek <xhejtman@ics.muni.cz>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.28-rc8 big regression in VM
Date: Tue, 16 Dec 2008 16:08:12 -0500	[thread overview]
Message-ID: <494818BC.6050505@tmr.com> (raw)
In-Reply-To: <20081213140214.GA21627@localhost>

KVMWu Fengguang wrote:
> On Sat, Dec 13, 2008 at 11:58:15AM +0200, Lukas Hejtmanek wrote:
>> On Sat, Dec 13, 2008 at 09:21:15AM +0800, Wu Fengguang wrote:
>>> I cannot reproduce it on 2.6.28-rc7, compiling 2.6.28-rc8...
>>>
>>> # free; echo 3 > /proc/sys/vm/drop_caches; free
>>>              total       used       free     shared    buffers     cached
>>> Mem:          1940        109       1831          0          0         42
>>> -/+ buffers/cache:         66       1873
>>> Swap:            0          0          0
>>>              total       used       free     shared    buffers     cached
>>> Mem:          1940         62       1877          0          0          7
>>> -/+ buffers/cache:         55       1884
>>> Swap:            0          0          0
>>>
>>>> once the whole memory is eaten by the cache, the system is pretty unusable.
>>> What's your kconfig?
>> attached.
> 
> OK I'll try it. I cannot produce the bug in my -rc8 configuration yet:
> 
> # free; echo 3 > /proc/sys/vm/drop_caches; free
>              total       used       free     shared    buffers     cached
> Mem:          1940        906       1033          0          0        761
> -/+ buffers/cache:        144       1795
> Swap:            0          0          0
>              total       used       free     shared    buffers     cached
> Mem:          1940        147       1793          0          0         19
> -/+ buffers/cache:        127       1813
> Swap:            0          0          0
> 

Could the problem be related to him running 2GB memory and you running... well, 
maybe a patches version of "free?" Or can you really run in 2MB, or am I misreading?

-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot


  reply	other threads:[~2008-12-16 21:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-12 18:38 2.6.28-rc8 big regression in VM Lukas Hejtmanek
2008-12-13  1:21 ` Wu Fengguang
2008-12-13  9:58   ` Lukas Hejtmanek
2008-12-13 14:02     ` Wu Fengguang
2008-12-16 21:08       ` Bill Davidsen [this message]
2008-12-15  1:16     ` Wu Fengguang
2008-12-15  2:05       ` KOSAKI Motohiro
2008-12-15  9:53         ` Lukas Hejtmanek
2008-12-15 10:56           ` KOSAKI Motohiro
2008-12-15  9:44       ` Lukas Hejtmanek
2008-12-16  4:59         ` Wu Fengguang
     [not found]           ` <20081216195219.GA4480@ics.muni.cz>
2008-12-17 12:27             ` Wu Fengguang
2008-12-17 12:33               ` Lukas Hejtmanek
2008-12-17 12:44                 ` Wu Fengguang
2008-12-17 12:49                   ` Lukas Hejtmanek
2008-12-17 13:02                     ` Wu Fengguang
2008-12-25 10:50                     ` Wu Fengguang
2008-12-25 10:58                       ` Lukas Hejtmanek
2008-12-25 11:18                         ` Wu Fengguang

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=494818BC.6050505@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xhejtman@ics.muni.cz \
    /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