From: Thomas Monjalon <thomas@monjalon.net>
To: Alejandro Lucero <alejandro.lucero@netronome.com>
Cc: stable@dpdk.org, dev <dev@dpdk.org>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>,
Yongseok Koh <yskoh@mellanox.com>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v4 0/5] use IOVAs check based on DMA mask
Date: Fri, 27 Jul 2018 10:52:32 +0200 [thread overview]
Message-ID: <2271468.kCQjBdv7Zo@xps> (raw)
In-Reply-To: <CAD+H993fgg3Tn7mg52Kn6GSA8xWAin7r=NwKtwRyFbntTOzN9A@mail.gmail.com>
27/07/2018 10:22, Alejandro Lucero:
> Thomas Monjalon <thomas@monjalon.net> wrote:
> > 27/07/2018 09:03, Alejandro Lucero:
> > > 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.
> > > 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.
> >
> > OK, I can change them to "Not Applicable".
> >
> It is not applicable to master but it should for 17.11.3. Adding
> stable@dpdk.org to this thread.
The process is to send the patches to stable@dpdk.org with
[PATCH 17.11] in the subject.
Then it must decided of accepting the exception or not.
> > > I'm working on it but waiting all the current patches from Anatoly being
> > > accepted for creating the final patchset.
> >
> > Is there still some patches which are not applied?
> >
> Uhmm, maybe a patch for 18.11 could be created now. I was thinking about
> these ones:
>
> Support externally allocated memory in DPDK
> Support running DPDK without hugetlbfs mountpoint
>
> But they are not going to be in 18.11, so I will submit the patch asap, but
> I'm afraid it will be for stable 18.11.1
> Next three weeks I'm on PTO, so hopefully I can submit the patch early
> September.
We are not going to apply them to 18.11.1. It should be in 18.11.0.
If you send them really early September, it can be fine.
next prev parent reply other threads:[~2018-07-27 8:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 17:25 [dpdk-stable] " Alejandro Lucero
2018-07-10 17:25 ` [dpdk-stable] [PATCH v4 1/5] mem: add function for checking memsegs IOVAs addresses Alejandro Lucero
2018-07-11 10:12 ` Eelco Chaudron
2018-07-10 17:25 ` [dpdk-stable] [PATCH v4 2/5] bus/pci: use IOVAs check when setting IOVA mode Alejandro Lucero
2018-07-11 10:18 ` Eelco Chaudron
2018-07-11 10:41 ` Burakov, Anatoly
2018-07-10 17:25 ` [dpdk-stable] [PATCH v4 3/5] mem: use address hint for mapping hugepages Alejandro Lucero
2018-07-10 17:25 ` [dpdk-stable] [PATCH v4 4/5] net/nfp: check hugepages IOVAs based on DMA mask Alejandro Lucero
2018-07-10 17:25 ` [dpdk-stable] [PATCH v4 5/5] net/nfp: support IOVA VA mode Alejandro Lucero
[not found] ` <3971346.ugMje1iWhR@xps>
[not found] ` <CAD+H990j8iynw3g06wEOWZESwGbyS_nV8ZLYuJG3ZDpZqD3bbQ@mail.gmail.com>
[not found] ` <1558429.OuX7aYRipb@xps>
2018-07-27 8:22 ` [dpdk-stable] [dpdk-dev] [PATCH v4 0/5] use IOVAs check based on DMA mask Alejandro Lucero
2018-07-27 8:52 ` Thomas Monjalon [this message]
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=2271468.kCQjBdv7Zo@xps \
--to=thomas@monjalon.net \
--cc=alejandro.lucero@netronome.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=yskoh@mellanox.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).