This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH][malloc] Avoid atomics in have_fastchunks


Markus Trippelsdorf wrote:
    
> The reason why nobody uses your trace/simulation patches is because they
> generate way too much data and are just too complex/invasive for most
> users. And someone would have to analyze all this data.
> So it is natural to look for other metrics like code complexity instead.

Indeed, I can generate hundreds of gigabytes of malloc traces in a few hours...
But what's the point? Traces are many orders of magnitude too large to share
(let alone commit), and unlike the workloads for the math functions it is difficult
to reduce a huge trace and yet remain 100% representative. 

So I think we'll need to add microbenchmarks that test various aspects of
memory allocation. Extracting small representative kernels from existing
applications/benchmarks should be easier than dealing with huge traces...

Wilco

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]