xfs
[Top] [All Lists]

Re: TAKE - backport kswapd changes from later kernels

To: lord@xxxxxxx
Subject: Re: TAKE - backport kswapd changes from later kernels
From: cattelan@xxxxxxxxxxx
Date: Tue, 18 Apr 2000 11:28:46 -0500
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: In your message of "Tue, 18 Apr 2000 11:10:03 -0500 (CDT)" <200004181610.LAA79745@clink.americas.sgi.com>
References: <200004181610.LAA79745@clink.americas.sgi.com>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Wanderlust/1.0.3 (Notorious) tm/7.108 XEmacs/21.1 (Bryce Canyon)
What to do you think... time to move the tree to pre5?
At Tue, 18 Apr 2000 11:10:03 -0500 (CDT),
Steve Lord <lord@xxxxxxx> wrote:
> 
> 
> Modid:  2.3.99pre2-xfs:slinx:58410a
> Date:  Tue Apr 18 09:09:35 PDT 2000
> Workarea:  clink.americas.sgi.com:/data/clink/io/lord/xfs-linux
> 
> The following file(s) were checked into:
>   bonnie.engr.sgi.com:/isms/slinx/2.3.99pre2-xfs
> 
> linux/mm/vmscan.c - 1.24
http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.4-xfs/> 
linux/mm/vmscan.c.diff?r1=text&tr1=1.24&r2=text&tr2=1.23&f=h
>       - Backport changes to kswapd into the xfs tree - this appeared to be 
> having
>         bad interactions with XFS (memory corruption). I was able to do much 
> more
>         with XFS after this change. [ The basic problem in kswapd was that it
>         ran for its complete timeslice even when there was nothing to do. ]

<Prev in Thread] Current Thread [Next in Thread>