From: Tiwei Bie <tiwei.bie@intel.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: mst@redhat.com, jasowang@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 5/5] virtio_ring: enable packed ring
Date: Wed, 16 May 2018 20:26:21 +0800 [thread overview]
Message-ID: <20180516122621.GA986@debian> (raw)
In-Reply-To: <dc6f6d01-7ca5-5264-6a58-1d5327da08cb@cogentembedded.com>
On Wed, May 16, 2018 at 02:42:53PM +0300, Sergei Shtylyov wrote:
> On 05/16/2018 01:21 PM, Tiwei Bie wrote:
>
> >>> Signed-off-by: Tiwei Bie <tiwei.bie@intel.com>
> >>> ---
> >>> drivers/virtio/virtio_ring.c | 2 ++
> >>> 1 file changed, 2 insertions(+)
> >>>
> >>> diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c
> >>> index de3839f3621a..b158692263b0 100644
> >>> --- a/drivers/virtio/virtio_ring.c
> >>> +++ b/drivers/virtio/virtio_ring.c
> >>> @@ -1940,6 +1940,8 @@ void vring_transport_features(struct virtio_device *vdev)
> >>> break;
> >>> case VIRTIO_F_IOMMU_PLATFORM:
> >>> break;
> >>> + case VIRTIO_F_RING_PACKED:
> >>> + break;
> >>
> >> Why not just add this *case* under the previous *case*?
> >
> > Do you mean fallthrough? Something like:
> >
> > case VIRTIO_F_IOMMU_PLATFORM:
> > case VIRTIO_F_RING_PACKED:
> > break;
>
> Yes, exactly. :-)
Using fallthrough in this case will make the code more
compact. I like such coding style. But unfortunately,
it's not consistent with the existing code. :(
The whole function will become something like this:
void vring_transport_features(struct virtio_device *vdev)
{
unsigned int i;
for (i = VIRTIO_TRANSPORT_F_START; i < VIRTIO_TRANSPORT_F_END; i++) {
switch (i) {
case VIRTIO_RING_F_INDIRECT_DESC:
break;
case VIRTIO_RING_F_EVENT_IDX:
break;
case VIRTIO_F_VERSION_1:
break;
case VIRTIO_F_IOMMU_PLATFORM:
case VIRTIO_F_RING_PACKED:
break;
default:
/* We don't understand this bit. */
__virtio_clear_bit(vdev, i);
}
}
}
Best regards,
Tiwei Bie
>
> > Best regards,
> > Tiwei Bie
>
> [...]
>
> MBR, Sergei
>
prev parent reply other threads:[~2018-05-16 12:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 8:37 [RFC v4 0/5] virtio: support packed ring Tiwei Bie
2018-05-16 8:37 ` [RFC v4 1/5] virtio: add packed ring definitions Tiwei Bie
2018-05-16 8:37 ` [RFC v4 2/5] virtio_ring: support creating packed ring Tiwei Bie
2018-05-16 8:37 ` [RFC v4 3/5] virtio_ring: add packed ring support Tiwei Bie
2018-05-16 11:50 ` Jason Wang
2018-05-16 12:39 ` Tiwei Bie
2018-05-16 12:51 ` Jason Wang
2018-05-16 13:45 ` Tiwei Bie
2018-05-16 14:05 ` Jason Wang
2018-05-16 14:33 ` Tiwei Bie
2018-05-17 12:01 ` Jason Wang
2018-05-18 11:29 ` Tiwei Bie
2018-05-18 13:17 ` Jason Wang
2018-05-18 14:33 ` Tiwei Bie
2018-05-19 1:12 ` Jason Wang
2018-05-19 2:29 ` Tiwei Bie
2018-05-21 2:30 ` Jason Wang
2018-05-21 2:39 ` Tiwei Bie
2018-05-16 8:37 ` [RFC v4 4/5] virtio_ring: add event idx support in packed ring Tiwei Bie
2018-05-16 12:17 ` Jason Wang
2018-05-16 12:58 ` Tiwei Bie
2018-05-16 13:31 ` Jason Wang
2018-05-16 8:37 ` [RFC v4 5/5] virtio_ring: enable " Tiwei Bie
2018-05-16 10:15 ` Sergei Shtylyov
2018-05-16 10:21 ` Tiwei Bie
2018-05-16 11:42 ` Sergei Shtylyov
2018-05-16 12:26 ` Tiwei Bie [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180516122621.GA986@debian \
--to=tiwei.bie@intel.com \
--cc=jasowang@redhat.com \
--cc=jfreimann@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=wexu@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).