From: Alejandro Lucero <alejandro.lucero@netronome.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [PATCH v2 1/6] mem: add function for checking memsegs IOVAs addresses
Date: Fri, 5 Oct 2018 13:19:43 +0100 [thread overview]
Message-ID: <CAD+H990W+guFY3ufvnWyJOhZFzKwHUrWddvoyyqedqU8OzcgvQ@mail.gmail.com> (raw)
In-Reply-To: <e0d642fa-837b-02de-7b3e-e3c421a37550@intel.com>
On Fri, Oct 5, 2018 at 1:15 PM Burakov, Anatoly <anatoly.burakov@intel.com>
wrote:
> On 05-Oct-18 1:06 PM, Alejandro Lucero wrote:
> > A device can suffer addressing limitations. This function checks
> > memsegs have iovas within the supported range based on dma mask.
> >
> > PMDs should use this function during initialization if device
> > suffers addressing limitations, returning an error if this function
> > returns memsegs out of range.
> >
> > Another usage is for emulated IOMMU hardware with addressing
> > limitations.
> >
> > It is necessary to save the most restricted dma mask for checking out
> > memory allocated dynamically after initialization.
> >
> > Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com>
> > ---
>
> Reviewed-by: Anatoly Burakov <anatoly.burakov@intel.com>
>
>
Thanks Anatoly.
I have just noticed I did not remove the previous keeping of the dma mask.
I will send another version just with this change and will add you review
if you are happy if I do so.
> --
> Thanks,
> Anatoly
>
next prev parent reply other threads:[~2018-10-05 12:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 12:06 [PATCH v2 0/6] use IOVAs check based on DMA mask Alejandro Lucero
2018-10-05 12:06 ` [PATCH v2 1/6] mem: add function for checking memsegs IOVAs addresses Alejandro Lucero
2018-10-05 12:15 ` Burakov, Anatoly
2018-10-05 12:19 ` Alejandro Lucero [this message]
2018-10-05 12:20 ` Burakov, Anatoly
2018-10-05 12:06 ` [PATCH v2 2/6] mem: use address hint for mapping hugepages Alejandro Lucero
2018-10-05 12:16 ` Burakov, Anatoly
2018-10-05 12:06 ` [PATCH v2 3/6] bus/pci: check iommu addressing limitation just once Alejandro Lucero
2018-10-05 12:16 ` Burakov, Anatoly
2018-10-05 12:06 ` [PATCH v2 4/6] bus/pci: use IOVAs dmak mask check when setting IOVA mode Alejandro Lucero
2018-10-05 12:18 ` Burakov, Anatoly
2018-10-05 12:06 ` [PATCH v2 5/6] net/nfp: check hugepages IOVAs based on DMA mask Alejandro Lucero
2018-10-05 12:06 ` [PATCH v2 6/6] net/nfp: support IOVA VA mode Alejandro Lucero
-- strict thread matches above, loose matches on Subject: below --
2018-07-03 12:09 [PATCH v2 0/6] use IOVAs check based on DMA mask Alejandro Lucero
2018-07-03 12:09 ` [PATCH v2 1/6] mem: add function for checking memsegs IOVAs addresses Alejandro Lucero
2018-07-03 12:37 ` 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+H990W+guFY3ufvnWyJOhZFzKwHUrWddvoyyqedqU8OzcgvQ@mail.gmail.com \
--to=alejandro.lucero@netronome.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.