DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Eugenio Pérez" <eperezma@redhat.com>
To: dev@dpdk.org
Cc: Adrian Moreno Zapata <amorenoz@redhat.com>,
	Chenbo Xia <chenbo.xia@intel.com>,
	Zhihong Wang <zhihong.wang@intel.com>,
	Jens Freimann <jfreimann@redhat.com>,
	stable@dpdk.org, Maxime Coquelin <maxime.coquelin@redhat.com>,
	Kevin Traynor <ktraynor@redhat.com>
Subject: [dpdk-dev] [PATCH v2 0/1] vhost: Make iotlb mempool not single-consumer
Date: Mon, 31 Aug 2020 09:59:21 +0200	[thread overview]
Message-ID: <20200831075922.17970-1-eperezma@redhat.com> (raw)
In-Reply-To: <20200810141103.8015-1-eperezma@redhat.com>

Bugzilla bug: 523

This behavior is only observed on packed vq + virtio-net kernel driver in the
guest, so we could make the single-consumer flag optional. However, I have not
found why I cannot see the issue in split, so the safer option is to never set
it.

Any comments?

Thanks!

v2: Modify commit message to not to include all trace and commands.

Eugenio Pérez (1):
  vhost: fix iotlb mempool single-consumer flag

 lib/librte_vhost/iotlb.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

-- 
2.18.1


  parent reply	other threads:[~2020-08-31  7:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-10 14:11 [dpdk-dev] [PATCH 0/1] vhost: fix iotlb mempool single-consumer flag Eugenio Pérez
2020-08-10 14:11 ` [dpdk-dev] [PATCH 1/1] " Eugenio Pérez
2020-08-25  9:17   ` Kevin Traynor
2020-08-26  6:28   ` Xia, Chenbo
2020-08-26 12:50     ` Eugenio Perez Martin
2020-08-27  1:20       ` Xia, Chenbo
2020-08-28 18:40   ` Jens Freimann
2020-08-18 14:21 ` [dpdk-dev] [PATCH 0/1] " Eugenio Perez Martin
2020-08-31  7:59 ` Eugenio Pérez [this message]
2020-08-31  7:59   ` [dpdk-dev] [PATCH v2 1/1] " Eugenio Pérez
2020-08-31 10:21     ` Xia, Chenbo
2020-09-18  9:49     ` Maxime Coquelin
2020-09-18 12:29     ` Maxime Coquelin

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=20200831075922.17970-1-eperezma@redhat.com \
    --to=eperezma@redhat.com \
    --cc=amorenoz@redhat.com \
    --cc=chenbo.xia@intel.com \
    --cc=dev@dpdk.org \
    --cc=jfreimann@redhat.com \
    --cc=ktraynor@redhat.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=stable@dpdk.org \
    --cc=zhihong.wang@intel.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).