summaryrefslogtreecommitdiff
path: root/ioops.c
diff options
context:
space:
mode:
authorDaniel Borkmann <dborkman@redhat.com>2013-07-11 17:21:09 +0200
committerDaniel Borkmann <dborkman@redhat.com>2013-07-11 17:21:09 +0200
commit4c139be17d5d26a1bba81c0775ca5c8fb3a6b181 (patch)
tree693ce5ee2e0d565f5b593d6a2cb89e6dfd2e70b2 /ioops.c
parentf1c783dc1c66b8868f011f327bf4e113a05f18f7 (diff)
link: allow future ethtool speed formats to be supported
In case some in the near future NICs with 40Gbit/s will appear. Allow ifpps to get the correct ethtool speed. Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
Diffstat (limited to 'ioops.c')
0 files changed, 0 insertions, 0 deletions
migration
The hwlat tracer creates a kernel thread at start of the tracer. It is pinned to a single CPU and will move to the next CPU after each period of running. If the user modifies the migration thread's affinity, it will not change after that happens. The original code created the thread at the first instance it was called, but later was changed to destroy the thread after the tracer was finished, and would not be created until the next instance of the tracer was established. The code that initialized the affinity was only called on the initial instantiation of the tracer. After that, it was not initialized, and the previous affinity did not match the current newly created one, making it appear that the user modified the thread's affinity when it did not, and the thread failed to migrate again. Cc: stable@vger.kernel.org Fixes: 0330f7aa8ee6 ("tracing: Have hwlat trace migrate across tracing_cpumask CPUs") Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'include/math-emu/op-4.h')