From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f53.google.com (mail-wm0-f53.google.com [74.125.82.53]) by dpdk.org (Postfix) with ESMTP id 9BF072B9B for ; Wed, 17 Aug 2016 14:34:33 +0200 (CEST) Received: by mail-wm0-f53.google.com with SMTP id i5so229283563wmg.0 for ; Wed, 17 Aug 2016 05:34:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=atomicrules-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=RKRgrJopLD3razYIE8j/VuBUgq+No2j4MTaP2coTWD0=; b=bokAaxTUOISEzzweH2K4DlWsnClE4dn0oeVy2u4wWRpa12hJTUtyb+qgRovYU0lEqR XHaiQFu3UXsMVb7ZJst0F+aldhyyrqpMD6cWIm19cJPrZvetw7XsQUcTLKhEJd24q6Hg /n6b0VegB/Ir8FOhQZvU41uIyzbtK1nNE9Cg3Rp5dXlASoaou8dF1PR7mZ0JoRPgaLLY jRSwt9sRgZDQrZH+hkfZkYZKkPYQNDPtGrMOrWDDPZkg3LI6TiRrynIgh+RW2rMWpDfH h/X9H8GK1tW+QIIhjgIMVHW3YMLEVb7idyCjWXpsThS5DfAMXRx1eTvU0s5n09JAe7Jw kuQA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=RKRgrJopLD3razYIE8j/VuBUgq+No2j4MTaP2coTWD0=; b=AMGy9p1iv72L0vhuxY+mFKe24+3lGVOg2X6PBhLndAudpTLA2iK/OkkOem4kDrgFn2 AQg7hV3+rj3X87BfAPvvS4aG1vjEHtkxhMgogX2lem3dfEXkymQXdbWCVwpvMmQhZMD3 X5f5w80O94cpPBdyNEBJaEp1H2MCmaPTAYoyuscrNAaocObRzoBQEFcgpvm9aZPoiKYF EBKlxlJk+m0FtDxQy20pAckIMZqwCg4ObvYtlErgWM3AOx81elIR4IBpEt7y9lx9x8J6 eY26tbrBQDcRPhv/1ZfZsFmM6hl7oG0KtsaBPE1ddubBkus8o9OPDuzDemF40XY7fb7G cdSA== X-Gm-Message-State: AEkoouuttHjJqxOt4oYNUXC1aOs9ZR3mpRUXAjELlJaEmZKEwk6LHDQCwaVUF3Gg70uiUMEQYSEPQR4XitSBLw== X-Received: by 10.194.36.226 with SMTP id t2mr10900359wjj.184.1471437273159; Wed, 17 Aug 2016 05:34:33 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.86.87 with HTTP; Wed, 17 Aug 2016 05:34:32 -0700 (PDT) From: Shepard Siegel Date: Wed, 17 Aug 2016 08:34:32 -0400 Message-ID: To: dev@dpdk.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] Best Practices for PMD Verification before Upstream Requests 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, 17 Aug 2016 12:34:33 -0000 Hi, Atomic Rules is new to the DPDK community. We attended the DPDK Summit last week and received terrific advice and encouragement. We are developing a DPDK PMD for our Arkville product which is a DPDK-aware data mover, capable of marshaling packets between FPGA/ASIC gates with AXI interfaces on one side, and the DPDK API/ABI on the other. Arkville plus a MAC looks like a line-rate-agnostic bare-bones L2 NIC. We have testpmd and our first DPDK applications running using our early-alpha Arkville PMD. This post is to ask of the DPDK community what tests, regressions, check-lists or similar verification assets we might work through before starting the process to upstream our code? We know device-specific PMDs are rather cloistered and unlikely to interfere; but still, others must have managed to find a way to fail with even an L2 baseline NIC. We don=E2=80= =99t want to needlessly repeat those mistakes. Any DPDK-specific collateral that we can use to verify and validate our codes before attempting to upstream them would be greatly appreciated. To the DPDK PMD developers, what can you share so that we are more aligned with your regressions? To the DPDK application developers, what=E2=80=99s your top gripe we might try to avoid= in our Arkville L2 baseline PMD? Thanks in advance. We won=E2=80=99t have anyone at the Dublin DPDK Summit, = but we will be at FPL2016 in two weeks. Any constructive feedback is greatly appreciated! Shepard Siegel, CTO atomicrules.com