This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Hi,something about the xentrace tool

rickey berkeley wrote:
so,dose this mechanisms will effect the system performance evidently?as we know ,copy huge raw data from kernel space to user space will exhaust so much efficiency and system resource.

I wouldn't call the amount of data 'huge'. Even on a very busy system, where there are thousands of trace records being generated every second, that's still a pretty small amount of data. (The size of a trace record is something like 50 or 60 bytes.) Also, the data is not "copied" from kernel space to user space. There is a shared memory buffer which xen writes into, and the user app reads out of. Memory read speeds are currently in the Gb/s range. So to answer your question, I don't think that this mechanism affects system performance in any significant way.

How about make use of relayfs? It is some kind of standardization of the way in which large amounts of data are transferred from kernel space to user space.

If the data were only being transferred between the linux kernel and a linux app, then I'd say yeah, relayfs sounds like a cool thing to do. However, the trace records are generated by the xen hypervisor, not the linux kernel. The hypervisor doesn't have relayfs (or any fs for that matter), so you're stuck with involving the linux kernel which would read stuff from a shared hypervisor buffer, then present the data to userland via relayfs. Doesn't sound like a better solution than what we have now.


Xen-devel mailing list