From: Cornelia Huck <cohuck@redhat.com>
To: Alvaro Karsz <alvaro.karsz@solid-run.com>
Cc: virtio-comment@lists.oasis-open.org
Subject: Re: [virtio-comment] [PATCH v7] Introduction of Virtio Network device notifications coalescing feature.
Date: Tue, 21 Jun 2022 12:31:54 +0200 [thread overview]
Message-ID: <87mte68fz9.fsf@redhat.com> (raw)
In-Reply-To: <CAJs=3_D0Ou99btHFm7_1LHk+7FCdWnbKZCrzS5Ypj1sityVCBQ@mail.gmail.com>
On Tue, Jun 21 2022, Alvaro Karsz <alvaro.karsz@solid-run.com> wrote:
>> Note that we are currently voting on
>> https://lists.oasis-open.org/archives/virtio-comment/202110/msg00010.html,
>> which uses feature bits 54 + 55, so this would need to pick another
>> one. No big deal, though, as we still have spare bits until we reach
>> 50. [Should we need to go to the range above 63, IIRC at least PCI would
>> need a tweak to support more than 64 feature bits, but that's not urgent
>> yet.]
>
> Do you want me to create a new version with a different bit?
> Or should I wait a little longer for comments/ack from a member who is
> more familiar with virtio-net?
I think it would be best to wait for a review from the virtio-net folks;
the bit is easy enough to change.
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:[~2022-06-21 10:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 14:39 [virtio-comment] [PATCH v7] Introduction of Virtio Network device notifications coalescing feature Alvaro Karsz
2022-06-21 9:48 ` Cornelia Huck
2022-06-21 10:23 ` Alvaro Karsz
2022-06-21 10:31 ` Cornelia Huck [this message]
2022-06-22 8:38 ` Alvaro Karsz
2022-06-23 3:13 ` Jason Wang
2022-06-23 12:04 ` Alvaro Karsz
2022-06-27 6:22 ` Jason Wang
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=87mte68fz9.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=alvaro.karsz@solid-run.com \
--cc=virtio-comment@lists.oasis-open.org \
/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