[lkml]   [2010]   [Sep]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [RFC PATCH 2/2] macvtap: TX zero copy between guest and host kernel
    On Tue, 2010-09-14 at 20:27 +0200, Michael S. Tsirkin wrote:
    > As others said, the harder issues for TX are in determining that it's
    > safe
    > to unpin the memory, and how much memory is it safe to pin to beging
    > with. For RX we have some more complexity.

    I think unpin the memory is in kfree_skb() whenever the last reference
    is gone for TX. What we discussed about here is when/how vhost get
    notified to update ring buffer descriptors. Do I misunderstand something

    > Well it's up to you of course, but this is not what I would try:
    > if you look at the
    > patchset vhost changes is not the largest part of it,
    > so this sounds a bit like effort duplication.
    > TX only is also much less interesting than full zero copy.

    It's not true. From the performance, TX only has gained big improvement.
    We need to identify how much gain from TX zero copy, and how much gain
    from RX zero copy.

    > I think that you should be able to simply combine
    > the two drivers together, add an ioctl to
    > enable/disable zero copy mode of operation.

    That could work. But what's the purpose to have two drivers if one
    driver can handle it?


     \ /
      Last update: 2010-09-14 20:51    [W:0.021 / U:3.688 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site