From: Harold Huang <baymaxhuang@gmail.com>
To: dev@dpdk.org
Cc: maxime.coquelin@redhat.com, chenbo.xia@intel.com
Subject: Fwd: [PATCH v2] net/virtio: unregister virtio user memory event to fix memory leak problem
Date: Mon, 20 Dec 2021 22:08:21 +0800 [thread overview]
Message-ID: <CAHJXk3aL-Ejj=uy5wE7Jv7x4zE6_0Hm7re-fhoabbq_NkRH2iw@mail.gmail.com> (raw)
In-Reply-To: <20211220124929.1309369-1-baymaxhuang@gmail.com>
The problem which this patch wants to solve can be reproduced via ovs 2.16:
1. add a port with an invalid speed parameter:
ovs-vsctl add-port ovs-br0 virtiouser0 -- set Interface virtiouser0
type=dpdk options:dpdk-devargs=virtio_user0,path=/dev/vhost-net,queue_size=1024,queues=1,speed=1000
2. delete the failed virtiouser0 port:
ovs-vsctl del-port virtiouser0
3. add a new port with valid parameters:
ovs-vsctl add-port ovs-br0 virtiouser0 -- set Interface virtiouser0
type=dpdk options:dpdk-devargs=virtio_user0,path=/dev/vhost-net,queue_size=1024,queues=1
The newly added port is always failed because of an existing memory event error.
next prev parent reply other threads:[~2021-12-20 14:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 12:41 [PATCH] net/virtio: unregister virtio user memery " Harold Huang
2021-12-20 12:49 ` [PATCH v2] net/virtio: unregister virtio user memory " Harold Huang
2021-12-20 14:08 ` Harold Huang [this message]
2021-12-22 8:33 ` [PATCH v3] net/virtio: fix unregister virtio user memory event cb problem Harold Huang
2021-12-23 4:42 ` [PATCH] net/virtio: fix unreleased resource when creating virtio user dev is failed Harold Huang
2022-01-14 7:48 ` Xia, Chenbo
2022-01-27 5:23 ` Xia, Chenbo
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='CAHJXk3aL-Ejj=uy5wE7Jv7x4zE6_0Hm7re-fhoabbq_NkRH2iw@mail.gmail.com' \
--to=baymaxhuang@gmail.com \
--cc=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
/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).