summaryrefslogtreecommitdiff
path: root/trafgen.zsh
diff options
context:
space:
mode:
authorTobias Klauser <tklauser@distanz.ch>2013-09-09 12:40:14 +0200
committerTobias Klauser <tklauser@distanz.ch>2013-09-09 12:40:14 +0200
commitdefd121efe1c394fe002ce9b0f36a2422a054af7 (patch)
treec448f569c3dcf303f5943bfe6a973ff6da615b5e /trafgen.zsh
parent382b08547cc61faf10d94cffef890ce0dc85609c (diff)
ifpps: correct calculation of line rate percentage
The line rate is given in Mbit rather than MiB (in which {rx,tx}_bytes were converted). Correct the calculation by converting {rx,tx}_bytes to Mbit: (n bytes * 8 bits per byte) / 1000^2 = (n bytes) / 125000 Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Diffstat (limited to 'trafgen.zsh')
0 files changed, 0 insertions, 0 deletions
mmit-subject'>btrfs: fix races on root_log_ctx lists
btrfs_remove_all_log_ctxs takes a shortcut where it avoids walking the list because it knows all of the waiters are patiently waiting for the commit to finish. But, there's a small race where btrfs_sync_log can remove itself from the list if it finds a log commit is already done. Also, it uses list_del_init() to remove itself from the list, but there's no way to know if btrfs_remove_all_log_ctxs has already run, so we don't know for sure if it is safe to call list_del_init(). This gets rid of all the shortcuts for btrfs_remove_all_log_ctxs(), and just calls it with the proper locking. This is part two of the corruption fixed by cbd60aa7cd1. I should have done this in the first place, but convinced myself the optimizations were safe. A 12 hour run of dbench 2048 will eventually trigger a list debug WARN_ON for the list_del_init() in btrfs_sync_log(). Fixes: d1433debe7f4346cf9fc0dafc71c3137d2a97bc4 Reported-by: Dave Jones <davej@codemonkey.org.uk> cc: stable@vger.kernel.org # 3.15+ Signed-off-by: Chris Mason <clm@fb.com>
Diffstat (limited to 'Documentation/IRQ-affinity.txt')