Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752920AbaJMGWY (ORCPT ); Mon, 13 Oct 2014 02:22:24 -0400 Received: from mx1.redhat.com ([209.132.183.28]:52435 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751434AbaJMGWV (ORCPT ); Mon, 13 Oct 2014 02:22:21 -0400 Message-ID: <543B6F94.2090107@redhat.com> Date: Mon, 13 Oct 2014 14:22:12 +0800 From: Jason Wang User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: "Michael S. Tsirkin" CC: rusty@rustcorp.com.au, virtualization@lists.linux-foundation.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux-api@vger.kernel.org, kvm@vger.kernel.org Subject: Re: [PATCH net-next RFC 1/3] virtio: support for urgent descriptors References: <1413011806-3813-1-git-send-email-jasowang@redhat.com> <1413011806-3813-2-git-send-email-jasowang@redhat.com> <20141012092744.GA9567@redhat.com> In-Reply-To: <20141012092744.GA9567@redhat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/12/2014 05:27 PM, Michael S. Tsirkin wrote: > On Sat, Oct 11, 2014 at 03:16:44PM +0800, Jason Wang wrote: >> Below should be useful for some experiments Jason is doing. >> I thought I'd send it out for early review/feedback. >> >> event idx feature allows us to defer interrupts until >> a specific # of descriptors were used. >> Sometimes it might be useful to get an interrupt after >> a specific descriptor, regardless. >> This adds a descriptor flag for this, and an API >> to create an urgent output descriptor. >> This is still an RFC: >> we'll need a feature bit for drivers to detect this, >> but we've run out of feature bits for virtio 0.X. >> For experimentation purposes, drivers can assume >> this is set, or add a driver-specific feature bit. >> >> Signed-off-by: Michael S. Tsirkin >> Signed-off-by: Jason Wang > I see that as compared to my original patch, you have > added a new flag: VRING_AVAIL_F_NO_URGENT_INTERRUPT > I don't think it's necessary, see below. > > As such, I think this patch should be split: > - original patch adding support for urgent descriptors > - a patch adding virtqueue_enable/disable_cb_urgent(_prepare)? Not sure this is a good idea, since the api of first patch is in-completed. > >> --- >> drivers/virtio/virtio_ring.c | 75 +++++++++++++++++++++++++++++++++++++--- >> include/linux/virtio.h | 14 ++++++++ >> include/uapi/linux/virtio_ring.h | 5 ++- >> 3 files changed, 89 insertions(+), 5 deletions(-) >> [...] >> >> +unsigned virtqueue_enable_cb_prepare_urgent(struct virtqueue *_vq) >> +{ >> + struct vring_virtqueue *vq = to_vvq(_vq); >> + u16 last_used_idx; >> + >> + START_USE(vq); >> + vq->vring.avail->flags &= ~VRING_AVAIL_F_NO_URGENT_INTERRUPT; >> + last_used_idx = vq->last_used_idx; >> + END_USE(vq); >> + return last_used_idx; >> +} >> +EXPORT_SYMBOL_GPL(virtqueue_enable_cb_prepare_urgent); >> + > You can implement virtqueue_enable_cb_prepare_urgent > simply by clearing ~VRING_AVAIL_F_NO_INTERRUPT. > > The effect is same: host sends interrupts only if there > is an urgent descriptor. Seems not, consider the case when event index was disabled. This will turn on all interrupts. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/