On Tue, May 30, 2017 at 01:17:41PM -0500, Christoph Lameter wrote:
> On Fri, 26 May 2017, Marcelo Tosatti wrote:
>
> > > interrupts and scheduler ticks. But what does this have to do with vmstat?
> > >
> > > Show me your dpdk code running and trace the tick on / off events as well
> > > as the vmstat invocations. Also show all system calls occurring on the cpu
> > > that runs dpdk. That is necessary to see what triggers vmstat and how the
> > > system reacts to the changes to the differentials.
This was in the host, while performing virtual machine migration... Which you
can
say "invalidates the argument" because virtual machine migration takes
MUCH longer time than what vmstat_update introduces.
> >
> > Sure, i can get that to you. The question remains: Are you arguing
> > its not valid for a realtime application to use any system call
> > which changes a vmstat counter?
>
> A true realtime app would be conscientious of its use of the OS services
> because the use of the services may cause additional latencies and also
> cause timers etc to fire later. A realtime app that is willing to use
> these services is therefore willing to tolerate larger latencies. A
> realtime app that is using OS service may cause the timer tick to be
> enabled which also causes additional latencies.
>
> I have seen completely OS noise free processing for extended time period
> when not using OS services and using RDMA for I/O. This fits my use case
> well.
People might want to use O/S services.
> If there are really these high latencies because of kworker processing for
> vmstat then maybe we need a different mechanism there (bh? or other
> triggers) and maybe we are using far too many counters so that the
> processing becomes a heavy user of resources.
>
> > Because if they are allowed, then its obvious something like
> > this is needed.
>
> I am still wondering what benefit there is. Lets get clear on the test
> load and see if this actually makes sense.
Ok, test load:
* Any userspace app that causes a systemcall which triggers
vmstat_update is susceptible to vmstat_update running on that
CPU, which might be detrimental to latency.
So either something which moves vmstat_update work to another CPU,
or that avoids vmstat_update (which is what the proposed patchset does),
must be necessary.
So if a customer comes to me and says: "i am using sys_XXX in my
application, but my latency is high", i'll have to tell him: "ok, please
don't use that system call since it triggers kernel activity on the CPU
which does not allow you to achieve the latency you desire".
But it seems the "no syscalls" rule seems to be a good idea for
CPU isolated, low latency stuff...
So i give up on the use-case behind this patch.
