On 27/04/17 00:21, Prakash, Prashanth wrote: > Hi Sudeep, > > On 4/25/2017 4:28 AM, Sudeep Holla wrote: >>> With hierarchy, it is possible to get information about relationship between cpus >>> and higher order shared resources. If we flatten the hierarchy we lose information >>> about relationships and it gets a little hard to clearly represent the idle states of >>> shared resources and which cpus share those resources. >>> >> No, what I meant is to have complete information broken down to the >> lowest possible level, but just one file access to get that information. >> >> IIUC, you had some format already for summary_stat file, just extend >> to get all the information you would get reading individual sysfs files >> organized hierarchically. I don't think that should matter much as you >> would have all these information, just the representation differs. I am >> assuming all this data is not used/interpreted on the fly, but mostly >> used offline for analysis. Otherwise it's already misuse and we don't >> want to expose such user ABI IMO. >> >> Just to summarize, though I agree this LPI stats are more accurate and >> more representative summary, I think it may fade away as we move towards >> hardware controlled lower power states. Since we already have cpuidle >> stats, I prefer to keep this LPI stats interface to userspace as simple >> and minimal as possible and yet helpful to get all the information. > > Sounds good. I will remove summary_stats and make other changes based on > feedback and post next rev. I am sorry if I was not clear earlier, I was infact asking you what if we just have single summary_stat file with all statistics broken down to minuet details you want instead of creating the hierarchy of individual files which you say has overhead to read. Do you process the stats on the fly when workload is running, I assume not. -- Regards, Sudeep -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
