From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B59BEC7618B for ; Wed, 24 Jul 2019 16:32:42 +0000 (UTC) Received: from dpdk.org (dpdk.org [92.243.14.124]) by mail.kernel.org (Postfix) with ESMTP id 5229C21911 for ; Wed, 24 Jul 2019 16:32:42 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=broadcom.com header.i=@broadcom.com header.b="hVvnkaxP" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 5229C21911 Authentication-Results: mail.kernel.org; dmarc=fail (p=quarantine dis=none) header.from=broadcom.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dev-bounces@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id EC6891C227; Wed, 24 Jul 2019 18:32:40 +0200 (CEST) Received: from mail-oi1-f193.google.com (mail-oi1-f193.google.com [209.85.167.193]) by dpdk.org (Postfix) with ESMTP id 7E8B41C222 for ; Wed, 24 Jul 2019 18:32:38 +0200 (CEST) Received: by mail-oi1-f193.google.com with SMTP id m202so35481132oig.6 for ; Wed, 24 Jul 2019 09:32:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=F6he9rUgh/jtqCiIiA3CMwin1blOUZh3rcEFl0jmMIU=; b=hVvnkaxPndgve8rEmIvSt2lbQNLujFLqcTdIhn43epNgOIFlxmK/dXZFmuSJtk4m/W eVhtF8HXTE2zXyciAqIhxy/rEBeFVfriOmjufB7yTetly4BzT9Yyb3QJsVVi6xasJAoo AvJh434cKWCxG9ZUqGUyqsPmz1slMseYxknkE= 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=F6he9rUgh/jtqCiIiA3CMwin1blOUZh3rcEFl0jmMIU=; b=EQAQ62bzbLUsiRmVQBgfYQ+jPvdaWgNf7sBYM3iTwk/ZYWqsNjljw4dRRV2l7fdiM2 XycG/+OAyy5ZtxpiGXJt7L6a4k0hq4NsZQ7tEbLAUxMCU/rrBYkBIEPOu8bBdyEQ7F5S noY5lzDeFoPpGUzzah2iUBdw54a5+O+1j+KgL2/pam0sSGiazZFAQCB2DVtybliN/zgC QGTdS/fy0e4ZolXYjuLRFQAfooIo7cbMObeiJQ3OYOlUUrzXWVnC+7ph+ND+Q9sGCD22 ZxHcohSNBJlGJzDby7feIoi2lWDkfUqPPqIqlxaSlrNQvbDsgN1z+K8/vnWONWUQdz57 vfmA== X-Gm-Message-State: APjAAAX7AQ4DY5tf5oYk0eWAJWDiP37XAxLfoNzMoGaGEevtSrAQG+nI Ngwbg7/TG/Hh5GkXnbACQhrPvbiCTlQ8YKWNjvcZejK1mjM= X-Google-Smtp-Source: APXvYqzlY7hT+XDdIU1F1fhiRLTlW0RYBAZlfwq77meS9sUhTcgTWzt+OaoFrf40Z1/GR7Wi6u7XVaMrcarxj6FxDss= X-Received: by 2002:a05:6808:182:: with SMTP id w2mr7097667oic.56.1563985957701; Wed, 24 Jul 2019 09:32:37 -0700 (PDT) MIME-Version: 1.0 References: <20190718033616.37605-10-ajit.khaparde@broadcom.com> <20190724161429.11946-1-lance.richardson@broadcom.com> In-Reply-To: <20190724161429.11946-1-lance.richardson@broadcom.com> From: Lance Richardson Date: Wed, 24 Jul 2019 12:32:26 -0400 Message-ID: To: dev@dpdk.org Cc: Ajit Khaparde , Somnath Kotur , Ferruh Yigit , Thomas Monjalon Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH] net/bnxt: use dedicated cpr for async events 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 24, 2019 at 12:14 PM Lance Richardson wrote: > process async events on a receive completion ring. This behavior > is controlled by a compile-time configuration variable. I will follow up with a v2 to correct the above statement in the commit log and to squash with these follow-up patches: http://patchwork.dpdk.org/patch/56799/ http://patchwork.dpdk.org/patch/56800/