Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1640561
| From | Christoph Lameter <cl@linux.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [patch 2/2] MM: allow per-cpu vmstat_threshold and vmstat_worker configuration |
| Date | 2017-05-12 18:10 +0200 |
| Message-ID | <tGliF-71V-9@gated-at.bofh.it> (permalink) |
| References | (4 earlier) <tCJCV-1aP-3@gated-at.bofh.it> <tFYm5-88r-7@gated-at.bofh.it> <tGhRL-4rF-9@gated-at.bofh.it> <tGkwi-6qS-11@gated-at.bofh.it> <tGkZj-6DA-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Fri, 12 May 2017, Marcelo Tosatti wrote: > In our case, vmstat updates are very rare (CPU is dominated by DPDK). What is the OS doing on the cores that DPDK runs on? I mean we here can clean a processor of all activities and are able to run for a long time without any interruptions. Why would you still let the OS do things on that processor? If activities by the OS are required then the existing NOHZ setup already minimizes latency to a short burst (and Chris Metcalf's work improves on that). What exactly is the issue you are seeing and want to address? I think we have similar aims and as far as I know the current situation is already good enough for what you may need. You may just not be aware of how to configure this. I doubt that doing inline updates will do much good compared to what we already have and what the dataplan mode can do.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [patch 2/2] MM: allow per-cpu vmstat_threshold and vmstat_worker configuration Marcelo Tosatti <mtosatti@redhat.com> - 2017-05-12 14:30 +0200
Re: [patch 2/2] MM: allow per-cpu vmstat_threshold and vmstat_worker configuration Christoph Lameter <cl@linux.com> - 2017-05-12 17:20 +0200
Re: [patch 2/2] MM: allow per-cpu vmstat_threshold and vmstat_worker configuration Marcelo Tosatti <mtosatti@redhat.com> - 2017-05-12 17:50 +0200
Re: [patch 2/2] MM: allow per-cpu vmstat_threshold and vmstat_worker configuration Christoph Lameter <cl@linux.com> - 2017-05-12 18:10 +0200
Re: [patch 2/2] MM: allow per-cpu vmstat_threshold and vmstat_worker configuration Christoph Lameter <cl@linux.com> - 2017-05-12 18:10 +0200
Re: [patch 2/2] MM: allow per-cpu vmstat_threshold and vmstat_worker configuration Marcelo Tosatti <mtosatti@redhat.com> - 2017-05-12 18:30 +0200
Re: [patch 2/2] MM: allow per-cpu vmstat_threshold and vmstat_worker configuration Christoph Lameter <cl@linux.com> - 2017-05-12 19:00 +0200
Re: [patch 2/2] MM: allow per-cpu vmstat_threshold and vmstat_worker configuration Marcelo Tosatti <mtosatti@redhat.com> - 2017-05-15 21:20 +0200
Re: [patch 2/2] MM: allow per-cpu vmstat_threshold and vmstat_worker configuration Christoph Lameter <cl@linux.com> - 2017-05-16 15:40 +0200
Re: [patch 2/2] MM: allow per-cpu vmstat_threshold and vmstat_worker configuration Marcelo Tosatti <mtosatti@redhat.com> - 2017-05-19 16:40 +0200
Re: [patch 2/2] MM: allow per-cpu vmstat_threshold and vmstat_worker configuration Christoph Lameter <cl@linux.com> - 2017-05-19 19:20 +0200
Re: [patch 2/2] MM: allow per-cpu vmstat_threshold and vmstat_worker configuration Luiz Capitulino <lcapitulino@redhat.com> - 2017-05-19 20:00 +0200
Re: [patch 2/2] MM: allow per-cpu vmstat_threshold and vmstat_worker configuration Christoph Lameter <cl@linux.com> - 2017-05-22 18:40 +0200
Re: [patch 2/2] MM: allow per-cpu vmstat_threshold and vmstat_worker configuration Marcelo Tosatti <mtosatti@redhat.com> - 2017-05-20 10:30 +0200
Re: [patch 2/2] MM: allow per-cpu vmstat_threshold and vmstat_worker configuration Christoph Lameter <cl@linux.com> - 2017-05-22 18:40 +0200
Re: [patch 2/2] MM: allow per-cpu vmstat_threshold and vmstat_worker configuration Marcelo Tosatti <mtosatti@redhat.com> - 2017-05-22 23:20 +0200
csiph-web