On 09/19/2013 04:45 PM, sf...@users.sourceforge.net wrote:
> Flavio, if you can, please try commenting out a line in fs/aufs/file.c
> and reproducing the problem.
>
> const struct address_space_operations aufs_aop = {
> :::
> - .migratepage = aufs_migratepage,
> + /* .migratepage = aufs_migratepage, */
> :::
> };
Unfortunately this does not solve the issue.
Moreover the debugging messages you asked me to add are not providing
any useful message. As I told you in my previous mail I had to load the
aufs module with debug=1 in order to see more messages inside of the
kernel logs. That however slowed down the whole system. It would be
definitely better to leave debug=0 when loading the kernel module.
> If opensuse have a package called numaclt and it contains a command
> named migratepage, then it may be a easier way to reproduce (I am not
> sure).
Yes it does, I tried to use it but it didn't help.
> Current my questions are
> - is this problem NUMA machine specific?
> - is your machine NUMA avaliable? in other words, does your machine have
> multiple memory node?
According to the output of numastats my machine has a single memory node:
flavio@roesti ~ ยป numastat
node0
numa_hit 7026419
numa_miss 0
numa_foreign 0
interleave_hit 18280
local_node 7026419
other_node 0
Thanks for your help
Flavio
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
