From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
Virtio-Dev <virtio-dev@lists.oasis-open.org>,
Kangjie Xu <kangjie.xu@linux.alibaba.com>,
Heng Qi <hengqi@linux.alibaba.com>
Subject: Re: [virtio-dev] [PATCH v8] virtio_net: support for split transport header
Date: Wed, 28 Sep 2022 09:39:10 -0400 [thread overview]
Message-ID: <20220928093530-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <619af5b3-4c38-955f-0f7f-f351f5a9527e@redhat.com>
On Mon, Sep 26, 2022 at 04:06:17PM +0800, Jason Wang wrote:
> > Jason I think the issue with previous proposals is that they conflict
> > with VIRTIO_F_ANY_LAYOUT. We have repeatedly found that giving the
> > driver flexibility in arranging the packet in memory is benefitial.
>
>
> Yes, but I didn't found how it can conflict the any_layout. Device can just
> to not split the header when the layout doesn't fit for header splitting.
> (And this seems the case even if we're using buffers).
Well spec says:
indicates to both the device and the driver that no
assumptions were made about framing.
if device assumes that descriptor boundaries are where
driver wants packet to be stored that is clearly
an assumption.
--
MST
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2022-09-28 13:39 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 2:56 [virtio-dev] [PATCH v8] virtio_net: support for split transport header hengqi
2022-09-19 8:47 ` [virtio-dev] " Heng Qi
2022-09-21 6:27 ` Michael S. Tsirkin
2022-09-20 1:59 ` [virtio-dev] " Jason Wang
2022-09-20 3:28 ` Heng Qi
2022-09-21 6:20 ` Jason Wang
2022-09-21 6:23 ` Jason Wang
2022-09-23 3:23 ` Xuan Zhuo
2022-09-23 4:04 ` Jason Wang
2022-09-23 5:59 ` Michael S. Tsirkin
2022-09-23 6:57 ` Xuan Zhuo
2022-09-23 10:44 ` Michael S. Tsirkin
2022-09-23 10:48 ` Xuan Zhuo
2022-09-23 11:04 ` Michael S. Tsirkin
2022-09-23 12:40 ` Xuan Zhuo
2022-09-26 8:06 ` Jason Wang
2022-09-28 13:39 ` Michael S. Tsirkin [this message]
2022-09-29 1:48 ` Jason Wang
2022-09-29 7:04 ` Michael S. Tsirkin
2022-09-29 8:24 ` Xuan Zhuo
2022-09-29 10:06 ` Michael S. Tsirkin
2022-09-29 11:48 ` Xuan Zhuo
2022-10-08 4:37 ` Jason Wang
2022-10-09 1:49 ` Xuan Zhuo
2022-10-10 17:11 ` Michael S. Tsirkin
2022-10-12 3:17 ` Jason Wang
2022-10-12 5:05 ` Michael S. Tsirkin
2022-10-13 6:47 ` Jason Wang
2022-10-13 14:33 ` Michael S. Tsirkin
2022-10-18 3:07 ` Xuan Zhuo
2022-10-20 8:16 ` Heng Qi
2023-01-31 9:23 ` 回复：[virtio-dev] " hengqi
2023-01-31 9:44 ` [virtio-comment] " Heng Qi
2023-01-31 23:08 ` Parav Pandit
2023-02-01 13:17 ` Heng Qi
2023-02-02 1:45 ` Parav Pandit
2023-02-02 3:45 ` Heng Qi
2023-02-02 4:20 ` Parav Pandit
2023-02-02 5:06 ` [virtio-comment] Re: [virtio-dev] " Heng Qi
2023-02-02 11:07 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2022-09-28 1:43 [virtio-dev] " Xuan Zhuo
2022-09-28 4:05 ` Michael S. Tsirkin
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=20220928093530-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=hengqi@linux.alibaba.com \
--cc=jasowang@redhat.com \
--cc=kangjie.xu@linux.alibaba.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=xuanzhuo@linux.alibaba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.