Ethtool can separately turn off tso
$ ethtool -K vethXXX tso off
$ ethtool -K vethXXX tx off will turn off tx checksum, tso, sg.
TSO depends on tx checksum and sg, so if you just want to turn off tso and
keep tx chechsum on, you can do it in the below way.
$ ethtool -K vethXXX tx on
$ ethtool
送: William Tu ; Yi Yang (杨�D)-云服务集团
; d...@openvswitch.org; i.maxim...@ovn.org
主题: Re: Re：[ovs-dev] Re: Re: [PATCH v4 0/3] Add support for TSO with DPDK
On Tue, Mar 10, 2020 at 04:08:43PM +0800, txfh2007 wrote:
> Hi Flavio and all:
>
> Is there a way to support software TSO for DP
Ilya, raw socket for the interface type of which is "system" has been set to
non-block mode, can you explain which syscall will lead to sleep? Yes, pmd
thread will consume CPU resource even if it has nothing to do, but all the
type=dpdk ports are handled by pmd thread, here we just let system
In the same environment, but I used tap but not veth, retr number is 0 for
the case without this patch (of course, I applied Flavio's tap enable patch)
vagrant@ubuntu1804:~$ sudo ./run-iperf3.sh
Connecting to host 10.15.1.3, port 5201
[ 4] local 10.15.1.2 port 54572 connected to 10.15.1.3 port
William, which kernel version did you use to test for this patch? I don't
want to build a kernel if Ubuntu 16.04 kernel can work.
-邮件原件-
发件人: dev [mailto:ovs-dev-boun...@openvswitch.org] 代表 William Tu
发送时间: 2020年2月21日 3:00
收件人: d...@openvswitch.org
抄送: f...@sysclose.org;
Hi, Flavio
I find this tso feature doesn't work normally on my Ubuntu 16.04, here is my
result. My kernel version is
$ uname -a
Linux cmp008 4.15.0-55-generic #60~16.04.2-Ubuntu SMP Thu Jul 4 09:03:09 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
$
$ ./run-iperf3.sh
Connecting to host 10.15.1.3,
Ilya, thank you so much for your comments, I'll fix them in next version.
For TSO support, this patch can work from functionality, but I checked
tpacket_v3 kernel code, I don't think tpacket_v3 kernel part can support it,
my test result also showed very bad performance if userspace-tso-enable is
ALL);
+sll.sll_protocol = (OVS_FORCE ovs_be16) htons(ETH_P_ALL);
if (bind(rx->fd, (struct sockaddr *) , sizeof sll) < 0) {
error = errno;
VLOG_ERR("%s: failed to bind raw socket (%s)",
-邮件原件-
发件人: Yi Yang (杨�D)-云服务集团
发送时间: 2020年2月1
[mailto:yang_y...@126.com]
发送时间: 2020年2月11日 18:22
收件人: ovs-dev@openvswitch.org
抄送: b...@ovn.org; ian.sto...@intel.com; Yi Yang (杨�D)-云服务集团
; yang_y...@163.com
主题: [PATCH v3] Use TPACKET_V3 to accelerate veth for userspace datapath
From: Yi Yang
We can avoid high system call overhead by using
interface, it can't support TSO, do you Redhat guys have plan to
enable it on kernel side.
-邮件原件-
发件人: Flavio Leitner [mailto:f...@sysclose.org]
发送时间: 2020年2月4日 5:46
收件人: d...@openvswitch.org
抄送: Stokes Ian ; Loftus Ciara
; Ilya Maximets ; Yi Yang (杨
�D)-云服务集团 ; txfh2007 ; Ben
Pfaff ; Flavio L
tween your 4.00 Gbps and 1.98Gbps?
>
>William
-邮件原件-----
发件人: Yi Yang (杨�D)-云服务集团
发送时间: 2020年2月3日 12:06
收件人: 'u9012...@gmail.com' ; 'b...@ovn.org'
; 'yang_y...@163.com'
抄送: 'ovs-dev@openvswitch.org' ;
'ian.sto...@intel.com'
主题: 答复: [PATCH] Use TPACKET_V1/V2/V3 to accelerate veth for DPD
e: Fri Aug 19 10:18:16 2011 +
>
>af-packet: TPACKET_V3 flexible buffer implementation.
>
>and based on OVS release
>http://docs.openvswitch.org/en/latest/faq/releases/
>after OVS 2.12, the minimum kernel requirement is 3.10.
>
>Regards,
>William
-邮件原件-
@openvswitch.org; ian.sto...@intel.com; Yi Yang (杨�D)-云服务集
团
主题: Re: [PATCH] Use TPACKET_V1/V2/V3 to accelerate veth for DPDK datapath
On Tue, Jan 21, 2020 at 02:49:47AM -0500, yang_y...@163.com wrote:
> From: Yi Yang
>
> We can avoid high system call overhead by using TPACKET_V1/V2/V3 a
New Year long holiday, so next version post will be sent out after one week
at least. Welcome more comments from other folks.
-邮件原件-
发件人: Ben Pfaff [mailto:b...@ovn.org]
发送时间: 2020年1月22日 3:26
收件人: yang_y...@163.com
抄送: ovs-dev@openvswitch.org; ian.sto...@intel.com; Yi Yang (杨�D)-云服务集
团
主题
iam Tu [mailto:u9012...@gmail.com]
发送时间: 2019年12月21日 1:50
收件人: Ben Pfaff
抄送: d...@openvswitch.org; i.maxim...@ovn.org; Yi Yang (杨�D)-云服务集团
; echau...@redhat.com
主题: Re: [PATCH RFC] WIP: netdev-tpacket: Add AF_PACKET v3 support.
On Thu, Dec 19, 2019 at 08:44:30PM -0800, Ben Pfaff wrote:
> On
Hi, William
What kernel version can support AF_PACKET v3? I can try it with your patch.
-邮件原件-
发件人: William Tu [mailto:u9012...@gmail.com]
发送时间: 2019年12月20日 8:41
收件人: d...@openvswitch.org
抄送: i.maxim...@ovn.org; Yi Yang (杨�D)-云服务集团 ;
b...@ovn.org; echau...@redhat.com
主题: [PATCH RFC] WIP
msgs, n, flags, timeout);
+if (retval >= 0 || errno != ENOSYS) {
+return retval;
+}
+recvmmsg_broken = true;
+errno = save_errno;
+}
-邮件原件-
发件人: Ben Pfaff [mailto:b...@ovn.org]
发送时间: 2019年12月18日 4:39
收件人: d...@openvswitch.org
抄送: Ben Pfaff
ate it with your fix patch and send another version.
-邮件原件-
发件人: Ben Pfaff [mailto:b...@ovn.org]
发送时间: 2019年12月18日 4:14
收件人: yang_y...@163.com
抄送: ovs-dev@openvswitch.org; ian.sto...@intel.com; Yi Yang (杨�D)-云服务集
团
主题: Re: [PATCH] Use batch process recv for tap and raw socket in netdev
datapath
On
William, thank you for your test, it is one of solutions to OVS DPDK issues
in OVS Conference :-), this is a kind of very cheap improving way, the
performance isn't that bad, it is basically acceptable for common use cases
which don't expect high network performance.
-邮件原件-
发件人: dev
Hi, Ilya
Can you explain what kernel limitations are for TCP for veth? I can't
understand why veth has such limitations only for TCP. I saw a veth bug
(https://tech.vijayp.ca/linux-kernel-bug-delivers-corrupt-tcp-ip-data-to-mes
os-kubernetes-docker-containers-4986f88f7a19) but it has been fixed
Hi, folks
We need to do SNAT for many internal IPs by just using several public IPs,
we also need to do DNAT by some other public IPs for exposing webservice,
openflow rules look like the below:
table=0,ip,nw_src=172.17.0.0/16,…,actions=ct(commit,table=0,zone=1,nat(src=
tch, stt,
system, tap, vxlan]
manager_options : []
next_cfg: 46
other_config: {dpdk-init="true", dpdk-socket-mem="4096",
pmd-cpu-mask="0xfe"}
ovs_version : "2.11.1"
ssl : []
statistics : {}
system_type
Hi, all
I’m doing experiments with OVS and OVS DPDK, only one bridge is there,
ports and flows are same for OVS and OVS DPDK, in OVS case, everything works
well, but in OVS DPDK case, iperf udp performance data are very poor, udp
packets are out of order, I have limited MTU and send buffer by
Hi, all
I was told meter only can be specified once, but actually there is such case
existing, i.e. multiple flows share a total bandwidth, but every flow also
has its own bandwidth limit, by two meters, we can not only get every flow
stats but also get total stats, I think this is very
Hi, all
We’re trying OVS DPDK in openstack cloud, but a big warn makes us hesitate.
Floating IP and qrouter use tap interfaces which are attached into br-int,
SNAT also should use similar way, so OVS DPDK will impact on VM network
performance significantly, I believe many cloud providers have
Hi, all
I need to add and delete flows according to user operations, I know
openflowplugin in Opendaylight can do this, but it seems “ovs-ofctl
del-flows” can’t do this way, why can’t cookie value be used to do this
for “ovs-ofctl del-flows”?
sudo ovs-ofctl -Oopenflow13 --strict del-flows
Hi, all
I just use ovs as a static router in my test case, ovs is ran in vagrant VM,
ethernet interfaces uses virtio driver, I create two ovs bridges, each one
adds one ethernet interface, two bridges are connected by patch port, only
default openflow rule is there.
table=0, priority=0
27 matches
Mail list logo
