From: Yuanhan Liu <yliu@fridaylinux.org>
To: Junjie Chen <junjie.j.chen@intel.com>
Cc: maxime.coquelin@redhat.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] vhost: do deep copy while reallocate vq
Date: Wed, 17 Jan 2018 22:46:21 +0800 [thread overview]
Message-ID: <20180117143708.GV29540@yliu-mob> (raw)
In-Reply-To: <1516015939-11266-1-git-send-email-junjie.j.chen@intel.com>
On Mon, Jan 15, 2018 at 06:32:19AM -0500, Junjie Chen wrote:
> When vhost reallocate dev and vq for NUMA enabled case, it doesn't perform
> deep copy, which lead to 1) zmbuf list not valid 2) remote memory access.
> This patch is to re-initlize the zmbuf list and also do the deep copy.
>
> Signed-off-by: Junjie Chen <junjie.j.chen@intel.com>
> ---
Applied to dpdk-next-virtio.
Thanks.
--yliu
prev parent reply other threads:[~2018-01-17 14:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 11:32 Junjie Chen
2018-01-15 9:05 ` Yang, Zhiyong
2018-01-15 9:14 ` Chen, Junjie J
2018-01-16 0:57 ` Yang, Zhiyong
2018-01-16 7:38 ` Chen, Junjie J
2018-01-17 1:36 ` Yang, Zhiyong
2018-01-16 8:54 ` Maxime Coquelin
2018-01-17 14:46 ` Yuanhan Liu [this message]
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=20180117143708.GV29540@yliu-mob \
--to=yliu@fridaylinux.org \
--cc=dev@dpdk.org \
--cc=junjie.j.chen@intel.com \
--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).