Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp7128476imm; Sun, 20 May 2018 19:31:26 -0700 (PDT) X-Google-Smtp-Source: AB8JxZrke4HpHtOe59jlubNdYAygJVnaC7FCU1bxtglPgFEJjfXa4SR/h9V5awLO+QaVJSxFSAr0 X-Received: by 2002:a62:de02:: with SMTP id h2-v6mr18257868pfg.205.1526869886527; Sun, 20 May 2018 19:31:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526869886; cv=none; d=google.com; s=arc-20160816; b=q2C/4HBOtnX4tRg6hhXTkpHTF2GI+rrtLb7U8gebt1HBUFzbN1JVl1XkjJhwMQb3AD xzurr/vzD5NUYaYEaYDnDOpVJTzIsm7PxqP7f5E/Qt2SUAnDfW8iIrEFK/rachVEk66W DpQhrWwnm7r8dZbBlsVFDIJyC6CDw6c6phLaGRBcMt/vuml0+Sy8Q0vdFRu1x8tboof5 lJdkEGU4fITEu4YvcibwL+kcKKoOvzRjT2C8Mttzw+rxvv2bU5DfoYTCAK/SoyM5QM2R aAFFdPL7/zo5VhqKDQuO7Fy5H/vP6aXGWWWevQmxa3RF319pLuh0JpX5NuE6ZB+BZC+A sSAQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=2j0oXhs4SAy5a1kqIWdyISZmlmme4ElIlJJ/Y70bo2Y=; b=H4ZTp9xoEWgb1S3NYSk0rKl4aR4lJ6KJHFmMJq3L1tv9fMhW+yncaHPCZFgbPXau4v XRGICPQCnqPLRVxWQ2saSIIzg6/iiY7WF3L6csWRyUp/Bla3r7SVavEN/P2CiLhRUJI8 rwzEcDyuvwuGhOh4V8hS8MZvEfQK9Zhyt5f4Va8TG8xw/dnu7QaRSUNfazpMnEp2E4nG QNrXimCQFTb7XEAO+G65NqPyhMrNxwr7sCLr04a1MQ5M5WpnCOMcI/iRS9aF/gafl6ia WxJlPbAC5QLuP/P4A/dmuHnRafJgYY7rlPXV+HU4kGejMdhFPAMlV5oqsX65hZrGusos CiQg== 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=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v9-v6si13525641plg.124.2018.05.20.19.31.11; Sun, 20 May 2018 19:31:26 -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=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752653AbeEUCa7 (ORCPT + 99 others); Sun, 20 May 2018 22:30:59 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:43360 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751094AbeEUCa5 (ORCPT ); Sun, 20 May 2018 22:30:57 -0400 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 0CE88413C12D; Mon, 21 May 2018 02:30:57 +0000 (UTC) Received: from [10.72.12.38] (ovpn-12-38.pek2.redhat.com [10.72.12.38]) by smtp.corp.redhat.com (Postfix) with ESMTPS id DCE652024505; Mon, 21 May 2018 02:30:53 +0000 (UTC) Subject: Re: [RFC v4 3/5] virtio_ring: add packed ring support To: Tiwei Bie Cc: mst@redhat.com, virtualization@lists.linux-foundation.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, wexu@redhat.com, jfreimann@redhat.com References: <20180516123909.GB986@debian> <20180516134550.GB4171@debian> <20180516143332.GA1957@debian> <20180518112950.GA28224@debian> <20180518143334.GA4537@debian> <1a661df0-8ca9-b31d-9c17-8684d608a33a@redhat.com> <20180519022938.GA18888@debian> From: Jason Wang Message-ID: Date: Mon, 21 May 2018 10:30:51 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180519022938.GA18888@debian> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Scanned-By: MIMEDefang 2.78 on 10.11.54.4 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.7]); Mon, 21 May 2018 02:30:57 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.7]); Mon, 21 May 2018 02:30:57 +0000 (UTC) for IP:'10.11.54.4' DOMAIN:'int-mx04.intmail.prod.int.rdu2.redhat.com' HELO:'smtp.corp.redhat.com' FROM:'jasowang@redhat.com' RCPT:'' Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. Thanks > Best regards, > Tiwei Bie >