The interesting bit is what happens inside arc_reclaim_needed(), 
that is, how it arrives at the conclusion that there is memory pressure. 

Maybe we could trace arg0, which gives the location where 
we have left the function. This would finger which return path 
arc_reclaim_needed() took. 


----- Original Message -----

Well it looks like the only place this get's changed is in the 
arc_reclaim_thread for opensolaris. I suppose you could dtrace it to see what 
is going on and investigate what is happening to the return code of the 
arc_reclaim_needed is.


dtrace -n 'fbt:zfs:arc_reclaim_needed:return { trace(arg1) }' 


zfs-discuss mailing list

Reply via email to