diff options
| author | Jan Beulich <[email protected]> | 2017-01-23 08:11:37 -0700 |
|---|---|---|
| committer | Konrad Rzeszutek Wilk <[email protected]> | 2017-01-23 13:27:42 -0500 |
| commit | 3b4f18843e511193e7eb616710e838f5852e661d (patch) | |
| tree | abf5739ec8edad0a94594aa2148d132ab2f20867 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | b32728ffef7f233dbdabb3f11814bdf692aaf501 (diff) | |
xen-blkfront: correct maximum segment accounting
Making use of "max_indirect_segments=" has issues:
- blkfront_setup_indirect() may end up with zero psegs when PAGE_SIZE
is sufficiently much larger than XEN_PAGE_SIZE
- the variable driven by the command line option
(xen_blkif_max_segments) has a somewhat different purpose, and hence
should namely never end up being zero
- as long as the specified value is lower than the legacy default,
we better don't use indirect segments at all (or we'd in fact lower
throughput)
Signed-off-by: Jan Beulich <[email protected]>
Signed-off-by: Konrad Rzeszutek Wilk <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions