Measure and compare syscall overhead in VM and in container.

There're several ways to do it.

1. using "lmbench". It's pre-installed on CrOS test image. The benefit of using it is that it contains other micro-benchmarks involving memory/network bandwidth and latency. However other than building it from source, the package is in Debian "non-free" component. So I'll need to modify apt sources.list to include non-free packages. Our usage didn't violet additional restrictions of lmbench though. 

2. Build open source third-party syscall benchmark from source, be it lmbench or other benchmark like unixbench. I'll need a way to pre-compile the source code and install it into the container however. Do we have a cross-compiler setup for the container? I can install gcc/clang and compile the code on-the-fly when running the benchmark, but I believe this less preferable. If we setup the toolchain, it would be useful in the future when we need to build other binary from source.

3. Write my own code snippet in other interpreter language like python or Lua. Python is pre-installed and luajit is small.  

Option 1 would be the most easy way, if adding "non-free" to container source list is not a problem.