From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <wkevils@gmail.com>
Received: from mail-ot0-f169.google.com (mail-ot0-f169.google.com
 [74.125.82.169]) by dpdk.org (Postfix) with ESMTP id 936A51DF8D
 for <dev@dpdk.org>; Mon, 11 Jun 2018 04:02:02 +0200 (CEST)
Received: by mail-ot0-f169.google.com with SMTP id q1-v6so21971573oth.13
 for <dev@dpdk.org>; Sun, 10 Jun 2018 19:02:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
 h=mime-version:from:date:message-id:subject:to;
 bh=1t8HfPA171Ng1zwJTxwp0AcZHFXFhLmZwNPtJS8dSME=;
 b=DcRJfLAPULPnJ+K45FditFVpmW+FB0a1J+4XIXdtXK7/Gkz5K6hwXuleSg5aazRpLB
 2uuKMY7pLw0dz3Kaq/Atd+Ph8L28gkct3miIVAYGB/BoMCIegWEMItZDDWuoJlcmqOD/
 F09zAZNiYIZsmnYW7H/L2CSyhUdT7XgIrzZGU5EIrrMMbgduR0+yXUrwlUWuRpX6ZB8D
 AveWdml0f0Dv/bvEMykmg2cvpFk0weZhjgcJA9mh4rSDy/4ebxiSmAIRGx+0H97J/MT+
 gLc+gcp5/X9GGzCmlG1ISpV/bhcaAe9W7HivdAci5h5WCBilp8l4AkZBeSigiLK2N+hH
 v+qQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
 bh=1t8HfPA171Ng1zwJTxwp0AcZHFXFhLmZwNPtJS8dSME=;
 b=eiqkRKUtuKZCSfoEZdOuzLxyH8uKSvb3/BqlS3obtNwecc0R24aC+HP6HomXaIZKL1
 1Si5253Z6YXZ6KqQRNwyx2mi/wSiYagyRDe/dZtL0eOi6oTdo/9zeHVYJQF0pMSphAa5
 iMIa4MaVfhGCTC31swq3sbEYwHbJdxklo3TpKdXcKTCXzoCTyl3ZA6aSd5ZfYL+eRI1N
 hFx/5Lr4UPhfDsjQ0LSzwefOGdaIIZf3t180FWwluaVEpiklhLP5EoR7a7yCrHeCmoIe
 kraIPXk15BeZ/2/zY0j1lD16/DAENml2dwigL7oDLOJfuh21S+JY5xcR2HEzRyZaX9Dh
 kuyQ==
X-Gm-Message-State: APt69E2AQRUFzcrRp5yl4MnxNlLVObSvAaFZ4mwTpauW7jSxf2tfmyxc
 HC6LicV3bowsWY13S5WzoQgR7DnEi0MVJjbDeAiyeg==
X-Google-Smtp-Source: ADUXVKLOqSkMMMTeC46CtOeq1mDlhpJnz81o1miehzLeFcEbYFQaN6SCvyAy1iZEjVJwMW5ft3oWUlG/ITRMgQHWi2Y=
X-Received: by 2002:a9d:fe5:: with SMTP id
 m34-v6mr8482238otd.372.1528682521894; 
 Sun, 10 Jun 2018 19:02:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4a:1587:0:0:0:0:0 with HTTP; Sun, 10 Jun 2018 19:02:01
 -0700 (PDT)
From: Kevin Wilson <wkevils@gmail.com>
Date: Mon, 11 Jun 2018 05:02:01 +0300
Message-ID: <CAGXs5wWPOfAwdfzKiBi8jzy8stHDGS-Fwa2jdOjjKvHx+LcxDw@mail.gmail.com>
To: dev@dpdk.org, jerin.jacob@caviumnetworks.com
Content-Type: text/plain; charset="UTF-8"
Subject: [dpdk-dev] Is there any HW requirement for a NIC to use the
 eventdev API for implementing Rx/Tx?
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2018 02:02:03 -0000

Hi,
According to what I understand from:
http://dpdk.org/doc/guides/eventdevs/index.html

only 3 drivers currently use the eventdev API,
NXP DPAA,NXP DPAA2 and Octeon SSOVF.

My question is: is there any HW requirements from a NIC
so that it will use the eventdev API for RX/TX instead
of the traditional polling mode used by all the other PMD drivers ?
Or theoretically and practically, one can implement DPDK driver using the
eventndev API for Rx/Tx for any NIC ?

Regards,
Kevin