Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp7133419imm; Sun, 20 May 2018 19:39:54 -0700 (PDT) X-Google-Smtp-Source: AB8JxZoX2VxCn8XKH+aneVwVn5G/tEKncgLtxmGep3jksQCtISxXaY6n9G5PP2pAnGIo45a4RLa2 X-Received: by 2002:a17:902:7149:: with SMTP id u9-v6mr18503886plm.356.1526870394793; Sun, 20 May 2018 19:39:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526870394; cv=none; d=google.com; s=arc-20160816; b=prj0HvetXKvgvgFbPC8r4WWAogxSFL72r6lRijJbGrjr+LxQD6CJi43L3Rh870H6C7 vmLQN7joTrcURPgSh8cd95KlEAnjuSe5O6CyVpz3Fruo2FBfnhYkuXgJxsnAm5vK9NS0 P96gXXDTByHcsVlMlUzdylrrokrZHrNF80/ktJNYwVEdyFoWUM/TupQFVc36Ua9a0SRA cuVHtFPoyfMgPIlDUXWl5/t8l2lCPLPF5As4Lsw40Tm5jJWFLvzHCdm4TztXtHYSnU/i bp8qaQ0DcbvNTKA+1kLsgnLC/1W73zfsyxYk0i5PcHF8AdSgMvx8lufvOqaQ4FoAYi+9 T/Bg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date :arc-authentication-results; bh=+9UOn3mXhNOoYqm31yH0swHI+MGNJhCBCyE/N6CKtzo=; b=O9cNk6HJhdRtA2K/gNaqSUlCzFfkovVo/p8MkhkmRGD32+gvvNYM1gzdtJLc7YSbse +WY0yPpjVZsdxt9xKpgMyh39GMxTFbLi3Cjg0kdyX7Afhyr747YPHg7vf62+x8UR85rG o7rIsOK8BEbMZeQOauIzEkzaRx0uBYsqpRr3oNr1Lml7ydsp0hq0E0hOKkl3z6O6FkR3 SmUYlhWZUxCqdD/ifIvI/Bj8IZRMVvtuWOAwXsgrXj8GYbpxvbkIF6y0HIV4oFMrGQMH 8gIFo9dHuYHFj4xsnRzosvTdJOQfAExM4djX+39ZIHIMjefGJSiQjvCHssQi3KDYpNnA /U4g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p67-v6si12543075pfp.72.2018.05.20.19.39.40; Sun, 20 May 2018 19:39:54 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752739AbeEUCjX (ORCPT + 99 others); Sun, 20 May 2018 22:39:23 -0400 Received: from mga03.intel.com ([134.134.136.65]:49844 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751637AbeEUCjV (ORCPT ); Sun, 20 May 2018 22:39:21 -0400 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 May 2018 19:39:20 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,425,1520924400"; d="scan'208";a="230274478" Received: from debian.sh.intel.com (HELO debian) ([10.67.104.203]) by fmsmga006.fm.intel.com with ESMTP; 20 May 2018 19:39:18 -0700 Date: Mon, 21 May 2018 10:39:44 +0800 From: Tiwei Bie To: Jason Wang Cc: mst@redhat.com, virtualization@lists.linux-foundation.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, wexu@redhat.com, jfreimann@redhat.com Subject: Re: [RFC v4 3/5] virtio_ring: add packed ring support Message-ID: <20180521023944.GA16702@debian> References: <20180516134550.GB4171@debian> <20180516143332.GA1957@debian> <20180518112950.GA28224@debian> <20180518143334.GA4537@debian> <1a661df0-8ca9-b31d-9c17-8684d608a33a@redhat.com> <20180519022938.GA18888@debian> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.9.5 (2018-04-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 21, 2018 at 10:30:51AM +0800, Jason Wang wrote: > On 2018年05月19日 10:29, Tiwei Bie wrote: > > > I don't hope so. > > > > > > > I agreed driver should track the DMA addrs or some > > > > other necessary things from the very beginning. And > > > > I also repeated the spec to emphasize that it does > > > > make sense. And I'd like to do that. > > > > > > > > What I was saying is that, to support OOO, we may > > > > need to manage these context (which saves DMA addrs > > > > etc) via a list which is similar to the desc list > > > > maintained via `next` in split ring instead of an > > > > array whose elements always can be indexed directly. > > > My point is these context is a must (not only for OOO). > > Yeah, and I have the exactly same point after you > > pointed that I shouldn't get the addrs from descs. > > I do think it makes sense. I'll do it in the next > > version. I don't have any doubt about it. All my > > questions are about the OOO, instead of whether we > > should save context or not. It just seems that you > > thought I don't want to do it, and were trying to > > convince me that I should do it. > > Right, but looks like I was wrong :) > > > > > > > The desc ring in split ring is an array, but its > > > > free entries are managed as list via next. I was > > > > just wondering, do we want to manage such a list > > > > because of OOO. It's just a very simple question > > > > that I want to hear your opinion... (It doesn't > > > > means anything, e.g. It doesn't mean I don't want > > > > to support OOO. It's just a simple question...) > > > So the question is yes. But I admit I don't have better idea other than what > > > you propose here (something like split ring which is a little bit sad). > > > Maybe Michael had. > > Yeah, that's why I asked this question. It will > > make the packed ring a bit similar to split ring > > at least in the driver part. So I want to draw > > your attention on this to make sure that we're > > on the same page. > > Yes. I think we are. Cool. Glad to hear that! Thanks! :) Best regards, Tiwei Bie > > Thanks > > > Best regards, > > Tiwei Bie > > >