Received: by 10.223.185.116 with SMTP id b49csp4864068wrg; Tue, 27 Feb 2018 04:04:30 -0800 (PST) X-Google-Smtp-Source: AH8x224q7gtWDPBMYPrxCZhI6Fsd2Sf9ODKmlG+AWiBBqOA4WrX8cdDt6MzI3jCQXvqYSmx04Fr7 X-Received: by 10.101.75.70 with SMTP id k6mr11444746pgt.335.1519733070091; Tue, 27 Feb 2018 04:04:30 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519733070; cv=none; d=google.com; s=arc-20160816; b=usuzi8SWD/QltpkNdeLcPG5hbz9+Z8ufYD/1KC+6lYm83oVKdxn4BcjZmQ7cHQ0gVM lclurhSLuX2ksLebtBf13uf+e6HCXU645PQ/aU3ItZgdb+PC3BPl9Nl47zK61Fee9tSR TQJ8Ulkk7s4Mlxqf/88i8ac8xKWbi1oUe5w61JTwmrpJYPtFXlhV+hAUMNSLmanHAFq+ +JxWp7K4ym4z6XVUmqaWEH08UaGEdPubmcT9MSXgk7dhi6KIk4xxD6c1fl0Id5wgCE9p z/ZPYMyAP0fi2p5L2x6KLQBMaLwveuMIfC7ZBOH9bc95c42g6nWu/tax2nDpXm9dNDVB kpFw== 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-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=jdKgsYZGhCW9fiQ+BTAy2DAMZ/Dz4xvSKSNoZjSGzl0=; b=xMOUV3DixRV3DoL9+0Jh17uGaii1XPRQxzyFqy8rd9K+M8c2J4eIRlODva3LVgEHbB GPNV922/kYoUtCgwpvESF4oKd8Ik3rjSksUUfgmTslMh24Bg94X0XDqTBxcpCYnH0I7M xuLU4idkEWsEhwGURu00Z5D7MSNYAWK3AQN1azVi29CkDlTE92KbLnLGAWv94z0C+Dtb 31rIsA8+fpG77B8t2KdoHBh/jZ7ToT6sJKXugReWf/OVXyvW7gVhnlS9hPH7v/WwQ5eu FrmfuwVTkp6qj+cMGa5NA80j6TFsS/uHDm2gu3KaUJEcf2E0poRlYx1Ly8/4aIw/1kq4 pvsQ== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j22-v6si8470526pli.594.2018.02.27.04.04.15; Tue, 27 Feb 2018 04:04:30 -0800 (PST) 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752772AbeB0MDf (ORCPT + 99 others); Tue, 27 Feb 2018 07:03:35 -0500 Received: from mga18.intel.com ([134.134.136.126]:35592 "EHLO mga18.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752130AbeB0MDe (ORCPT ); Tue, 27 Feb 2018 07:03:34 -0500 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Feb 2018 04:03:33 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.47,400,1515484800"; d="scan'208";a="37803009" Received: from debian.sh.intel.com (HELO debian) ([10.67.104.164]) by orsmga002.jf.intel.com with ESMTP; 27 Feb 2018 04:03:31 -0800 Date: Tue, 27 Feb 2018 20:01:59 +0800 From: Tiwei Bie To: Jens Freimann Cc: mst@redhat.com, virtualization@lists.linux-foundation.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, jasowang@redhat.com, wexu@redhat.com Subject: Re: [PATCH RFC 1/2] virtio: introduce packed ring defines Message-ID: <20180227120159.g47rtazm3uhoht6f@debian> References: <20180223111801.15240-1-tiwei.bie@intel.com> <20180223111801.15240-2-tiwei.bie@intel.com> <20180227085458.h5dytkwaeczrrijr@dhcp-192-241.str.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20180227085458.h5dytkwaeczrrijr@dhcp-192-241.str.redhat.com> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 27, 2018 at 09:54:58AM +0100, Jens Freimann wrote: > On Fri, Feb 23, 2018 at 07:18:00PM +0800, Tiwei Bie wrote: [...] > > > > +struct vring_packed_desc_event { > > + /* Descriptor Event Offset */ > > + __virtio16 desc_event_off : 15, > > + /* Descriptor Event Wrap Counter */ > > + desc_event_wrap : 1; > > + /* Descriptor Event Flags */ > > + __virtio16 desc_event_flags : 2; > > +}; > > Where would the virtqueue number go in driver notifications? This structure is for event suppression instead of notification. You could refer to the "Event Suppression Structure Format" section of the spec for more details: https://github.com/oasis-tcs/virtio-docs/blob/master/virtio-v1.1-packed-wd08.pdf Best regards, Tiwei Bie