From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id E7771A0C51; Fri, 16 Jul 2021 14:12:49 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D1FED41359; Fri, 16 Jul 2021 14:12:49 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id E11F84067B for ; Fri, 16 Jul 2021 14:12:48 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1626437568; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=g50OgMU5/55xk0DbybySQDtE0P81mGGRZRt05+aHPMg=; b=AbyHA7hXRpJJhWP6ZSkSvwH4pSk6WkGiyLBSmbm7mC+f9gs3TZKe2eTtBV0BhrplCZ38ll sameva8Pj0h89PwbSv9kAbQ+XT7WDwmU47J9NLR2emBc4hA1I00Gv8mFrKP8pUpBNeQvcR c37mogxvVV/D48+wIMjVX1F4gwMfOsM= Received: from mail-vk1-f197.google.com (mail-vk1-f197.google.com [209.85.221.197]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-458-xbTTb9tbMmmGgNWHpX0LlA-1; Fri, 16 Jul 2021 08:12:47 -0400 X-MC-Unique: xbTTb9tbMmmGgNWHpX0LlA-1 Received: by mail-vk1-f197.google.com with SMTP id g64-20020a1f52430000b0290230feb5a2b9so2145720vkb.21 for ; Fri, 16 Jul 2021 05:12:47 -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=g50OgMU5/55xk0DbybySQDtE0P81mGGRZRt05+aHPMg=; b=iF26gWVWzdDE8cWztSshZdHagsuepaCdm5I5eGuPIO9oxLwzm1BOOg6jseA+UK3IUm dAXObSxUjI3wil0vdQNz45YxJcooj2wc0HqH3qnN9AHRARdTl0eIe1eDDJQTKvUDAbHl AQXig0gdSIlgSFFhHWathoXnLem9QIXNIBeM8DJ468lIypuhIkv1jDhbUl6cXRPP9aNB i/1lLUenIdrXtqiQWaAC3jB7Xku1q5MOn0wZHoWdw+kHMyIpYRNs3cUGeR0YyQkYbEUp f18pCDysE65awCe07X74JLdGXhWX1V2Wprt/atGikY04BU04ka/CMJ3xHfX0psTKXQQ6 I2XA== X-Gm-Message-State: AOAM533G7rrki6cVDn81pgAlUOqDhus7qHSeA+yz4Kpww6bycBPtrYne 0JdSeplXP/i8Ghoufi0dPlyRyMxD8x/5hMCiJhpGWOlEnTU/tnpDiveJND6HKdXopmpD1w2Od2j 6lWlTyx+J5SK3ExvzZjs= X-Received: by 2002:a67:df85:: with SMTP id x5mr12350688vsk.17.1626437566972; Fri, 16 Jul 2021 05:12:46 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyc7/NDMLQOphbX4uJ9mnzzHaf/OLs7oGdQM8XUy/EPgUufvE5sOPUlCbGNDVjnD/6lab6XqoumVJgkf3u/xZk= X-Received: by 2002:a67:df85:: with SMTP id x5mr12350672vsk.17.1626437566785; Fri, 16 Jul 2021 05:12:46 -0700 (PDT) MIME-Version: 1.0 References: <20210527152510.1551026-1-andrew.rybchenko@oktetlabs.ru> <20210702083948.546667-1-andrew.rybchenko@oktetlabs.ru> <20210702083948.546667-20-andrew.rybchenko@oktetlabs.ru> In-Reply-To: <20210702083948.546667-20-andrew.rybchenko@oktetlabs.ru> From: David Marchand Date: Fri, 16 Jul 2021 14:12:35 +0200 Message-ID: To: Andrew Rybchenko , Igor Romanov , Ivan Malov Cc: dev , Andy Moreton Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dmarchan@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH v4 19/20] net/sfc: support flow action COUNT in transfer rules X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 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" Hello gyus, On Fri, Jul 2, 2021 at 10:41 AM Andrew Rybchenko wrote: > > From: Igor Romanov > > For now, a rule may have only one dedicated counter, shared counters > are not supported. > > HW delivers (or "streams") counter readings using special packets. > The driver creates a dedicated Rx queue to receive such packets > and requests that HW start "streaming" the readings to it. > > The counter queue is polled periodically, and the first available > service core is used for that. Hence, the user has to specify at least > one service core for counters to work. Such a core is shared by all > MAE-capable devices managed by sfc driver. If no service lcore is available, did you consider falling back and using a control thread per mae device? -- David Marchand