summaryrefslogtreecommitdiff
path: root/COPYING
diff options
context:
space:
mode:
authorDaniel Borkmann <dborkman@redhat.com>2013-03-22 12:29:19 +0100
committerDaniel Borkmann <dborkman@redhat.com>2013-03-22 12:29:19 +0100
commit08c2dc1fcb403519a86a1129ad27c3188294e18f (patch)
tree39885c89ebf328b8e40162f93b1b5263cc12101f /COPYING
parent540ae1ee3b2456355fc9c36410667e1b5019e314 (diff)
trafgen: fix bug in packet scheduling
When having a config like cpu(1): {...}, and one runs it with -n1, trafgen behaves buggy, I also noted that in other situations. Fix this by letting the loop also return on CPU state RES, and do not perform this stupid magic in the main routine. So far it seems to work now after some basic tests I did. Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions
callback starts the timer with add_timer_on(). So the timer is already queued which triggers the BUG. Using add_timer_on() is pretty pointless in this code because the timer is strictlty per CPU, initialized as pinned and all operations which arm the timer happen on the CPU to which the timer belongs. Simplify the whole machinery by using mod_timer() instead of add_timer_on() which avoids the problem because mod_timer() can handle already queued timers. Use __start_timer() everywhere so the earliest armed expiry time is preserved. Reported-by: Erik Veijola <erik.veijola@intel.com> Tested-by: Borislav Petkov <bp@alien8.de> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Reviewed-by: Borislav Petkov <bp@alien8.de> Cc: Tony Luck <tony.luck@intel.com> Link: http://lkml.kernel.org/r/alpine.DEB.2.20.1701310936080.3457@nanos Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'net/rxrpc/conn_service.c')