On 07/21/2014 12:55 AM, Jiri Olsa wrote: > hi, > this patchset factors session's ordered samples queue, > and allows to limit the size of this queue. > > v3 changes: > - rebased to latest tip/perf/core > - add comment for WARN in patch 8 (David) > - added ordered-events debug variable (David) > - renamed ordered_events_(get|put) to ordered_events_(new|delete) > - renamed struct ordered_events_queue to struct ordered_events > > v2 changes: > - several small changes for review comments (Namhyung) > > > The report command queues events till any of following > conditions is reached: > - PERF_RECORD_FINISHED_ROUND event is processed > - end of the file is reached > > Any of above conditions will force the queue to flush some > events while keeping all allocated memory for next events. > > If PERF_RECORD_FINISHED_ROUND is missing the queue will
Why is it missing? > allocate memory for every single event in the perf.data. > This could lead to enormous memory consuption and speed > degradation of report command for huge perf.data files. > > With the quue allocation limit of 100 MB, I've got around > 15% speedup on reporting of ~10GB perf.data file. How do you know the results are still valid? Wouldn't it be better to wait that extra 15% and know that the data has been processed correctly? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
