From: David Marchand <david.marchand@redhat.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev <dev@dpdk.org>, Anatoly Burakov <anatoly.burakov@intel.com>,
Scott Wasson <scott_wasson@affirmednetworks.com>,
dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v2] kni: fix not contiguous FIFO
Date: Fri, 14 Feb 2020 12:30:45 +0100 [thread overview]
Message-ID: <CAJFAV8ypCZ6eXUr48HsNyPEcc+Z7KFQgfFbYnF29Kn5Bf32EtA@mail.gmail.com> (raw)
In-Reply-To: <20200214100052.2795482-1-ferruh.yigit@intel.com>
On Fri, Feb 14, 2020 at 11:01 AM Ferruh Yigit <ferruh.yigit@intel.com> wrote:
>
> From: Scott Wasson <scott_wasson@affirmednetworks.com>
>
> KNI requires FIFO to be physically contiguous, with existing
> 'rte_memzone_reserve()' API this is not guaranteed by default and as a
> result KNI rings and packet delivery may be broken if reserved memory
> is not physically contiguous.
>
> Fixing it by providing 'RTE_MEMZONE_IOVA_CONTIG' flag to ask physically
> contiguous memory.
>
Bugzilla ID: 389
> Fixes: 23fa86e529e4 ("memzone: enable IOVA-contiguous reserving")
> Cc: stable@dpdk.org
>
> Signed-off-by: Scott Wasson <scott_wasson@affirmednetworks.com>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied, thanks.
--
David Marchand
prev parent reply other threads:[~2020-02-14 11:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 19:47 [dpdk-dev] [PATCH] kni: fix bug 389 - Crash in librte_kni driver due to noncontiguous pages Scott Wasson
2020-02-11 9:28 ` Ferruh Yigit
2020-02-11 12:18 ` Burakov, Anatoly
2020-02-11 14:09 ` Ferruh Yigit
2020-02-14 10:00 ` [dpdk-dev] [PATCH v2] kni: fix not contiguous FIFO Ferruh Yigit
2020-02-14 11:30 ` David Marchand [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=CAJFAV8ypCZ6eXUr48HsNyPEcc+Z7KFQgfFbYnF29Kn5Bf32EtA@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=scott_wasson@affirmednetworks.com \
--cc=stable@dpdk.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).