Date: Tue, 22 May 2018 12:59:24 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 228335] [patch] virtio indirect descriptors should use contiguous memory Message-ID: <bug-228335-27103-QfHTvNNxGf@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-228335-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-228335-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228335 --- Comment #2 from Nick Reilly <nreilly@blackberry.com> --- I'm actually taking the FreeBSD kernel networking components and running th= em in user space on another OS. I've got the kernel malloc(9) macro'd through = to the normal system malloc() and on this OS the allocations are not physically contiguous. I get an address that is close to the end of one virtual page a= nd it spans on to the next virtual page, however these virtual pages are not physically contiguous. I don't see anything on the man page for malloc(9) that specifies that it allocates from within a single page for smaller allocations. I agree that it will because of the use of the UMA layer, but I don't see it as required. This isn't a showstopper for me, I can work around it and others are unlike= ly to run in to it. If you just want to defer this and have it come out in the switch to bus_dma(9) that's OK. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-228335-27103-QfHTvNNxGf>