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=-3.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,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 28F24C11F66 for ; Tue, 29 Jun 2021 06:41:16 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 0EE5461CC7 for ; Tue, 29 Jun 2021 06:41:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232177AbhF2Gnl (ORCPT ); Tue, 29 Jun 2021 02:43:41 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54130 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232134AbhF2Gnj (ORCPT ); Tue, 29 Jun 2021 02:43:39 -0400 Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 487E4C061760 for ; Mon, 28 Jun 2021 23:41:11 -0700 (PDT) Received: by mail-ed1-x533.google.com with SMTP id n25so3210982edw.9 for ; Mon, 28 Jun 2021 23:41:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bytedance-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=llkKHmBkfnr2e7nGu5wo9NWF1Rvx5VVNTXNZeIaOEY8=; b=b6IxjHxgrsOeV79Ht0Ax4/VA7XYqaQCz8mEI89nlODOpkbbNQKkT86lVUMKt1PlsZi aO9kArwDvjiDefLm8Gqo0xUt1Mk7mf97PWF41AYIIn47zWADydgm2jEpt5HbuvJNgu5D ntPRGt8AK87ZDLLlBie2K5g/5+KlMcWQeGjcg4WsoHO2ksy66nVpAOJnvc90t5QRYxsZ lmYM79ne39YAIfMIugI5AFk+AfwA9H9Bbs5SlIVioXOv0ITHb/z3Mum0jibvHXkilmpY vBesh85ghF0T5N8Mk3dWMoelFiG83Ubtv9E3WAB1/u1Mox5/MvGtN3SeVQ5/0Ut6/dR8 OyRg== 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:content-transfer-encoding; bh=llkKHmBkfnr2e7nGu5wo9NWF1Rvx5VVNTXNZeIaOEY8=; b=PepNM+Jh9Ou62eJIKiNhITMo9LXpfWV9B1U623oelyvkC2aE+IaDpNmIR9JmAmYbb8 xaJL6ADdQUtj1yawOYRTMDueJCOd161CtpqEQrqlps5HDe6RAVKDTLIN10TDwQB6kbPJ GanVkcRqjuVH6kxNG2e2o7/RElYIOcR8oVo/yAM9/no/rNxfHUnIUPztJ5LjyJFa23mQ tz99/bP20IjhP6aysciZIN7MY5Kevh5tpBo/UfJk1fDCFiCEazesPh7joiuY0YDKEiIm gK4a4DRaA5W23UZhZgdIsEjDwcv6aF2LKeMOcLX9jC5pRCRHbEVGZfItM64I5osBVec7 lN/g== X-Gm-Message-State: AOAM5305j9Sno5JPXdYEdlkam5TehqJbniru3fR+FQIfjFS1dTFHkjvn Zw3ikjB/lc5kzKEUnOavy0qcKPpOWxpC7Iu/HJBl X-Google-Smtp-Source: ABdhPJztCqFdUxDVPRMjQB4Q3BvYvtgtIsSUG1gu1hpU8fUwWsabUxu+tfnt4bzd/O6vpsvz+4mWTWvqMD3uAaEQxFk= X-Received: by 2002:a50:ff01:: with SMTP id a1mr37794534edu.253.1624948869940; Mon, 28 Jun 2021 23:41:09 -0700 (PDT) MIME-Version: 1.0 References: <20210615141331.407-1-xieyongji@bytedance.com> <20210628103309.GA205554@storage2.sh.intel.com> In-Reply-To: From: Yongji Xie Date: Tue, 29 Jun 2021 14:40:59 +0800 Message-ID: Subject: Re: Re: [PATCH v8 00/10] Introduce VDUSE - vDPA Device in Userspace To: Jason Wang Cc: Yongji Xie , Liu Xiaodong , "Michael S. Tsirkin" , Stefan Hajnoczi , Stefano Garzarella , Parav Pandit , Christoph Hellwig , Christian Brauner , Randy Dunlap , Matthew Wilcox , Al Viro , Jens Axboe , bcrl@kvack.org, Jonathan Corbet , =?UTF-8?Q?Mika_Penttil=C3=A4?= , Dan Carpenter , joro@8bytes.org, Greg KH , kvm , netdev@vger.kernel.org, linux-kernel , virtualization , iommu@lists.linux-foundation.org, songmuchun@bytedance.com, linux-fsdevel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Tue, Jun 29, 2021 at 12:13 PM Jason Wang wrote: > > > =E5=9C=A8 2021/6/28 =E4=B8=8B=E5=8D=886:32, Yongji Xie =E5=86=99=E9=81=93= : > >> The large barrier is bounce-buffer mapping: SPDK requires hugepages > >> for NVMe over PCIe and RDMA, so take some preallcoated hugepages to > >> map as bounce buffer is necessary. Or it's hard to avoid an extra > >> memcpy from bounce-buffer to hugepage. > >> If you can add an option to map hugepages as bounce-buffer, > >> then SPDK could also be a potential user of vduse. > >> > > I think we can support registering user space memory for bounce-buffer > > use like XDP does. But this needs to pin the pages, so I didn't > > consider it in this initial version. > > > > Note that userspace should be unaware of the existence of the bounce buff= er. > If so, it might be hard to use umem. Because we can't use umem for coherent mapping which needs physical address contiguous space. Thanks, Yongji