I use it all the time, but I have not updated to a more recent kernel yet. I am
at LinuxCon, so I am unlikely to try it until I get home.
> On Aug 21, 2014, at 2:50 PM, Christopher Covington
> wrote:
>
> Hi Richard,
>
>> On 11/25/2013 10:49 AM, Richard Yao wrote:
>&
On 12/06/2013 06:14 AM, Will Deacon wrote:
> On Wed, Dec 04, 2013 at 08:43:18PM +0000, Richard Yao wrote:
>> The 9p-virtio transport does zero copy on things larger than 1024 bytes
>> in size. It accomplishes this by returning the physical addresses of
>> pages to the virtio-p
ZFS file-based vdevs on virtfs to be used without killing QEMU.
Also, special thanks to both Avi Kivity and Alexander Graf for their
interpretation of QEMU backtraces. Without their guidence, tracking down
this bug would have taken much longer.
Signed-off-by: Richard Yao
---
net/9p
version of this patch to the appropriate subsystem
maintainer(s).
On 11/26/2013 10:38 AM, Richard Yao wrote:
> Christopher,
>
> It sounds like you disabled zero-copy entirely, which is not necessary.
> As far as I recall, loading kernel modules is the only case in which
> val
instead
rework the zero-copy to properly handle valloc() allocated buffers.
Yours truly,
Richard Yao
On 11/26/2013 10:16 AM, Christopher Covington wrote:
> Hi Richard,
>
> On 11/25/2013 04:50 PM, Richard Yao wrote:
>> I figured out the problem. There is zerocopy IO is being done via DMA
I figured out the problem. There is zerocopy IO is being done via DMA to
a buffer allocated with valloc(). Right now, I am running a hack-fix
locally so I can get some other stuff done first. I will propose a
proper fix to the list in a few days.
On 11/25/2013 10:49 AM, Richard Yao wrote:
>
