On Fri, Oct 07, 2011 at 11:09:07PM +0530, Ritesh Raj Sarraf wrote:
> On Friday, October 7, 2011, Alessandro Ghedini wrote:
> > ulatencyd reports errors of not being able to write to a
> processes's
> > memory limits. Attached log has more details
>
> > WARNING: can't write into
> > :/sys/fs/cgroup/memory/usr_1000/pgr_2983/
> memory.memsw.limit_in_bytes
>
> I don't have memory.memsw.limit_in_bytes too, but I don't get those
> warnings. I tried on a stock kernel twice, enabling and disabling
> CONFIG_CGROUP_MEM_RES_CTLR_SWAP, and on a custom kernel without it at
> all.
>
> (If ulatencyd couldn't access the memory subsystem it would have
> printed
> something like "can't access memory subsystem").
>
> Did you recompile the kernel? Did you modify the scheduler/20-
> desktop.lua
> file (or did you write your own rule file using that option)? Did
> those
> warnings appear recently or have been there for a while?
>
>
> None. This is a stock Debian kernel with cgroup_enable=memory on the kernel
> command line. Apart from that, I've done no changes.
> I just followed your README.Debian instructions.
Did you try passing swapaccount=1 to the kernel? Let me know if it helps,
I'll update README.Debian accordingly.
Cheers
--
perl -E'$_=q;$/= @{[@_]};and s;\S+;<inidehG ordnasselA>;eg;say~~reverse'
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
