On Fri, 10 May 2013, Will Huck wrote: > On 05/09/2013 10:00 PM, Christoph Lameter wrote: > > On Thu, 9 May 2013, Will Huck wrote: > > > > > On 05/02/2013 11:10 PM, Christoph Lameter wrote: > > > > On Wed, 1 May 2013, Will Huck wrote: > > > > > > > > > > Age refers to the mininum / avg / maximum age of the object in > > > > > > ticks. > > > > > Why need monitor the age of the object? > > > > Will give you some idea as to when these objects were created. > > > Thanks for your clarify. ;-) But why mininum / avg / maximum instead of a > > > single value? > > You can see the age of the oldest and youngest object. > > > > It seems that age = jiffies - track->when; can't accurately describe age of > each used object in one slab. The objects in one slab should be same age in > current logic, but jiffies are changed when each time enter into add_location. The objects could be allocated at any time. The track structure is per object not per slab. The "age" refers to the time in jiffies since object allocation. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>