summaryrefslogtreecommitdiff
path: root/flowtop.zsh
diff options
context:
space:
mode:
authorKen-ichirou MATSUZAWA <chamaken@gmail.com>2015-09-11 16:57:37 +0900
committerTobias Klauser <tklauser@distanz.ch>2015-09-15 10:47:37 +0200
commit67728607d5144cd36d056c4289c7e53f9113329a (patch)
tree7d259435a6dbde4ca70bb083df9705527117795f /flowtop.zsh
parent4669e7a1ac2112b0e9ba7c0b865fdedffbb86055 (diff)
netsniff-ng: nlmsg: update pull size
It would be better to use NLMSG_HDRLEN instead of sizeof(*hdr) and not to use NLMSG_PAYLOAD to get payload length, I think. Signed-off-by: Ken-ichirou MATSUZAWA <chamas@h4.dion.ne.jp> Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Diffstat (limited to 'flowtop.zsh')
0 files changed, 0 insertions, 0 deletions
msg'>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 'drivers/usb/atm/usbatm.h')