switch from 'query' to 'stream' terminology
Closed this issue · 1 comments
We have lots of things using the term 'query' which is a hangover from code for working with the GL_INTEL_performance_query extension. In that case a query represents a delimited query for metrics made via the command stream whereas mostly all other metrics are periodically sampled and read from the kernel as a stream.
At some point we should get rid of this naming confusion.
In the case of struct gputop_perf_query this represents the (mostly immutable) meta data for a metric set, automatically generated from the XML data by oa-gen.py. probably struct gputop_metric_set would be a better description.
struct gputop_worker_query has an extra naming hangover from when the code used to be run in a Web Worker thread which isn't true anymore. This one should probably become a 'stream' something like struct gputop_remote_stream