From: John Fastabend <john.fastabend@gmail.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: daniel@iogearbox.net, eric.dumazet@gmail.com, kubakici@wp.pl,
shm@cumulusnetworks.com, davem@davemloft.net,
alexei.starovoitov@gmail.com, netdev@vger.kernel.org,
bblanco@plumgrid.com, john.r.fastabend@intel.com,
brouer@redhat.com, tgraf@suug.ch
Subject: Re: [net-next PATCH v2 3/5] virtio_net: Add XDP support
Date: Mon, 28 Nov 2016 15:26:53 -0800 [thread overview]
Message-ID: <583CBD3D.1080808@gmail.com> (raw)
In-Reply-To: <20161128060446-mutt-send-email-mst@kernel.org>
[...]
>> Perfect! hacking qemu for testing is no problem this helps a lot thanks
>> and saves me time trying to figure out how to get qemu to do this.
>
> Pls note I didn't try this at all, so might not work, but should
> give you the idea.
>
>>>
>>> diff --git a/hw/net/virtio-net.c b/hw/net/virtio-net.c
>>> index b68c69d..4866144 100644
>>> --- a/hw/net/virtio-net.c
>>> +++ b/hw/net/virtio-net.c
>>> @@ -1164,6 +1164,7 @@ static ssize_t virtio_net_receive(NetClientState *nc, const uint8_t *buf, size_t
>>> offset = n->host_hdr_len;
>>> total += n->guest_hdr_len;
>>> guest_offset = n->guest_hdr_len;
>>> + continue;
>>> } else {
>>> guest_offset = 0;
>>> }
>>>
>>>
>>>
>>> here's one that should cap the 1st s/g to 100 bytes:
>>>
>>>
>>> diff --git a/hw/net/virtio-net.c b/hw/net/virtio-net.c
>>> index b68c69d..7943004 100644
>>> --- a/hw/net/virtio-net.c
>>> +++ b/hw/net/virtio-net.c
>>> @@ -1164,6 +1164,7 @@ static ssize_t virtio_net_receive(NetClientState *nc, const uint8_t *buf, size_t
>>> offset = n->host_hdr_len;
>>> total += n->guest_hdr_len;
>>> guest_offset = n->guest_hdr_len;
>>> + sg.iov_len = MIN(sg.iov_len, 100);
>>> } else {
>>> guest_offset = 0;
>>> }
>>>
Here is the patch I went with, I'm using vhost=on:
--- a/drivers/vhost/vhost.c
+++ b/drivers/vhost/vhost.c
@@ -1777,7 +1777,8 @@ static int translate_desc(struct vhost_virtqueue
*vq, u64
_iov = iov + ret;
size = node->size - addr + node->start;
- _iov->iov_len = min((u64)len - s, size);
+ printk("%s: build 100 length headers!\n", __func__);
+ _iov->iov_len = min((u64)len - s, (u64)100);//size);
_iov->iov_base = (void __user *)(unsigned long)
(node->userspace_addr + addr - node->start);
s += size;
This seems to do the trick and with 100 I can use 'ping -s' to generate
as many bufs is needed up to MTU. The patch I have seems to be working
fine I'll let it run a bit and test it with some real traffic (not just
ping) then push out a v3 assuming I don't find any issues.
Thanks,
John
next prev parent reply other threads:[~2016-11-28 23:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-20 2:49 [net-next PATCH v2 0/5] XDP for virtio_net John Fastabend
2016-11-20 2:49 ` [net-next PATCH v2 1/5] net: virtio dynamically disable/enable LRO John Fastabend
2016-11-21 23:23 ` Michael S. Tsirkin
2016-11-22 8:16 ` John Fastabend
2016-11-20 2:50 ` [net-next PATCH v2 2/5] net: xdp: add invalid buffer warning John Fastabend
2016-11-20 2:50 ` [net-next PATCH v2 3/5] virtio_net: Add XDP support John Fastabend
2016-11-21 23:20 ` Michael S. Tsirkin
2016-11-22 8:27 ` John Fastabend
2016-11-22 14:58 ` Michael S. Tsirkin
2016-11-25 21:24 ` John Fastabend
2016-11-28 3:36 ` Michael S. Tsirkin
2016-11-28 3:56 ` John Fastabend
2016-11-28 4:07 ` Michael S. Tsirkin
2016-11-28 23:26 ` John Fastabend [this message]
2016-11-20 2:51 ` [net-next PATCH v2 4/5] virtio_net: add dedicated XDP transmit queues John Fastabend
2016-11-21 11:45 ` Daniel Borkmann
2016-11-21 15:56 ` John Fastabend
2016-11-21 23:13 ` Michael S. Tsirkin
2016-11-22 8:17 ` John Fastabend
2016-11-22 14:59 ` Michael S. Tsirkin
2016-11-20 2:51 ` [net-next PATCH v2 5/5] virtio_net: add XDP_TX support John Fastabend
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=583CBD3D.1080808@gmail.com \
--to=john.fastabend@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=bblanco@plumgrid.com \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=john.r.fastabend@intel.com \
--cc=kubakici@wp.pl \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=shm@cumulusnetworks.com \
--cc=tgraf@suug.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).