From: Thomas Monjalon <thomas@monjalon.net>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, yuwei1.zhang@intel.com
Subject: Re: [dpdk-dev] [PATCH] memalloc: check for contiguousness in external segments
Date: Sun, 18 Nov 2018 17:21:15 +0100 [thread overview]
Message-ID: <2055442.uj1xbPjuRI@xps> (raw)
In-Reply-To: <8533ab3a49f63e9700764ead8b9147a098911b41.1542204687.git.anatoly.burakov@intel.com>
14/11/2018 15:51, Anatoly Burakov:
> For IOVA as VA mode, we assume that memory is contiguous. However,
> for external segments that assumption may not necessarily hold.
> Fix the code to not assume that external memory segments are
> contiguous even in IOVA as VA mode.
>
> Fixes: 5282bb1c3695 ("mem: allow memseg lists to be marked as external")
>
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
Applied, thanks
prev parent reply other threads:[~2018-11-18 16:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 14:51 Anatoly Burakov
2018-11-14 15:00 ` [dpdk-dev] [PATCH v2] malloc: fix adjacency check to also include segment list Anatoly Burakov
2018-11-14 16:04 ` Burakov, Anatoly
2018-11-18 13:15 ` Thomas Monjalon
2018-11-18 13:05 ` [dpdk-dev] [PATCH] memalloc: check for contiguousness in external segments Thomas Monjalon
2018-11-18 16:21 ` Thomas Monjalon [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=2055442.uj1xbPjuRI@xps \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=yuwei1.zhang@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).