From: Alejandro Lucero <alejandro.lucero@netronome.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev <dev@dpdk.org>, "Burakov, Anatoly" <anatoly.burakov@intel.com>
Subject: Re: [dpdk-dev] [PATCH v4 0/5] use IOVAs check based on DMA mask
Date: Fri, 27 Jul 2018 09:03:44 +0200 [thread overview]
Message-ID: <CAD+H990j8iynw3g06wEOWZESwGbyS_nV8ZLYuJG3ZDpZqD3bbQ@mail.gmail.com> (raw)
In-Reply-To: <3971346.ugMje1iWhR@xps>
Hi Thomas,
Why deferred? This patch is only to be applied to 17.11.3. Because the
changes the memory code has gone through the last months, the same fix will
be different for newer versions.
I'm working on it but waiting all the current patches from Anatoly being
accepted for creating the final patchset.
On Thu, Jul 26, 2018 at 5:41 PM, Thomas Monjalon <thomas@monjalon.net>
wrote:
> 10/07/2018 19:25, Alejandro Lucero:
> > This patchset applies on 17.11.3.
> >
> > Similar changes will be submitted to main DPDK branch soon.
>
> In patchwork, I mark this patchset as Deferred,
> waiting a new version for 18.11.
>
>
>
next prev parent reply other threads:[~2018-07-27 7:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 17:25 Alejandro Lucero
2018-07-10 17:25 ` [dpdk-dev] [PATCH v4 1/5] mem: add function for checking memsegs IOVAs addresses Alejandro Lucero
2018-07-11 10:12 ` [dpdk-dev] [dpdk-stable] " Eelco Chaudron
2018-07-10 17:25 ` [dpdk-dev] [PATCH v4 2/5] bus/pci: use IOVAs check when setting IOVA mode Alejandro Lucero
2018-07-11 10:18 ` [dpdk-dev] [dpdk-stable] " Eelco Chaudron
2018-07-11 10:41 ` Burakov, Anatoly
2018-07-10 17:25 ` [dpdk-dev] [PATCH v4 3/5] mem: use address hint for mapping hugepages Alejandro Lucero
2018-07-10 17:25 ` [dpdk-dev] [PATCH v4 4/5] net/nfp: check hugepages IOVAs based on DMA mask Alejandro Lucero
2018-07-10 17:25 ` [dpdk-dev] [PATCH v4 5/5] net/nfp: support IOVA VA mode Alejandro Lucero
2018-07-26 15:41 ` [dpdk-dev] [PATCH v4 0/5] use IOVAs check based on DMA mask Thomas Monjalon
2018-07-27 7:03 ` Alejandro Lucero [this message]
2018-07-27 8:01 ` Thomas Monjalon
2018-07-27 8:22 ` Alejandro Lucero
2018-07-27 8:52 ` Thomas Monjalon
2018-07-27 8:59 ` Alejandro Lucero
2018-07-27 8:54 ` Burakov, Anatoly
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=CAD+H990j8iynw3g06wEOWZESwGbyS_nV8ZLYuJG3ZDpZqD3bbQ@mail.gmail.com \
--to=alejandro.lucero@netronome.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).