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 7B09D45A9A for ; Thu, 3 Oct 2024 11:23:11 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 505A3400D7; Thu, 3 Oct 2024 11:23:11 +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 81E97400D7 for ; Thu, 3 Oct 2024 11:23:10 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1727947390; 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=svdd38dobce6BtFAJ4baSxHyo7+2ZNCreCbAnkZH7/w=; b=GYzNA7CxaQv2nNGJCN7KKydxf8pd+Q1DiQ2jrQLFpjAkI1ZPrY/MiikaUcPBbgFUFvEY89 2DZQQ5CERJKcuHZ5Gcoy8rA10+9PpEiW7mlQqpyefYOrlFuwmA3LwiMtpOqCEo8JTYTk5b 5HC0S8v3QoQD/LgW9V2XsPO82ePxlLE= Received: from mail-lf1-f71.google.com (mail-lf1-f71.google.com [209.85.167.71]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-48-DCSzCE0cOPqYzQtnDRFCAg-1; Thu, 03 Oct 2024 05:23:08 -0400 X-MC-Unique: DCSzCE0cOPqYzQtnDRFCAg-1 Received: by mail-lf1-f71.google.com with SMTP id 2adb3069b0e04-5398b8cb3cdso510437e87.1 for ; Thu, 03 Oct 2024 02:23:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727947387; x=1728552187; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=svdd38dobce6BtFAJ4baSxHyo7+2ZNCreCbAnkZH7/w=; b=Avnb+AeT1vhFciIaNRhqtvCZsc71BScrinoAa+YHDUL4/s9hMvZJW9aldPbMpn23Ee IxxDl7/2/9k1wyBmCEw+YU1OeB4K46Vhv3lHzZzcnUMBPNeHqm04aYknJvMeCkxkraxO jw6MM8O615jG0eV19fQ9R64YFL+j5qqLtf/njTt+6p3obrLLA1IslqsxOefFqwg64r8L MOkyb+K+bE9K3IMdO9To/NLy6wPHcdXyXV7Qy7bg6vkEUeYlBV6HWot7TGgpdyuj/2qv BU/HGidzeYvisOiPX1KtPlgbDetbzdIO+s9THFSEiyAXH6MBtQcKAr2319AtPOlzGowN EmNA== X-Forwarded-Encrypted: i=1; AJvYcCW0CSUvpTlut9wij6kINQdvztYcklMMsMyerJ0WWOHFMBzB0ijlUn5nLuerxzdGecW7uNoR7uA=@dpdk.org X-Gm-Message-State: AOJu0YzZOK5eGZyHWMETbOU4cqWO1It54eZLxDJu7v+aEaMELJ2hwX7P S4hC2j7IeVyZgQg08NFTyh5JbNxGnCW8AerpxkKHvZcr0Dc6o4amVGErW2Id/jB771Myh1jfBiI daYEOX9eRB3ckunp8wGIKQWLSRPzkasAwncSTA6c9FQu1DNAH+UlKv9N6ACiMWqGEeccAM1Hkeu CrQYCMPdiLZXHVX+57g5U= X-Received: by 2002:a05:6512:1114:b0:539:8fcd:524 with SMTP id 2adb3069b0e04-539a0683c21mr3559966e87.30.1727947387312; Thu, 03 Oct 2024 02:23:07 -0700 (PDT) X-Google-Smtp-Source: AGHT+IGeOFj0XVt1U00jXlt1N4vOeZrbi/CVcj+oRlMIlDpI/uo/ixC1oUilJXMhbFkIuitBqtgLS+88DlDVZO2ws4g= X-Received: by 2002:a05:6512:1114:b0:539:8fcd:524 with SMTP id 2adb3069b0e04-539a0683c21mr3559947e87.30.1727947386929; Thu, 03 Oct 2024 02:23:06 -0700 (PDT) MIME-Version: 1.0 References: <20241003081110.3471793-1-maxime.coquelin@redhat.com> In-Reply-To: <20241003081110.3471793-1-maxime.coquelin@redhat.com> From: David Marchand Date: Thu, 3 Oct 2024 11:22:56 +0200 Message-ID: Subject: Re: [PATCH v2] vhost: restrict set max queue pair API to VDUSE To: Maxime Coquelin Cc: dev@dpdk.org, chenbox@nvidia.com, yux.jiang@intel.com, stable@dpdk.org X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 On Thu, Oct 3, 2024 at 10:11=E2=80=AFAM Maxime Coquelin wrote: > > In order to avoid breaking Vhost-user live-migration, we want the > rte_vhost_driver_set_max_queue_num API to only be effective with > VDUSE. > > Furthermore, this API is only really needed for VDUSE where the > device number of queues is defined by the backend. For Vhost-user, > this is defined by the frontend (e.g. QEMU), so the advantages of > restricting more the maximum number of queue pairs is limited to > a small memory gain (a handful of pointers). > > Fixes: 4aa1f88ac13d ("vhost: add API to set max queue pairs") > Cc: stable@dpdk.org > > Reported-by: Yu Jiang > Signed-off-by: Maxime Coquelin Acked-by: David Marchand --=20 David Marchand