From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 85E5AA10DA for ; Wed, 31 Jul 2019 11:29:26 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id E87661C0C4; Wed, 31 Jul 2019 11:29:24 +0200 (CEST) Received: from mail-ua1-f67.google.com (mail-ua1-f67.google.com [209.85.222.67]) by dpdk.org (Postfix) with ESMTP id C51AE1C0C3 for ; Wed, 31 Jul 2019 11:29:22 +0200 (CEST) Received: by mail-ua1-f67.google.com with SMTP id s4so26691393uad.7 for ; Wed, 31 Jul 2019 02:29:22 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=YKO5krONDuM28i8qLQFCybLFEwDmZ16TuVp7nvVwPWg=; b=UEnR9K08zSPAwG0vkIPWVwbLXX97Wb1MXe9a6mp28qo9tbX7U6XbEq0UTcfPZ2pR8M SPXydz+dms2CecR1YAnAYuag24cf9GiymrQHZWLLKTtMWMIyAeHWiKl6Lp7csRjndErF /suD/TAjeyQp2XmTVfaXP8scfXR7ryC42cFkKqLIgeygkiCbrMxWf65nN53V4hvrIRYs bCH/TjeGyh3zQIYax7sQyi/hGz9nhMl/dCre0b8YPJtqeQ9jf4d8W6dpl5PuPZwGvqZO yc2CNmOMAyAD+cPrQE/Jm4XSCpt2FqGL1sA+i2PW9kygvzReOkIs+ENVFL0Tf85osME7 IMSQ== X-Gm-Message-State: APjAAAXmYdFl00zbDWLZBDQyiQVpPz9LM+hKlYPLr3qP/fgfdFKoWrQ7 mVyuFd+VcRPwXbh7HpkBWGGtAGlxQfio8pDu3wKGwQ== X-Google-Smtp-Source: APXvYqx7JZFp4NMd6UGRjTl5GrJvpdlEwx6/Q1u43VskH7UR2uBw1Y4f1hbe0MoZgmHzBM/Rmj3kpLiavJkXQZkKhQM= X-Received: by 2002:ab0:3003:: with SMTP id f3mr16531624ual.86.1564565362170; Wed, 31 Jul 2019 02:29:22 -0700 (PDT) MIME-Version: 1.0 References: <20190731033523.2482-1-tyos@jp.ibm.com> In-Reply-To: <20190731033523.2482-1-tyos@jp.ibm.com> From: David Marchand Date: Wed, 31 Jul 2019 11:29:11 +0200 Message-ID: To: Takeshi Yoshimura Cc: dev Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in ppc X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Wed, Jul 31, 2019 at 5:36 AM Takeshi Yoshimura wrote: > > Commit b76fafb174d2 ("eal: fix IOVA mode selection as VA for PCI > drivers") breaks ppc apps with no IOVA configs (or RTE_IOVA_DC) > because of the inconsistency of user's request and the result of > device capability for IOVA mode. I updated the code to force IOVA as > PA in ppc as before because current ppc driver does not support VA > mode. What is the "ppc driver" you are referring to? Do you mean the vfio implementation for ppc? > > Theoretically, ppc can support VA mode, but I suspect that ppc with > VA mode may have performance issues to create a big DMA window > (VA often uses higher addresses than PA). So, I didn't change the > code to check device capability in ppc. Sorry, I am confused. Is VA mode not working at all? or is it a performance issue? -- David Marchand