On 27 March 2014 08:17, Li Zefan wrote:
> This doesn't look like a complete solution, because newer timers/workqueues
> can
> still run in those CPUs.
The initial idea was to disable load balance between CPUs and then do this.
So, that new timers and workqueues from other CPUs would never get
qu
On 2014/3/20 21:49, Viresh Kumar wrote:
> For networking applications platforms need to provide one CPU per each user
> space data plane thread. These CPUs should not be interrupted by kernel at all
> unless userspace has requested for some syscalls. Currently, there are
> background kernel activit
For networking applications platforms need to provide one CPU per each user
space data plane thread. These CPUs should not be interrupted by kernel at all
unless userspace has requested for some syscalls. Currently, there are
background kernel activities that are running on almost every CPU, like:
3 matches
Mail list logo
