From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by dpdk.org (Postfix) with ESMTP id 6D9929597 for ; Wed, 21 Oct 2015 17:26:20 +0200 (CEST) Received: by wicll6 with SMTP id ll6so96364835wic.0 for ; Wed, 21 Oct 2015 08:26:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type; bh=mhHTZoMhqbizblHYEptzz9zvhB17OQ893FlF72Yop9M=; b=f/04P7H9RQkqOpNM7YmNWXcPh5jM5VsnGLPkbzTkqnLObwhCfU1wus1cU/RPD1zxOp 6C4NUeD/nkgeLA5mEW+XzcrhvOGajdiQqsbI72UOKVAvmKt5Q11TuH70EwQVZYGNuY7j AtRCBP6fkRfy2cUS8ACKN8EUsUYnCH+0dWxXkKLL7lnmm9zBm6YSU5zRw7AFYRlfcJYJ K/W7ahZKs+L/WNNOd6KFDhvXTvnw1t+0faDDXwjQZbMIl3M5gv4ymXBIjsIhWe1M0ZDC ft4SfFjQbi8T9cZGaDipzsqQNkgp8oBILGrPumP7ghZyVAGEtJEHw6oqlXq6gSwT94MG Bs6w== X-Gm-Message-State: ALoCoQlVTYXbid4dJY/w1yWfGOYXih/fryq8GcZ+jEznnW+gReNZ6chKY2BVV254jebXuZK1qjj1 X-Received: by 10.194.133.129 with SMTP id pc1mr11649640wjb.148.1445441180209; Wed, 21 Oct 2015 08:26:20 -0700 (PDT) Received: from xps13.localnet (guy78-3-82-239-227-177.fbx.proxad.net. [82.239.227.177]) by smtp.gmail.com with ESMTPSA id ly4sm11053894wjb.4.2015.10.21.08.26.18 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 21 Oct 2015 08:26:19 -0700 (PDT) From: Thomas Monjalon To: Alejandro Lucero Date: Wed, 21 Oct 2015 17:25:14 +0200 Message-ID: <2304404.uKjJZErY2S@xps13> Organization: 6WIND User-Agent: KMail/4.14.10 (Linux/4.1.6-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: References: <1444992324-5504-1-git-send-email-alejandro.lucero@netronome.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH v3 2/4] nfp-uio: new uio driver for netronome nfp6000 card X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Oct 2015 15:26:20 -0000 2015-10-21 15:39, Alejandro Lucero: > On Wed, Oct 21, 2015 at 6:24 AM, David Marchand > wrote: > > Please, can you elaborate on the need for (yet another) uio driver, rather > > than make igb_uio work with your hardware ? [...] > I have been looking at the possibility of getting rid of nfp_uio. The fact > is our PMD can work without it, both for the PF and VF (not the PMD version > already submitted but one under development). The PF support requires not > using UIO at all, because the device is attached to the BSP driver. The > only problem with this approach is we do not have support for interrupts, > what is not critical (I can see other PMDs not having support for Link > Status Changes) but we do not like it as programs can register callbacks > for these interrupts which would not work at all. > > Interrupt support could be implemented in the BSP, doing the same UIO or > VFIO do, but this will require (minor) changes to DPDK for having another > intr_handle (not UIO, not VFIO). I do not know if other PMDs could also > make use of such a change but I guess that would help to accept those > changes. We are going to have an external handler (used for mlx5): http://dpdk.org/ml/archives/dev/2015-October/024678.html Problem solved :) Is it possible to rework your PMD without nfp-uio? Thanks