DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Davide Caratti <dcaratti@redhat.com>
Cc: dev@dpdk.org, dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/bnxt: support IOVA VA mode
Date: Tue, 12 Feb 2019 11:01:10 -0800	[thread overview]
Message-ID: <CACZ4nhtxNYpGEXqMz7qqJQ3siKsuFTUEiN9hBT5hNgVoe0gatQ@mail.gmail.com> (raw)
In-Reply-To: <a8073ccaa9cf1c7454bdc061e3a0a95a2f4ac541.1549995965.git.dcaratti@redhat.com>

On Tue, Feb 12, 2019 at 10:30 AM Davide Caratti <dcaratti@redhat.com> wrote:

> Set RTE_PCI_DRV_IOVA_AS_VA in drv_flags: this allows initializing bnxt
> PMD as non-root also on Linux v4.x, where /proc/self/pagemap can't be
> acccessed without CAP_SYS_ADMIN privileges.
>
> Cc: stable@dpdk.org
> Signed-off-by: Davide Caratti <dcaratti@redhat.com>
>
Acked-by: Ajit Khaparde <ajit.khaparde@broadcom.com>


> ---
>  drivers/net/bnxt/bnxt_ethdev.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/bnxt/bnxt_ethdev.c
> b/drivers/net/bnxt/bnxt_ethdev.c
> index 801c6ffad..189527207 100644
> --- a/drivers/net/bnxt/bnxt_ethdev.c
> +++ b/drivers/net/bnxt/bnxt_ethdev.c
> @@ -3548,7 +3548,7 @@ static int bnxt_pci_remove(struct rte_pci_device
> *pci_dev)
>  static struct rte_pci_driver bnxt_rte_pmd = {
>         .id_table = bnxt_pci_id_map,
>         .drv_flags = RTE_PCI_DRV_NEED_MAPPING |
> -               RTE_PCI_DRV_INTR_LSC,
> +               RTE_PCI_DRV_INTR_LSC | RTE_PCI_DRV_IOVA_AS_VA,
>         .probe = bnxt_pci_probe,
>         .remove = bnxt_pci_remove,
>  };
> --
> 2.20.1
>
>

  reply	other threads:[~2019-02-12 19:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-12 18:30 Davide Caratti
2019-02-12 19:01 ` Ajit Khaparde [this message]
2019-02-13 13:29   ` Ferruh Yigit

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=CACZ4nhtxNYpGEXqMz7qqJQ3siKsuFTUEiN9hBT5hNgVoe0gatQ@mail.gmail.com \
    --to=ajit.khaparde@broadcom.com \
    --cc=dcaratti@redhat.com \
    --cc=dev@dpdk.org \
    --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).