| commit | d8e0420603cf1ce9cb459c00ea0b7337de41b968 | |
| author | Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> | |
| Mon, 9 Feb 2009 20:05:46 +0000 (9 12:05 -0800) | ||
| committer | Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> | |
| Mon, 18 Oct 2010 14:40:28 +0000 (18 10:40 -0400) | ||
| tree | 10294b14b8f0a432763d2b87c38bd41538923d85 | treesnapshot (tar.gz zip) |
| parent | 23ace955c22cb9bdf703e4bdc9bf7379166113cd | commitdiff |
xen: define BIOVEC_PHYS_MERGEABLE()
Impact: allow Xen control of bio merging
When running in Xen domain with device access, we need to make sure
the block subsystem doesn't merge requests across pages which aren't
machine physically contiguous. To do this, we define our own
BIOVEC_PHYS_MERGEABLE. When CONFIG_XEN isn't enabled, or we're not
running in a Xen domain, this has identical behaviour to the normal
implementation. When running under Xen, we also make sure the
underlying machine pages are the same or adjacent.
Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Impact: allow Xen control of bio merging
When running in Xen domain with device access, we need to make sure
the block subsystem doesn't merge requests across pages which aren't
machine physically contiguous. To do this, we define our own
BIOVEC_PHYS_MERGEABLE. When CONFIG_XEN isn't enabled, or we're not
running in a Xen domain, this has identical behaviour to the normal
implementation. When running under Xen, we also make sure the
underlying machine pages are the same or adjacent.
Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
| arch/x86/include/asm/io.h | diffblobblamehistory | |
| drivers/xen/Makefile | diffblobblamehistory | |
| drivers/xen/biomerge.c | [new file with mode: 0644] | blob |