Re: 2.6.39-rc4+: Kernel leaking memory during FS scanning,regression?

[Mike Galbraith]

On Thu, 2011-04-28 at 17:28 +0200, Sedat Dilek wrote:

> OK, I tried with the patch proposed by Thomas (0003):

(thanks)

> patches/0001-Revert-rcu-restrict-TREE_RCU-to-SMP-builds-with-PREE.patch
> patches/0002-sched-Add-warning-when-RT-throttling-is-activated.patch
> patches/0003-sched-Remove-skip_clock_update-check.patch
> 
> >From the very beginning it looked as the system is "stable" due to:
> 
>   .rt_nr_running                 : 0
>   .rt_throttled                  : 0
> 
> This changed when I started a simple tar-job to save my kernel
> build-dir to an external USB-hdd.
> From...
> 
>   .rt_nr_running                 : 1
>   .rt_throttled                  : 1
> 
> ...To:
> 
>   .rt_nr_running                 : 2
>   .rt_throttled                  : 1
> 
> Unfortunately, reducing all activities to a minimum load, did not
> change from last known RT throttling state.
> 
> Just noticed rt_time exceeds the value of 950 first time here:

That would happen even if we did forced eviction.

> ----------------------------------------------------------------------------------------------------------
> R            cat  2652    115108.993460         1   120
> 115108.993460         1.147986         0.000000 /
> --
> rt_rq[0]:
>   .rt_nr_running                 : 1
>   .rt_throttled                  : 1
>   .rt_time                       : 950.005460
>   .rt_runtime                    : 950.000000
> ----------------------------------------------------------------------------------------------------------
>            rcuc0     7         0.000000     56869    98
> 0.000000       981.385605         0.000000 /
> --
> rt_rq[0]:
>   .rt_nr_running                 : 2
>   .rt_throttled                  : 1
>   .rt_time                       : 950.005460
>   .rt_runtime                    : 950.000000

Still getting stuck.  Eliminates the clock update optimization, but that
seemed unlikely anyway.  (I'll build a UP kernel and poke it)

	-Mike

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/