summaryrefslogtreecommitdiffstats
path: root/usr.sbin/bhyve
diff options
context:
space:
mode:
authorgrehan <grehan@FreeBSD.org>2015-05-21 04:19:22 +0000
committergrehan <grehan@FreeBSD.org>2015-05-21 04:19:22 +0000
commit5432c8344b04cadeb9dd069993e62c1a8ec37edc (patch)
tree08ba453694a41f97e867d89487d114e2afa0af63 /usr.sbin/bhyve
parent2ad178c529bedbff2f435e1d5cd8de18fac3ad3a (diff)
downloadFreeBSD-src-5432c8344b04cadeb9dd069993e62c1a8ec37edc.zip
FreeBSD-src-5432c8344b04cadeb9dd069993e62c1a8ec37edc.tar.gz
Temporarily revert r282922 which bumped the max descriptors.
While there is no issued with the number of descriptors in a virtio indirect descriptor, it's a guest's choice as to whether indirect descriptors are used. For the case where they aren't, the virtio block ring size is still 64 which is less than the now reported max_segs of 67. This results in an assertion in recent Linux guests even though it was benign since they were using indirect descs. The intertwined relationship between virtio ring size, max seg size and blockif queue size will be addressed in an upcoming commit, at which point the max descriptors will again be bumped up to 67.
Diffstat (limited to 'usr.sbin/bhyve')
-rw-r--r--usr.sbin/bhyve/block_if.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/usr.sbin/bhyve/block_if.h b/usr.sbin/bhyve/block_if.h
index b1849a6..8e63407 100644
--- a/usr.sbin/bhyve/block_if.h
+++ b/usr.sbin/bhyve/block_if.h
@@ -39,7 +39,7 @@
#include <sys/uio.h>
#include <sys/unistd.h>
-#define BLOCKIF_IOV_MAX 67 /* not practical to be IOV_MAX */
+#define BLOCKIF_IOV_MAX 33 /* not practical to be IOV_MAX */
struct blockif_req {
struct iovec br_iov[BLOCKIF_IOV_MAX];
OpenPOWER on IntegriCloud