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 6421DA0C4B for ; Thu, 21 Oct 2021 14:27:24 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 516B24117A; Thu, 21 Oct 2021 14:27:24 +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 99A7A4117A for ; Thu, 21 Oct 2021 14:27:22 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1634819242; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=3jDOUR9soyAbtex2vBEL7nNl6uhuMbonYRp4tode/Lc=; b=ZSFWIZnum/gcuVkB8pQEneYNoePH8jZtRS4Xy2KOcwuZzRrol3viVjwdPYY/MSQ1C2ltpZ h1IYXgj2jJMQfhd24ANsJ7VIAG7kfjEbSI9NcBYboPOQpBQgz6VagZiWs2IeQKlFJJz3xq rEG1ZdqyrF/5NAW7PxATLmtpyzu2ULE= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-336-psQPQJBNNH6yA3hZ9qPakA-1; Thu, 21 Oct 2021 08:27:19 -0400 X-MC-Unique: psQPQJBNNH6yA3hZ9qPakA-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id E98A0802B4F; Thu, 21 Oct 2021 12:27:17 +0000 (UTC) Received: from [10.39.208.27] (unknown [10.39.208.27]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 571F35D9DE; Thu, 21 Oct 2021 12:27:13 +0000 (UTC) Message-ID: <3d5b90a7-22fe-0b54-8ad0-f51b553928b2@redhat.com> Date: Thu, 21 Oct 2021 14:27:11 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.1.0 To: Xueming Li , dev@dpdk.org Cc: stable@dpdk.org, Matan Azrad , Viacheslav Ovsiienko References: <20210923081758.178745-1-xuemingl@nvidia.com> <20211015150545.1673312-1-xuemingl@nvidia.com> From: Maxime Coquelin In-Reply-To: <20211015150545.1673312-1-xuemingl@nvidia.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=maxime.coquelin@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-stable] [PATCH v2 1/2] vdpa/mlx5: workaround FW first completion in start X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Sender: "stable" On 10/15/21 17:05, Xueming Li wrote: > After a vDPA application restart, qemu restores VQ with used and > available index, new incoming packet triggers virtio driver to > handle buffers. Under heavy traffic, no available buffer for > firmware to receive new packets, no Rx interrupts generated, > driver is stuck on endless interrupt waiting. > > As a firmware workaround, this patch sends a notification after > VQ setup to ask driver handling buffers and filling new buffers. > > Fixes: bff735011078 ("vdpa/mlx5: prepare virtio queues") > Cc: stable@dpdk.org > > Signed-off-by: Xueming Li > Reviewed-by: Matan Azrad > --- > drivers/vdpa/mlx5/mlx5_vdpa_virtq.c | 4 ++++ > 1 file changed, 4 insertions(+) > Applied to dpdk-next-virtio/main. Thanks, Maxime