From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
dev@dpdk.org, tiwei.bie@intel.com, yliu@fridaylinux.org,
jfreimann@redhat.com, jianfeng.tan@intel.com
Cc: stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v4 0/2] vhost: IOTLB fixes
Date: Mon, 5 Feb 2018 17:44:47 +0000 [thread overview]
Message-ID: <e73be3f7-b88e-ae7e-4ecd-e47d5c38193d@intel.com> (raw)
In-Reply-To: <20180205150457.15543-1-maxime.coquelin@redhat.com>
On 2/5/2018 3:04 PM, Maxime Coquelin wrote:
> First patch of the series fixes OOM handling from the IOTLB
> mempool, the second one removes pending IOTLB entry when the
> IOTLB miss request sending failed.
>
> Changes since v3:
> -----------------
> - Fix 32bits compilation issue in error message in patch 2 (Ferruh)
>
> Changes since v2:
> -----------------
> - patch 2: Fix error message with correct IOVA
>
> Changes since v1:
> -----------------
> - Make log levels consistent (Tiwei)
> - Remove pending IOTLB entry of miss request seding failed (Tiwei)
>
> Maxime Coquelin (2):
> vhost: fix iotlb pool out-of-memory handling
> vhost: remove pending IOTLB entry if IOTLB MISS request sending failed
Series applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-02-05 17:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 15:04 Maxime Coquelin
2018-02-05 15:04 ` [dpdk-dev] [PATCH v4 1/2] vhost: fix iotlb pool out-of-memory handling Maxime Coquelin
2018-02-05 15:04 ` [dpdk-dev] [PATCH v4 2/2] vhost: remove pending IOTLB entry if IOTLB MISS request sending failed Maxime Coquelin
2018-02-05 17:44 ` Ferruh Yigit [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=e73be3f7-b88e-ae7e-4ecd-e47d5c38193d@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=jfreimann@redhat.com \
--cc=jianfeng.tan@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=stable@dpdk.org \
--cc=tiwei.bie@intel.com \
--cc=yliu@fridaylinux.org \
/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).