On Thu, May 15, 2008 at 11:43:40AM -0700, Christoph Lameter wrote:
> On Thu, 15 May 2008, Matthew Wilcox wrote:
>
> > > Details of the crash please?
> >
> > I don't have any.
>
> Well the amount of information we are getting has always been the main
> factor in delaying this further and further. Sigh.
Or possibly your assumptions have been the main factor. I gave you a
reproducer for this problem 6 weeks ago. As far as I can tell, you
haven't run it since.
> > > You could just start with 2.6.25.X which already contains the slab
> > > statistics.
> >
> > Certainly. Exactly how does collecting these stats work? Am I supposed
> > to zero the counters after the TPC has done its initial ramp-up? What
> > commands should I run, and at exactly which points?
>
> Compile slabinfo and then do f.e. slabinfo -AD (this is documented in the
> help text provided when enabling statistics).
That's an utterly unhelpful answer. Let me try asking again.
Exactly how does collecting these stats work? Am I supposed to zero
the counters after the TPC has done its initial ramp-up? What commands
should I run, and at exactly which points?
Otherwise I'll get something wrong and these numbers will be useless to
you. Or that's what you'll claim anyway.
For reference the helptext says:
SLUB statistics are useful to debug SLUBs allocation behavior in
order find ways to optimize the allocator. This should never be
enabled for production use since keeping statistics slows down
the allocator by a few percentage points. The slabinfo command
supports the determination of the most active slabs to figure
out which slabs are relevant to a particular load.
Try running: slabinfo -DA
By the way, when you say 'compile slabinfo', you mean the file shipped
as Documentation/vm/slabinfo.c (rather than, say, something out of tree?)
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
