From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: zhenwei pi <pizhenwei@bytedance.com>,
"stefanha@redhat.com" <stefanha@redhat.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
"houp@yusur.tech" <houp@yusur.tech>,
"helei.sig11@bytedance.com" <helei.sig11@bytedance.com>,
"zhouhuaping.san@bytedance.com" <zhouhuaping.san@bytedance.com>,
"xinhao.kong@duke.edu" <xinhao.kong@duke.edu>
Subject: [virtio-comment] Re: PING: [PATCH v4 0/7] Introduce Virtio Over Fabrics
Date: Wed, 19 Jul 2023 08:48:31 -0400 [thread overview]
Message-ID: <20230719084646-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB54816BDFABCC4F2D7DD9D95EDC39A@PH0PR12MB5481.namprd12.prod.outlook.com>
On Wed, Jul 19, 2023 at 12:44:52PM +0000, Parav Pandit wrote:
>
>
> > From: zhenwei pi <pizhenwei@bytedance.com>
> > Sent: Wednesday, July 19, 2023 3:07 AM
> >
> > Hi Stefan & Parav
> >
> > Ping!
> >
>
> This task is not in the top items for 1.4 for virtio, so had slow progress.
> I will spend some time this month.
maybe it should be :)
zhenwei if you are going to do something as significant as adding a new
transport you really should join the TC as a member I think.
--
MST
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next prev parent reply other threads:[~2023-07-19 12:48 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 7:25 [virtio-comment] [PATCH v4 0/7] Introduce Virtio Over Fabrics zhenwei pi
2023-06-26 7:25 ` [virtio-comment] [PATCH v4 1/7] transport-fabrics: introduce Virtio Over Fabrics overview zhenwei pi
2023-07-29 23:23 ` Raphael Norwitz
2023-07-31 4:44 ` zhenwei pi
2023-08-01 0:20 ` Raphael Norwitz
2023-11-15 14:20 ` [virtio-comment] " Stefan Hajnoczi
2023-06-26 7:25 ` [virtio-comment] [PATCH v4 2/7] transport-fabrics: introduce Virtio-oF Qualified Name zhenwei pi
2023-07-29 23:24 ` Raphael Norwitz
2023-06-26 7:25 ` [virtio-comment] [PATCH v4 3/7] transport-fabrics: introduce Virtio-oF Protocol Data Unit zhenwei pi
2023-07-29 23:25 ` Raphael Norwitz
2023-07-31 2:28 ` zhenwei pi
2023-06-26 7:25 ` [virtio-comment] [PATCH v4 4/7] transport-fabrics: introduce command set zhenwei pi
2023-06-27 9:04 ` [virtio-comment] " Jason Wang
2023-06-28 1:34 ` [virtio-comment] " zhenwei pi
2023-06-28 2:56 ` Jason Wang
2023-06-28 6:53 ` [virtio-comment] " zhenwei pi
2023-07-29 23:28 ` [virtio-comment] " Raphael Norwitz
2023-07-31 2:34 ` zhenwei pi
2023-08-01 0:25 ` Raphael Norwitz
2023-08-01 2:00 ` zhenwei pi
2023-06-26 7:25 ` [virtio-comment] [PATCH v4 5/7] transport-fabrics: introduce transport binding zhenwei pi
2023-07-29 23:28 ` Raphael Norwitz
2023-07-31 2:36 ` zhenwei pi
2023-06-26 7:25 ` [virtio-comment] [PATCH v4 6/7] transport-fabrics: add device initialization zhenwei pi
2023-07-29 23:29 ` Raphael Norwitz
2023-06-26 7:25 ` [virtio-comment] [PATCH v4 7/7] transport-fabrics: introduce keyed eager buffers zhenwei pi
2023-07-29 23:30 ` Raphael Norwitz
2023-07-31 3:21 ` zhenwei pi
2023-07-19 7:07 ` [virtio-comment] PING: [PATCH v4 0/7] Introduce Virtio Over Fabrics zhenwei pi
2023-07-19 12:44 ` [virtio-comment] " Parav Pandit
2023-07-19 12:48 ` Michael S. Tsirkin [this message]
2023-07-20 2:32 ` [virtio-comment] Re: " zhenwei pi
2023-07-20 2:34 ` [virtio-comment] " Parav Pandit
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=20230719084646-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=helei.sig11@bytedance.com \
--cc=houp@yusur.tech \
--cc=jasowang@redhat.com \
--cc=parav@nvidia.com \
--cc=pizhenwei@bytedance.com \
--cc=stefanha@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=xinhao.kong@duke.edu \
--cc=zhouhuaping.san@bytedance.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