virtio-vsock: add max payload size config field
PATCH v4 1/1 virtio-vsock: add max payload size config field
Added a new field to the vsock device config space that is limiting the size of the packet payload. This way the driver is not allowed to allocate huge buffers, and potentially fill up the entire memory.
Also defined a new feature bit for this, VIRTIO_VSOCK_F_SIZE_MAX, in order to keep backwards compatibility.
--- conformance.tex | 2 ++ virtio-vsock.tex | 24 ++++++++++++++++++++++++ 2 files changed, 26 insertions(+)
conformance.tex +2 -0
@@ -222,6 +222,7 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets} A socket driver MUST conform to the following normative statements: \begin{itemize} +\item \ref{drivernormative:Device Types / Socket Device / Device configuration layout} \item \ref{drivernormative:Device Types / Socket Device / Device Operation / Buffer Space Management} \item \ref{drivernormative:Device Types / Socket Device / Device Operation / Receive and Transmit} \item \ref{drivernormative:Device Types / Socket Device / Device Operation / Device Events}
@@ -481,6 +482,7 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets} A socket device MUST conform to the following normative statements: \begin{itemize} +\item \ref{devicenormative:Device Types / Socket Device / Device configuration layout} \item \ref{devicenormative:Device Types / Socket Device / Device Operation / Buffer Space Management} \item \ref{devicenormative:Device Types / Socket Device / Device Operation / Receive and Transmit} \end{itemize}
virtio-vsock.tex +24 -0
@@ -23,6 +23,10 @@ \subsection{Feature bits}\label{sec:Device Types / Socket Device / Feature bits} \begin{description} \item[VIRTIO_VSOCK_F_STREAM (0)] stream socket type is supported. \item[VIRTIO_VSOCK_F_SEQPACKET (1)] seqpacket socket type is supported. +\item[VIRTIO_VSOCK_F_SIZE_MAX (2)] Maximum size of the packet payload is in + \field{data_max_size}. If offered by the device, device advises driver + about the value of its maximum payload size. If negotiated, the driver uses + \field{data_max_size} as the maximum packet payload size value. \end{description} \subsection{Device configuration layout}\label{sec:Device Types / Socket Device / Device configuration layout}
@@ -32,6 +36,7 @@ \subsection{Device configuration layout}\label{sec:Device Types / Socket Device \begin{lstlisting} struct virtio_vsock_config { le64 guest_cid; + le32 data_max_size; }; \end{lstlisting}
@@ -57,6 +62,25 @@ \subsection{Device configuration layout}\label{sec:Device Types / Socket Device \hline \end{tabular} +The following driver-read-only field, \field{data_max_size} only exists if +VIRTIO_VSOCK_F_SIZE_MAX is set. This field specifies the maximum packet payload +size for the driver to use. + +\devicenormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout} + +The device MUST NOT change the value exposed through \field{data_max_size}. + +\drivernormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout} + +A driver SHOULD negotiate VIRTIO_VSOCK_F_SIZE_MAX if the device offers it. + +If the driver negotiates VIRTIO_VSOCK_F_SIZE_MAX, the receive buffers it +supplies for a packet MUST have a total size that doesn't exceed the size +\field{data_max_size} (plus header length). + +If the driver negotiates VIRTIO_VSOCK_F_SIZE_MAX, it MUST NOT transmit packets +of size exceeding the value of \field{data_max_size} (plus header length). + \subsection{Device Initialization}\label{sec:Device Types / Socket Device / Device Initialization} \begin{enumerate}
Signature · 23 lines
2.17.1 Amazon Development Center (Romania) S.R.L. registered office: 27A Sf. Lazar Street, UBC5, floor 2, Iasi, Iasi County, 700045, Romania. Registered in Romania. Registration number J22/2621/2005. 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: [email protected] Unsubscribe: [email protected] List help: [email protected] 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/
Quoted 7 lines · Laura Loghin
Added a new field to the vsock device config space that is limiting the size of the packet payload. This way the driver is not allowed to allocate huge buffers, and potentially fill up the entire memory.
Also defined a new feature bit for this,VIRTIO_VSOCK_F_SIZE_MAX, in order to keep backwards compatibility.
Quoted 7 lines
Signed-off-by Laura Loghin <[email protected]>--- conformance.tex | 2 ++ virtio-vsock.tex | 24 ++++++++++++++++++++++++ 2 files changed, 26 insertions(+)
I think you dropped Stefano's R-b by accident -- Stefano, I guess it still holds? (I can readd when merging).
Looks good to me now; if nobody else has any comments, we can start voting.
Quoted 60 lines
conformance.tex +2
-0@@ -222,6 +222,7 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets} A socket driver MUST conform to the following normative statements: \begin{itemize} +\item \ref{drivernormative:Device Types / Socket Device / Device configuration layout} \item \ref{drivernormative:Device Types / Socket Device / Device Operation / Buffer Space Management} \item \ref{drivernormative:Device Types / Socket Device / Device Operation / Receive and Transmit} \item \ref{drivernormative:Device Types / Socket Device / Device Operation / Device Events}@@ -481,6 +482,7 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets} A socket device MUST conform to the following normative statements: \begin{itemize} +\item \ref{devicenormative:Device Types / Socket Device / Device configuration layout} \item \ref{devicenormative:Device Types / Socket Device / Device Operation / Buffer Space Management} \item \ref{devicenormative:Device Types / Socket Device / Device Operation / Receive and Transmit} \end{itemize}virtio-vsock.tex +17
-0@@ -23,6 +23,10 @@ \subsection{Feature bits}\label{sec:Device Types / Socket Device / Feature bits} \begin{description} \item[VIRTIO_VSOCK_F_STREAM (0)] stream socket type is supported. \item[VIRTIO_VSOCK_F_SEQPACKET (1)] seqpacket socket type is supported. +\item[VIRTIO_VSOCK_F_SIZE_MAX (2)] Maximum size of the packet payload is in + \field{data_max_size}. If offered by the device, device advises driver + about the value of its maximum payload size. If negotiated, the driver uses + \field{data_max_size} as the maximum packet payload size value. \end{description} \subsection{Device configuration layout}\label{sec:Device Types / Socket Device / Device configuration layout}@@ -32,6 +36,7 @@ \subsection{Device configuration layout}\label{sec:Device Types / Socket Device \begin{lstlisting} struct virtio_vsock_config { le64 guest_cid; + le32 data_max_size; }; \end{lstlisting}@@ -57,6 +62,25 @@ \subsection{Device configuration layout}\label{sec:Device Types / Socket Device \hline \end{tabular} +The following driver-read-only field, \field{data_max_size} only exists if +VIRTIO_VSOCK_F_SIZE_MAX is set. This field specifies the maximum packet payload +size for the driver to use. + +\devicenormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout} + +The device MUST NOT change the value exposed through \field{data_max_size}. + +\drivernormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout} + +A driver SHOULD negotiate VIRTIO_VSOCK_F_SIZE_MAX if the device offers it. +
virtio-vsock.tex \subsection{Device configuration layout}\label{sec:Device Types / Socket Device · line 86
Quoted 10 lines
virtio-vsock.tex +7
-0+If the driver negotiates VIRTIO_VSOCK_F_SIZE_MAX, the receive buffers it +supplies for a packet MUST have a total size that doesn't exceed the size +\field{data_max_size} (plus header length). + +If the driver negotiates VIRTIO_VSOCK_F_SIZE_MAX, it MUST NOT transmit packets +of size exceeding the value of \field{data_max_size} (plus header length). + \subsection{Device Initialization}\label{sec:Device Types / Socket Device / Device Initialization} \begin{enumerate}
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: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
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/
Stefano Garzarella
Reviewed-byQuoted 11 lines · Cornelia Huck
Quoted 9 lines · Laura Loghin
Added a new field to the vsock device config space that is limiting the size of the packet payload. This way the driver is not allowed to allocate huge buffers, and potentially fill up the entire memory.
Also defined a new feature bit for this,VIRTIO_VSOCK_F_SIZE_MAX, in order to keep backwards compatibility.
Quoted 8 lines
Quoted 5 lines
Signed-off-by Laura Loghin <[email protected]>--- conformance.tex | 2 ++ virtio-vsock.tex | 24 ++++++++++++++++++++++++ 2 files changed, 26 insertions(+)I think you dropped Stefano's R-b by accident -- Stefano, I guess it still holds? (I can readd when merging).
Yep, thanks for CCing me!
Quoted 74 lines
Looks good to me now; if nobody else has any comments, we can start voting.
Quoted 70 lines
conformance.tex +2
-0@@ -222,6 +222,7 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets} A socket driver MUST conform to the following normative statements: \begin{itemize} +\item \ref{drivernormative:Device Types / Socket Device / Device configuration layout} \item \ref{drivernormative:Device Types / Socket Device / Device Operation / Buffer Space Management} \item \ref{drivernormative:Device Types / Socket Device / Device Operation / Receive and Transmit} \item \ref{drivernormative:Device Types / Socket Device / Device Operation / Device Events}@@ -481,6 +482,7 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets} A socket device MUST conform to the following normative statements: \begin{itemize} +\item \ref{devicenormative:Device Types / Socket Device / Device configuration layout} \item \ref{devicenormative:Device Types / Socket Device / Device Operation / Buffer Space Management} \item \ref{devicenormative:Device Types / Socket Device / Device Operation / Receive and Transmit} \end{itemize}virtio-vsock.tex +24
-0@@ -23,6 +23,10 @@ \subsection{Feature bits}\label{sec:Device Types / Socket Device / Feature bits} \begin{description} \item[VIRTIO_VSOCK_F_STREAM (0)] stream socket type is supported. \item[VIRTIO_VSOCK_F_SEQPACKET (1)] seqpacket socket type is supported. +\item[VIRTIO_VSOCK_F_SIZE_MAX (2)] Maximum size of the packet payload is in + \field{data_max_size}. If offered by the device, device advises driver + about the value of its maximum payload size. If negotiated, the driver uses + \field{data_max_size} as the maximum packet payload size value. \end{description} \subsection{Device configuration layout}\label{sec:Device Types / Socket Device / Device configuration layout}@@ -32,6 +36,7 @@ \subsection{Device configuration layout}\label{sec:Device Types / Socket Device \begin{lstlisting} struct virtio_vsock_config { le64 guest_cid; + le32 data_max_size; }; \end{lstlisting}@@ -57,6 +62,25 @@ \subsection{Device configuration layout}\label{sec:Device Types / Socket Device \hline \end{tabular} +The following driver-read-only field, \field{data_max_size} only exists if +VIRTIO_VSOCK_F_SIZE_MAX is set. This field specifies the maximum packet payload +size for the driver to use. + +\devicenormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout} + +The device MUST NOT change the value exposed through \field{data_max_size}. + +\drivernormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout} + +A driver SHOULD negotiate VIRTIO_VSOCK_F_SIZE_MAX if the device offers it. + +If the driver negotiates VIRTIO_VSOCK_F_SIZE_MAX, the receive buffers it +supplies for a packet MUST have a total size that doesn't exceed the size +\field{data_max_size} (plus header length). + +If the driver negotiates VIRTIO_VSOCK_F_SIZE_MAX, it MUST NOT transmit packets +of size exceeding the value of \field{data_max_size} (plus header length). + \subsection{Device Initialization}\label{sec:Device Types / Socket Device / Device Initialization} \begin{enumerate}
Quoted 13 lines · On Mon, 13 Jun 2022 13:40:38 +0300 Laura Loghin <[email protected]> wrote:
virtio-vsock.tex +9
-0@@ -57,6 +62,25 @@ \subsection{Device configuration layout}\label{sec:Device Types / Socket Device \hline \end{tabular} +The following driver-read-only field, \field{data_max_size} only exists if +VIRTIO_VSOCK_F_SIZE_MAX is set. This field specifies the maximum packet payload +size for the driver to use. + +\devicenormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout} + +The device MUST NOT change the value exposed through \field{data_max_size}. + +\drivernormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout}
virtio-vsock.tex \subsection{Device configuration layout}\label{sec:Device Types / Socket Device · line 83
Quoted 10 lines
virtio-vsock.tex +10
-0+ +A driver SHOULD negotiate VIRTIO_VSOCK_F_SIZE_MAX if the device offers it. + +If the driver negotiates VIRTIO_VSOCK_F_SIZE_MAX, the receive buffers it +supplies for a packet MUST have a total size that doesn't exceed the size +\field{data_max_size} (plus header length). + +If the driver negotiates VIRTIO_VSOCK_F_SIZE_MAX, it MUST NOT transmit packets +of size exceeding the value of \field{data_max_size} (plus header length). +
Hi and sorry for being late to the party!
I believe I do understand why do we want to put a restriction on the size of the transmitted packets, but I would appreciate if you could explain to me why do we want to limit the receive buffer size.
Also I find the wording regarding a little bit ambiguous because in a networking context it also makes sense to talk about the size of the receive buffer. I guess hear we are talking about a single virtio buffer (a descriptor chain described potentially non-continuous (or compact in the mathematical sense of the word) which is composed from as many continuous chunks of memory as many descriptors are contained within the descriptor chain). If we are indeed talking about a single virtio buffer, I don't understand the plural. If not, I'm not sure what are we talking about.
Also, do we have some sort of packets may not cross virtio buffer boundaries, or even a single packet per single viritio buffer rule for vsock. I did a quick search and could not find any. Did I overlook something? Should we spell this out?
@Michael, Conny: What do you think?
Regards,
Halil
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: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
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/
Quoted 33 lines · Halil Pasic
Quoted 13 lines · On Mon, 13 Jun 2022 13:40:38 +0300 Laura Loghin <[email protected]> wrote:
virtio-vsock.tex +9
-0@@ -57,6 +62,25 @@ \subsection{Device configuration layout}\label{sec:Device Types / Socket Device \hline \end{tabular} +The following driver-read-only field, \field{data_max_size} only exists if +VIRTIO_VSOCK_F_SIZE_MAX is set. This field specifies the maximum packet payload +size for the driver to use. + +\devicenormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout} + +The device MUST NOT change the value exposed through \field{data_max_size}. + +\drivernormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout}virtio-vsock.tex \subsection{Device configuration layout}\label{sec:Device Types / Socket Device · line 83
Quoted 10 lines
virtio-vsock.tex +10
-0+ +A driver SHOULD negotiate VIRTIO_VSOCK_F_SIZE_MAX if the device offers it. + +If the driver negotiates VIRTIO_VSOCK_F_SIZE_MAX, the receive buffers it +supplies for a packet MUST have a total size that doesn't exceed the size +\field{data_max_size} (plus header length). + +If the driver negotiates VIRTIO_VSOCK_F_SIZE_MAX, it MUST NOT transmit packets +of size exceeding the value of \field{data_max_size} (plus header length). +Hi and sorry for being late to the party!
I believe I do understand why do we want to put a restriction on the size of the transmitted packets, but I would appreciate if you could explain to me why do we want to limit the receive buffer size.
Quoted 9 lines
Also I find the wording regarding a little bit ambiguous because in a networking context it also makes sense to talk about the size of the receive buffer. I guess hear we are talking about a single virtio buffer (a descriptor chain described potentially non-continuous (or compact in the mathematical sense of the word) which is composed from as many continuous chunks of memory as many descriptors are contained within the descriptor chain). If we are indeed talking about a single virtio buffer, I don't understand the plural. If not, I'm not sure what are we talking about.
I think I agree here, I don't understand the mix of "buffers" and "a packet" either.
I voted "no" on the ballot, though if others feel we should apply as is and fix up later, that is not too bad.
Quoted 9 lines
Also, do we have some sort of packets may not cross virtio buffer boundaries, or even a single packet per single viritio buffer rule for vsock. I did a quick search and could not find any. Did I overlook something? Should we spell this out?
@Michael, Conny: What do you think?
Regards,
Halil
Quoted 44 lines · Michael S. Tsirkin
Quoted 33 lines · Halil Pasic
Quoted 13 lines · On Mon, 13 Jun 2022 13:40:38 +0300 Laura Loghin <[email protected]> wrote:
virtio-vsock.tex +9
-0@@ -57,6 +62,25 @@ \subsection{Device configuration layout}\label{sec:Device Types / Socket Device \hline \end{tabular} +The following driver-read-only field, \field{data_max_size} only exists if +VIRTIO_VSOCK_F_SIZE_MAX is set. This field specifies the maximum packet payload +size for the driver to use. + +\devicenormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout} + +The device MUST NOT change the value exposed through \field{data_max_size}. + +\drivernormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout}virtio-vsock.tex \subsection{Device configuration layout}\label{sec:Device Types / Socket Device · line 83
Quoted 10 lines
virtio-vsock.tex +10
-0+ +A driver SHOULD negotiate VIRTIO_VSOCK_F_SIZE_MAX if the device offers it. + +If the driver negotiates VIRTIO_VSOCK_F_SIZE_MAX, the receive buffers it +supplies for a packet MUST have a total size that doesn't exceed the size +\field{data_max_size} (plus header length). + +If the driver negotiates VIRTIO_VSOCK_F_SIZE_MAX, it MUST NOT transmit packets +of size exceeding the value of \field{data_max_size} (plus header length). +Hi and sorry for being late to the party!
I believe I do understand why do we want to put a restriction on the size of the transmitted packets, but I would appreciate if you could explain to me why do we want to limit the receive buffer size.
Quoted 9 lines
Also I find the wording regarding a little bit ambiguous because in a networking context it also makes sense to talk about the size of the receive buffer. I guess hear we are talking about a single virtio buffer (a descriptor chain described potentially non-continuous (or compact in the mathematical sense of the word) which is composed from as many continuous chunks of memory as many descriptors are contained within the descriptor chain). If we are indeed talking about a single virtio buffer, I don't understand the plural. If not, I'm not sure what are we talking about.
Quoted 5 lines
I think I agree here, I don't understand the mix of "buffers" and "a packet" either.
I voted "no" on the ballot, though if others feel we should apply as is and fix up later, that is not too bad.
I now switched to "no" as well; it's not too bad to fix things later, but it would be good if we had a common understanding before the change goes in.
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: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
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/
Quoted 48 lines · Cornelia Huck
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
Quoted 42 lines · Michael S. Tsirkin
Quoted 41 lines · Halil Pasic
Quoted 13 lines · On Mon, 13 Jun 2022 13:40:38 +0300 Laura Loghin<[email protected]> wrote:
virtio-vsock.tex +9
-0@@ -57,6 +62,25 @@ \subsection{Device configuration layout}\label{sec:Device Types / Socket Device \hline \end{tabular} +The following driver-read-only field, \field{data_max_size} only exists if +VIRTIO_VSOCK_F_SIZE_MAX is set. This field specifies the maximum packet payload +size for the driver to use. + +\devicenormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout} + +The device MUST NOT change the value exposed through \field{data_max_size}. + +\drivernormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout}virtio-vsock.tex \subsection{Device configuration layout}\label{sec:Device Types / Socket Device · line 83
Quoted 10 lines
virtio-vsock.tex +10
-0+ +A driver SHOULD negotiate VIRTIO_VSOCK_F_SIZE_MAX if the device offers it. + +If the driver negotiates VIRTIO_VSOCK_F_SIZE_MAX, the receive buffers it +supplies for a packet MUST have a total size that doesn't exceed the size +\field{data_max_size} (plus header length). + +If the driver negotiates VIRTIO_VSOCK_F_SIZE_MAX, it MUST NOT transmit packets +of size exceeding the value of \field{data_max_size} (plus header length). +Hi and sorry for being late to the party!
I believe I do understand why do we want to put a restriction on the size of the transmitted packets, but I would appreciate if you could explain to me why do we want to limit the receive buffer size.
Also I find the wording regarding a little bit ambiguous because in a networking context it also makes sense to talk about the size of the receive buffer. I guess hear we are talking about a single virtio buffer (a descriptor chain described potentially non-continuous (or compact in the mathematical sense of the word) which is composed from as many continuous chunks of memory as many descriptors are contained within the descriptor chain). If we are indeed talking about a single virtio buffer, I don't understand the plural. If not, I'm not sure what are we talking about.
Quoted 9 lines
Quoted 5 lines
I think I agree here, I don't understand the mix of "buffers" and "a packet" either.
I voted "no" on the ballot, though if others feel we should apply as is and fix up later, that is not too bad.
I now switched to "no" as well; it's not too bad to fix things later, but it would be good if we had a common understanding before the change goes in.
Hi!
Sorry, I will address your comments this week. Thanks everyone for the feedback!
Laura
Amazon Development Center (Romania) S.R.L. registered office: 27A Sf. Lazar Street, UBC5, floor 2, Iasi, Iasi County, 700045, Romania. Registered in Romania. Registration number J22/2621/2005.
Quoted 49 lines · Cornelia Huck
Quoted 47 lines · Michael S. Tsirkin
Quoted 33 lines · Halil Pasic
Quoted 13 lines · On Mon, 13 Jun 2022 13:40:38 +0300 Laura Loghin <[email protected]> wrote:
virtio-vsock.tex +9
-0@@ -57,6 +62,25 @@ \subsection{Device configuration layout}\label{sec:Device Types / Socket Device \hline \end{tabular} +The following driver-read-only field, \field{data_max_size} only exists if +VIRTIO_VSOCK_F_SIZE_MAX is set. This field specifies the maximum packet payload +size for the driver to use. + +\devicenormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout} + +The device MUST NOT change the value exposed through \field{data_max_size}. + +\drivernormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout}virtio-vsock.tex \subsection{Device configuration layout}\label{sec:Device Types / Socket Device · line 83
Quoted 10 lines
virtio-vsock.tex +10
-0+ +A driver SHOULD negotiate VIRTIO_VSOCK_F_SIZE_MAX if the device offers it. + +If the driver negotiates VIRTIO_VSOCK_F_SIZE_MAX, the receive buffers it +supplies for a packet MUST have a total size that doesn't exceed the size +\field{data_max_size} (plus header length). + +If the driver negotiates VIRTIO_VSOCK_F_SIZE_MAX, it MUST NOT transmit packets +of size exceeding the value of \field{data_max_size} (plus header length). +Hi and sorry for being late to the party!
I believe I do understand why do we want to put a restriction on the size of the transmitted packets, but I would appreciate if you could explain to me why do we want to limit the receive buffer size.
Quoted 9 lines
Also I find the wording regarding a little bit ambiguous because in a networking context it also makes sense to talk about the size of the receive buffer. I guess hear we are talking about a single virtio buffer (a descriptor chain described potentially non-continuous (or compact in the mathematical sense of the word) which is composed from as many continuous chunks of memory as many descriptors are contained within the descriptor chain). If we are indeed talking about a single virtio buffer, I don't understand the plural. If not, I'm not sure what are we talking about.
I think I agree here, I don't understand the mix of "buffers" and "a packet" either.
Quoted 6 lines
Quoted 2 lines
I voted "no" on the ballot, though if others feel we should apply as is and fix up later, that is not too bad.
I now switched to "no" as well; it's not too bad to fix things later, but it would be good if we had a common understanding before the change goes in.
If anyone else intends to change their votes, note today is the last opportunity.
Alternatively, Laura, would you consider to address the issues? If you want us to withdraw the ballot to consider the options, that is ok too.
Signature · 1 line
MST
Quoted 60 lines · Michael S. Tsirkin
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
Quoted 44 lines · Cornelia Huck
Quoted 42 lines · Michael S. Tsirkin
Quoted 41 lines · Halil Pasic
Quoted 13 lines · On Mon, 13 Jun 2022 13:40:38 +0300 Laura Loghin<[email protected]> wrote:
virtio-vsock.tex +9
-0@@ -57,6 +62,25 @@ \subsection{Device configuration layout}\label{sec:Device Types / Socket Device \hline \end{tabular} +The following driver-read-only field, \field{data_max_size} only exists if +VIRTIO_VSOCK_F_SIZE_MAX is set. This field specifies the maximum packet payload +size for the driver to use. + +\devicenormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout} + +The device MUST NOT change the value exposed through \field{data_max_size}. + +\drivernormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout}virtio-vsock.tex \subsection{Device configuration layout}\label{sec:Device Types / Socket Device · line 83
Quoted 10 lines
virtio-vsock.tex +10
-0+ +A driver SHOULD negotiate VIRTIO_VSOCK_F_SIZE_MAX if the device offers it. + +If the driver negotiates VIRTIO_VSOCK_F_SIZE_MAX, the receive buffers it +supplies for a packet MUST have a total size that doesn't exceed the size +\field{data_max_size} (plus header length). + +If the driver negotiates VIRTIO_VSOCK_F_SIZE_MAX, it MUST NOT transmit packets +of size exceeding the value of \field{data_max_size} (plus header length). +Hi and sorry for being late to the party!
I believe I do understand why do we want to put a restriction on the size of the transmitted packets, but I would appreciate if you could explain to me why do we want to limit the receive buffer size.
Also I find the wording regarding a little bit ambiguous because in a networking context it also makes sense to talk about the size of the receive buffer. I guess hear we are talking about a single virtio buffer (a descriptor chain described potentially non-continuous (or compact in the mathematical sense of the word) which is composed from as many continuous chunks of memory as many descriptors are contained within the descriptor chain). If we are indeed talking about a single virtio buffer, I don't understand the plural. If not, I'm not sure what are we talking about.
Quoted 8 lines
Quoted 5 lines
I think I agree here, I don't understand the mix of "buffers" and "a packet" either.
I voted "no" on the ballot, though if others feel we should apply as is and fix up later, that is not too bad.
I now switched to "no" as well; it's not too bad to fix things later, but it would be good if we had a common understanding before the change goes in.
If anyone else intends to change their votes, note today is the last opportunity.
Quoted 7 lines
Alternatively, Laura, would you consider to address the issues? If you want us to withdraw the ballot to consider the options, that is ok too.
--
MST
Hi,
I sent a message a bit earlier. I plan to address the comments this week. I'm not yet very familiar with the voting process, but if addressing the comments means withdrawing the ballot, that is fine on my side. Thanks!
Laura
Amazon Development Center (Romania) S.R.L. registered office: 27A Sf. Lazar Street, UBC5, floor 2, Iasi, Iasi County, 700045, Romania. Registered in Romania. Registration number J22/2621/2005.
Quoted 8 lines · Laura Loghin
Quoted 7 lines · Michael S. Tsirkin
If anyone else intends to change their votes, note today is the last opportunity.
Alternatively, Laura, would you consider to address the issues? If you want us to withdraw the ballot to consider the options, that is ok too.
Quoted 6 lines
Quoted 3 lines
--
MSTHi,
I sent a message a bit earlier. I plan to address the comments this week. I'm not yet very familiar with the voting process, but if addressing the comments means withdrawing the ballot, that is fine on my side. Thanks!
"Withdrawing the ballot" is supposed to be an active action (so it needs to be requested explicitly IMHO, so I'd prefer to have an explict statement before doing so).
If you plan to send a new version to be voted upon, please just state that you'd like the ballot to be withdrawn. Thanks!
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: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
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/
Quoted 19 lines · Cornelia Huck
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
Quoted 13 lines · Laura Loghin
Quoted 10 lines · Michael S. Tsirkin
If anyone else intends to change their votes, note today is the last opportunity.
Alternatively, Laura, would you consider to address the issues? If you want us to withdraw the ballot to consider the options, that is ok too.
--
MSTHi,
Quoted 8 lines
Quoted 1 line
I sent a message a bit earlier. I plan to address the comments this week. I'm not yet very familiar with the voting process, but if addressing the comments means withdrawing the ballot, that is fine on my side. Thanks!
"Withdrawing the ballot" is supposed to be an active action (so it needs to be requested explicitly IMHO, so I'd prefer to have an explict statement before doing so).
If you plan to send a new version to be voted upon, please just state that you'd like the ballot to be withdrawn. Thanks!
OK, I'd like my ballot to be withdrawn.
Thanks,
Laura
Amazon Development Center (Romania) S.R.L. registered office: 27A Sf. Lazar Street, UBC5, floor 2, Iasi, Iasi County, 700045, Romania. Registered in Romania. Registration number J22/2621/2005.
Quoted 21 lines · Laura Loghin
Quoted 20 lines · Cornelia Huck
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
Quoted 14 lines · Laura Loghin
Quoted 10 lines · Michael S. Tsirkin
If anyone else intends to change their votes, note today is the last opportunity.
Alternatively, Laura, would you consider to address the issues? If you want us to withdraw the ballot to consider the options, that is ok too.
--
MSTHi,
I sent a message a bit earlier. I plan to address the comments this week. I'm not yet very familiar with the voting process, but if addressing the comments means withdrawing the ballot, that is fine on my side. Thanks!
Quoted 8 lines
Quoted 7 lines
"Withdrawing the ballot" is supposed to be an active action (so it needs to be requested explicitly IMHO, so I'd prefer to have an explict statement before doing so).
If you plan to send a new version to be voted upon, please just state that you'd like the ballot to be withdrawn. Thanks!
OK, I'd like my ballot to be withdrawn.
Thanks for the confirmation, I just did that.
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: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
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/
Quoted 32 lines · Halil Pasic
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
Quoted 13 lines · On Mon, 13 Jun 2022 13:40:38 +0300 Laura Loghin<[email protected]> wrote:
virtio-vsock.tex +9
-0@@ -57,6 +62,25 @@ \subsection{Device configuration layout}\label{sec:Device Types / Socket Device \hline \end{tabular} +The following driver-read-only field, \field{data_max_size} only exists if +VIRTIO_VSOCK_F_SIZE_MAX is set. This field specifies the maximum packet payload +size for the driver to use. + +\devicenormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout} + +The device MUST NOT change the value exposed through \field{data_max_size}. + +\drivernormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout}virtio-vsock.tex \subsection{Device configuration layout}\label{sec:Device Types / Socket Device · line 83
Quoted 10 lines
virtio-vsock.tex +10
-0+ +A driver SHOULD negotiate VIRTIO_VSOCK_F_SIZE_MAX if the device offers it. + +If the driver negotiates VIRTIO_VSOCK_F_SIZE_MAX, the receive buffers it +supplies for a packet MUST have a total size that doesn't exceed the size +\field{data_max_size} (plus header length). + +If the driver negotiates VIRTIO_VSOCK_F_SIZE_MAX, it MUST NOT transmit packets +of size exceeding the value of \field{data_max_size} (plus header length). +Hi and sorry for being late to the party!
Quoted 3 lines
I believe I do understand why do we want to put a restriction on the size of the transmitted packets, but I would appreciate if you could explain to me why do we want to limit the receive buffer size.
My initial proposal was having a limit only for the size of the TX packets, but Stefano suggested to add it for RX as well, and I found that okay, since both the RX and TX buffers are provided by the driver, so they are untrusted. This way we would limit the memory allocated for both types of buffers, and consequently for the packets as well.
Quoted 10 lines
Also I find the wording regarding a little bit ambiguous because in a networking context it also makes sense to talk about the size of the receive buffer. I guess hear we are talking about a single virtio buffer (a descriptor chain described potentially non-continuous (or compact in the mathematical sense of the word) which is composed from as many continuous chunks of memory as many descriptors are contained within the descriptor chain). If we are indeed talking about a single virtio buffer, I don't understand the plural. If not, I'm not sure what are we talking about.
Hmm so my understanding when reading the spec was that a virtio buffer is corresponding to a single descriptor (not to a descriptor chain). Did I misunderstand it the whole time? :(
Quoted 5 lines
Also, do we have some sort of packets may not cross virtio buffer boundaries, or even a single packet per single viritio buffer rule for vsock. I did a quick search and could not find any. Did I overlook something? Should we spell this out?
I think the rule would be the same as for the other devices, at least the ones that I know some things about, so I might be wrong with this
assumption: one message or transmission unit (not sure what would be the best word here). e.g. request for block, packet for net/vsock is corresponding to exactly one descriptor chain (so one virtio buffer if you consider a buffer as being a descriptor chain).
Quoted 5 lines
@Michael, Conny: What do you think?
Regards,
Halil
Thanks,
Laura
Amazon Development Center (Romania) S.R.L. registered office: 27A Sf. Lazar Street, UBC5, floor 2, Iasi, Iasi County, 700045, Romania. Registered in Romania. Registration number J22/2621/2005.
Quoted 46 lines · Michael S. Tsirkin
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
Quoted 32 lines · Halil Pasic
Quoted 13 lines · On Mon, 13 Jun 2022 13:40:38 +0300 Laura Loghin<[email protected]> wrote:
virtio-vsock.tex +9
-0@@ -57,6 +62,25 @@ \subsection{Device configuration layout}\label{sec:Device Types / Socket Device \hline \end{tabular} +The following driver-read-only field, \field{data_max_size} only exists if +VIRTIO_VSOCK_F_SIZE_MAX is set. This field specifies the maximum packet payload +size for the driver to use. + +\devicenormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout} + +The device MUST NOT change the value exposed through \field{data_max_size}. + +\drivernormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout}virtio-vsock.tex \subsection{Device configuration layout}\label{sec:Device Types / Socket Device · line 83
Quoted 10 lines
virtio-vsock.tex +10
-0+ +A driver SHOULD negotiate VIRTIO_VSOCK_F_SIZE_MAX if the device offers it. + +If the driver negotiates VIRTIO_VSOCK_F_SIZE_MAX, the receive buffers it +supplies for a packet MUST have a total size that doesn't exceed the size +\field{data_max_size} (plus header length). + +If the driver negotiates VIRTIO_VSOCK_F_SIZE_MAX, it MUST NOT transmit packets +of size exceeding the value of \field{data_max_size} (plus header length). +Hi and sorry for being late to the party!
I believe I do understand why do we want to put a restriction on the size of the transmitted packets, but I would appreciate if you could explain to me why do we want to limit the receive buffer size.
Quoted 9 lines
Also I find the wording regarding a little bit ambiguous because in a networking context it also makes sense to talk about the size of the receive buffer. I guess hear we are talking about a single virtio buffer (a descriptor chain described potentially non-continuous (or compact in the mathematical sense of the word) which is composed from as many continuous chunks of memory as many descriptors are contained within the descriptor chain). If we are indeed talking about a single virtio buffer, I don't understand the plural. If not, I'm not sure what are we talking about.
Quoted 2 lines
I think I agree here, I don't understand the mix of "buffers" and "a packet" either.
The way I was understanding that while reading the spec is that a buffer is corresponding to one descriptor, so a packet will correspond to multiple buffers (like for example in Linux one buffer for the packet header and one buffer for the payload). I wanted to limit the memory allocated by the driver for RX buffers and TX buffers, so that's why I used 'buffers' for RX. Does it make sense or did I misunderstand what was causing the confusion here?
Thanks,
Laura
Quoted 14 lines
I voted "no" on the ballot, though if others feel we should apply as is and fix up later, that is not too bad.
Quoted 9 lines
Also, do we have some sort of packets may not cross virtio buffer boundaries, or even a single packet per single viritio buffer rule for vsock. I did a quick search and could not find any. Did I overlook something? Should we spell this out?
@Michael, Conny: What do you think?
Regards,
Halil
Amazon Development Center (Romania) S.R.L. registered office: 27A Sf. Lazar Street, UBC5, floor 2, Iasi, Iasi County, 700045, Romania. Registered in Romania. Registration number J22/2621/2005.
Quoted 52 lines · Laura Loghin
On 6/16/22 19:40, Michael S. Tsirkin wrote:
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
On Tue, Jun 14, 2022 at 01:57:34PM +0200, Halil Pasic wrote:
On Mon, 13 Jun 2022 13:40:38 +0300
Laura Loghin <[email protected]> wrote:@@ -57,6 +62,25 @@ \subsection{Device configuration layout}\label{sec:Device Types / Socket Device
\hline
\end{tabular}+The following driver-read-only field, \field{data_max_size} only exists if
+VIRTIO_VSOCK_F_SIZE_MAX is set. This field specifies the maximum packet payload
+size for the driver to use.
+
+\devicenormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout} +
+The device MUST NOT change the value exposed through \field{data_max_size}.
+
+\drivernormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout} +
+A driver SHOULD negotiateVIRTIO_VSOCK_F_SIZE_MAXif the device offers it.
+
+If the driver negotiatesVIRTIO_VSOCK_F_SIZE_MAX, the receive buffers it
+supplies for a packet MUST have a total size that doesn't exceed the size
+\field{data_max_size} (plus header length).
+
+If the driver negotiatesVIRTIO_VSOCK_F_SIZE_MAX, it MUST NOT transmit packets
+of size exceeding the value of \field{data_max_size} (plus header length).
+Hi and sorry for being late to the party!
I believe I do understand why do we want to put a restriction on the size of the transmitted packets, but I would appreciate if you could explain to me why do we want to limit the receive buffer size.
Also I find the wording regarding a little bit ambiguous because in a networking context it also makes sense to talk about the size of the receive buffer. I guess hear we are talking about a single virtio buffer (a descriptor chain described potentially non-continuous (or compact in the mathematical sense of the word) which is composed from as many continuous chunks of memory as many descriptors are contained within the descriptor chain). If we are indeed talking about a single virtio buffer, I don't understand the plural. If not, I'm not sure what are we talking about.
Quoted 5 lines
I think I agree here, I don't understand the mix of "buffers" and "a packet" either.
The way I was understanding that while reading the spec is that a buffer is corresponding to one descriptor,
what gave this impression? buffers can use any number of descriptors.
Quoted 9 lines
so a packet will correspond to
multiple buffers (like for example in Linux one buffer for the packet header and one buffer for the payload). I wanted to limit the memory allocated by the driver for RX buffers and TX buffers, so that's why I used 'buffers' for RX. Does it make sense or did I misunderstand what was causing the confusion here?Thanks,
Laura
As above, a buffer can consist of many descriptors. See e.g. Descriptor Chaining.
I think there are places in spec when say "descriptor" and we should fix them to say one or more descriptors.
Quoted 22 lines
I voted "no" on the ballot, though if others feel we should apply as is and fix up later, that is not too bad.
Also, do we have some sort of packets may not cross virtio buffer boundaries, or even a single packet per single viritio buffer rule for vsock. I did a quick search and could not find any. Did I overlook something? Should we spell this out?
@Michael, Conny: What do you think?
Regards,
HalilAmazon Development Center (Romania) S.R.L. registered office: 27A Sf. Lazar Street, UBC5, floor 2, Iasi, Iasi County, 700045, Romania. Registered in Romania. Registration number J22/2621/2005.
Quoted 57 lines · Michael S. Tsirkin
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
Quoted 52 lines · Laura Loghin
On 6/16/22 19:40, Michael S. Tsirkin wrote:
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
On Tue, Jun 14, 2022 at 01:57:34PM +0200, Halil Pasic wrote:
On Mon, 13 Jun 2022 13:40:38 +0300
Laura Loghin<[email protected]> wrote:@@ -57,6 +62,25 @@ \subsection{Device configuration layout}\label{sec:Device Types / Socket Device
\hline
\end{tabular}+The following driver-read-only field, \field{data_max_size} only exists if
+VIRTIO_VSOCK_F_SIZE_MAX is set. This field specifies the maximum packet payload
+size for the driver to use.
+
+\devicenormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout} +
+The device MUST NOT change the value exposed through \field{data_max_size}.
+
+\drivernormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout} +
+A driver SHOULD negotiateVIRTIO_VSOCK_F_SIZE_MAXif the device offers it.
+
+If the driver negotiatesVIRTIO_VSOCK_F_SIZE_MAX, the receive buffers it
+supplies for a packet MUST have a total size that doesn't exceed the size
+\field{data_max_size} (plus header length).
+
+If the driver negotiatesVIRTIO_VSOCK_F_SIZE_MAX, it MUST NOT transmit packets
+of size exceeding the value of \field{data_max_size} (plus header length).
+Hi and sorry for being late to the party!
I believe I do understand why do we want to put a restriction on the size of the transmitted packets, but I would appreciate if you could explain to me why do we want to limit the receive buffer size.
Also I find the wording regarding a little bit ambiguous because in a networking context it also makes sense to talk about the size of the receive buffer. I guess hear we are talking about a single virtio buffer (a descriptor chain described potentially non-continuous (or compact in the mathematical sense of the word) which is composed from as many continuous chunks of memory as many descriptors are contained within the descriptor chain). If we are indeed talking about a single virtio buffer, I don't understand the plural. If not, I'm not sure what are we talking about.
Quoted 7 lines
Quoted 5 lines
I think I agree here, I don't understand the mix of "buffers" and "a packet" either.
The way I was understanding that while reading the spec is that a buffer is corresponding to one descriptor,
what gave this impression? buffers can use any number of descriptors.
There are sections in the spec that make you think of a buffer as corresponding to a descriptor chain, and others that don't, for example:
2.6.5 The Virtqueue Descriptor Table: Each descriptor describes a buffer which is read-only for the device (“device-readable”) or write-only for the device (“device-writable”), but a chain of descriptors can contain both device-readable and device-writable buffers. I remember while reading the spec I was always confused about the buffer
- descriptor (chain) relation, but in the end concluded that the buffer is the memory region to which a single descriptor is pointing to (probably also because when you think of a buffer you would at first assume it is contiguous in memory).
This doesn't seem to be the right understanding, so I will update the patch.
Quoted 7 lines
Quoted 7 lines
so a packet will correspond to
multiple buffers (like for example in Linux one buffer for the packet header and one buffer for the payload). I wanted to limit the memory allocated by the driver for RX buffers and TX buffers, so that's why I used 'buffers' for RX. Does it make sense or did I misunderstand what was causing the confusion here?
Quoted 7 lines
Quoted 2 lines
Thanks,
LauraAs above, a buffer can consist of many descriptors. See e.g. Descriptor Chaining.
I think there are places in spec when say "descriptor" and we should fix them to say one or more descriptors.
It would be great if we could fix the spec, so that the relation between a descriptor and a buffer becomes more clear and doesn't leave room for interpretations.
Laura
Quoted 17 lines
Quoted 17 lines
I voted "no" on the ballot, though if others feel we should apply as is and fix up later, that is not too bad.
Also, do we have some sort of packets may not cross virtio buffer boundaries, or even a single packet per single viritio buffer rule for vsock. I did a quick search and could not find any. Did I overlook something? Should we spell this out?
@Michael, Conny: What do you think?
Regards,
Halil
Quoted 4 lines
Quoted 4 lines
Amazon Development Center (Romania) S.R.L. registered office: 27A Sf. Lazar Street, UBC5, floor 2, Iasi, Iasi County, 700045, Romania. Registered in Romania. Registration number J22/2621/2005.
Amazon Development Center (Romania) S.R.L. registered office: 27A Sf. Lazar Street, UBC5, floor 2, Iasi, Iasi County, 700045, Romania. Registered in Romania. Registration number J22/2621/2005.
Quoted 31 lines · Cornelia Huck
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
Quoted 25 lines · Laura Loghin
Quoted 24 lines · Cornelia Huck
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
Quoted 8 lines · Laura Loghin
Quoted 7 lines · Michael S. Tsirkin
If anyone else intends to change their votes, note today is the last opportunity.
Alternatively, Laura, would you consider to address the issues? If you want us to withdraw the ballot to consider the options, that is ok too.
Quoted 6 lines
Quoted 3 lines
--
MSTHi,
I sent a message a bit earlier. I plan to address the comments this week. I'm not yet very familiar with the voting process, but if addressing the comments means withdrawing the ballot, that is fine on my side. Thanks!
"Withdrawing the ballot" is supposed to be an active action (so it needs to be requested explicitly IMHO, so I'd prefer to have an explict statement before doing so).
Quoted 6 lines
Quoted 4 lines
Quoted 3 lines
If you plan to send a new version to be voted upon, please just state that you'd like the ballot to be withdrawn. Thanks!
OK, I'd like my ballot to be withdrawn.
Thanks for the confirmation, I just did that.
Hello,
I just sent a new version
https://lists.oasis-open.org/archives/virtio-comment/202206/msg00088.html in which I hopefully addressed the outstanding issues. Please have another look!
Laura
Amazon Development Center (Romania) S.R.L. registered office: 27A Sf. Lazar Street, UBC5, floor 2, Iasi, Iasi County, 700045, Romania. Registered in Romania. Registration number J22/2621/2005.
Quoted 65 lines · On Fri, 24 Jun 2022 11:23:31 +0300 Laura Loghin <[email protected]> wrote:
Quoted 57 lines · Michael S. Tsirkin
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
Quoted 52 lines · Laura Loghin
On 6/16/22 19:40, Michael S. Tsirkin wrote:
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
On Tue, Jun 14, 2022 at 01:57:34PM +0200, Halil Pasic wrote:
On Mon, 13 Jun 2022 13:40:38 +0300
Laura Loghin<[email protected]> wrote:@@ -57,6 +62,25 @@ \subsection{Device configuration layout}\label{sec:Device Types / Socket Device
\hline
\end{tabular}+The following driver-read-only field, \field{data_max_size} only exists if
+VIRTIO_VSOCK_F_SIZE_MAX is set. This field specifies the maximum packet payload
+size for the driver to use.
+
+\devicenormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout} +
+The device MUST NOT change the value exposed through \field{data_max_size}.
+
+\drivernormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout} +
+A driver SHOULD negotiateVIRTIO_VSOCK_F_SIZE_MAXif the device offers it.
+
+If the driver negotiatesVIRTIO_VSOCK_F_SIZE_MAX, the receive buffers it
+supplies for a packet MUST have a total size that doesn't exceed the size
+\field{data_max_size} (plus header length).
+
+If the driver negotiatesVIRTIO_VSOCK_F_SIZE_MAX, it MUST NOT transmit packets
+of size exceeding the value of \field{data_max_size} (plus header length).
+Hi and sorry for being late to the party!
I believe I do understand why do we want to put a restriction on the size of the transmitted packets, but I would appreciate if you could explain to me why do we want to limit the receive buffer size.
Also I find the wording regarding a little bit ambiguous because in a networking context it also makes sense to talk about the size of the receive buffer. I guess hear we are talking about a single virtio buffer (a descriptor chain described potentially non-continuous (or compact in the mathematical sense of the word) which is composed from as many continuous chunks of memory as many descriptors are contained within the descriptor chain). If we are indeed talking about a single virtio buffer, I don't understand the plural. If not, I'm not sure what are we talking about.
Quoted 7 lines
Quoted 5 lines
I think I agree here, I don't understand the mix of "buffers" and "a packet" either.
The way I was understanding that while reading the spec is that a buffer is corresponding to one descriptor,
what gave this impression? buffers can use any number of descriptors.
Quoted 11 lines
There are sections in the spec that make you think of a buffer as corresponding to a descriptor chain, and others that don't, for example:
2.6.5 The Virtqueue Descriptor Table: Each descriptor describes a buffer which is read-only for the device (“device-readable”) or write-only for the device (“device-writable”), but a chain of descriptors can contain both device-readable and device-writable buffers. I remember while reading the spec I was always confused about the buffer
- descriptor (chain) relation, but in the end concluded that the buffer is the memory region to which a single descriptor is pointing to (probably also because when you think of a buffer you would at first assume it is contiguous in memory).
I think in the distant past I have pointed out that the usage of the word buffer in the virtio spec is somewhat confusing. But I never took the time to make a patch which attempts to set it strait.
IMHO eve if we were to use "buffer" consistently in a sense that, it is a portion of the RAM which may or may not be continuous in the address space used by virtio (guest physical or DMA depending on ...) where chained descriptors describe continuous pieces of the same, we would still have the problem, that in the normal CS world AFAIK a buffer is usually a continuous piece of memory used for a certain purpose.
https://en.wikipedia.org/wiki/Data_buffer
Well actually our buffers are continuous in a sense that each descriptor chain defines and has an address space of its own. In a sense that we can talk about the N-th byte of the L long buffer (N < L), but that the difference between addresses of the 0-th and the N-th byte of an virtio buffer described by a descriptor chain in DMA/guest physical address space isn't guaranteed to be N.
One solution would be to define the terms:
virtqueue buffer: a portion of a RAM that is composed by one or more primitive buffers and a descriptor chain such that at least one descriptor in the chain is pointed to each primitive buffer primitive buffer: a byte array in RAM which is continuous in the address space used by the spec
and use this terms consistently. That is never use buffer without a qualifier.
BTW I don't remember if the our primitive buffers are allowed to cross page boundaries.
Quoted 13 lines
This doesn't seem to be the right understanding, so I will update the patch.
Quoted 10 lines
Quoted 9 lines
so a packet will correspond to
multiple buffers (like for example in Linux one buffer for the packet header and one buffer for the payload). I wanted to limit the memory allocated by the driver for RX buffers and TX buffers, so that's why I used 'buffers' for RX. Does it make sense or did I misunderstand what was causing the confusion here?Thanks,
Laura
Quoted 8 lines
Quoted 4 lines
As above, a buffer can consist of many descriptors. See e.g. Descriptor Chaining.
I think there are places in spec when say "descriptor" and we should fix them to say one or more descriptors.It would be great if we could fix the spec, so that the relation between a descriptor and a buffer becomes more clear and doesn't leave room for interpretations.
+1
Regards,
Halil
Quoted 29 lines
Laura
Quoted 17 lines
Quoted 17 lines
I voted "no" on the ballot, though if others feel we should apply as is and fix up later, that is not too bad.
Also, do we have some sort of packets may not cross virtio buffer boundaries, or even a single packet per single viritio buffer rule for vsock. I did a quick search and could not find any. Did I overlook something? Should we spell this out?
@Michael, Conny: What do you think?
Regards,
HalilQuoted 4 lines
Quoted 4 lines
Amazon Development Center (Romania) S.R.L. registered office: 27A Sf. Lazar Street, UBC5, floor 2, Iasi, Iasi County, 700045, Romania. Registered in Romania. Registration number J22/2621/2005.
Amazon Development Center (Romania) S.R.L. registered office: 27A Sf. Lazar Street, UBC5, floor 2, Iasi, Iasi County, 700045, Romania. Registered in Romania. Registration number J22/2621/2005.
Quoted 68 lines · Halil Pasic
Quoted 65 lines · On Fri, 24 Jun 2022 11:23:31 +0300 Laura Loghin <[email protected]> wrote:
Quoted 64 lines · Michael S. Tsirkin
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
Quoted 52 lines · Laura Loghin
On 6/16/22 19:40, Michael S. Tsirkin wrote:
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
On Tue, Jun 14, 2022 at 01:57:34PM +0200, Halil Pasic wrote:
On Mon, 13 Jun 2022 13:40:38 +0300
Laura Loghin<[email protected]> wrote:@@ -57,6 +62,25 @@ \subsection{Device configuration layout}\label{sec:Device Types / Socket Device
\hline
\end{tabular}+The following driver-read-only field, \field{data_max_size} only exists if
+VIRTIO_VSOCK_F_SIZE_MAX is set. This field specifies the maximum packet payload
+size for the driver to use.
+
+\devicenormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout} +
+The device MUST NOT change the value exposed through \field{data_max_size}.
+
+\drivernormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout} +
+A driver SHOULD negotiateVIRTIO_VSOCK_F_SIZE_MAXif the device offers it.
+
+If the driver negotiatesVIRTIO_VSOCK_F_SIZE_MAX, the receive buffers it
+supplies for a packet MUST have a total size that doesn't exceed the size
+\field{data_max_size} (plus header length).
+
+If the driver negotiatesVIRTIO_VSOCK_F_SIZE_MAX, it MUST NOT transmit packets
+of size exceeding the value of \field{data_max_size} (plus header length).
+Hi and sorry for being late to the party!
I believe I do understand why do we want to put a restriction on the size of the transmitted packets, but I would appreciate if you could explain to me why do we want to limit the receive buffer size.
Also I find the wording regarding a little bit ambiguous because in a networking context it also makes sense to talk about the size of the receive buffer. I guess hear we are talking about a single virtio buffer (a descriptor chain described potentially non-continuous (or compact in the mathematical sense of the word) which is composed from as many continuous chunks of memory as many descriptors are contained within the descriptor chain). If we are indeed talking about a single virtio buffer, I don't understand the plural. If not, I'm not sure what are we talking about.
Quoted 5 lines
I think I agree here, I don't understand the mix of "buffers" and "a packet" either.
The way I was understanding that while reading the spec is that a buffer is corresponding to one descriptor,
what gave this impression? buffers can use any number of descriptors.
Quoted 11 lines
Quoted 11 lines
There are sections in the spec that make you think of a buffer as corresponding to a descriptor chain, and others that don't, for example:
2.6.5 The Virtqueue Descriptor Table: Each descriptor describes a buffer which is read-only for the device (“device-readable”) or write-only for the device (“device-writable”), but a chain of descriptors can contain both device-readable and device-writable buffers. I remember while reading the spec I was always confused about the buffer
- descriptor (chain) relation, but in the end concluded that the buffer is the memory region to which a single descriptor is pointing to (probably also because when you think of a buffer you would at first assume it is contiguous in memory).
well we have wording like
Device reports the number of bytes it has written to memory for each buffer it uses. This is referred to as ``used length''.
Quoted 19 lines
I think in the distant past I have pointed out that the usage of the word buffer in the virtio spec is somewhat confusing. But I never took the time to make a patch which attempts to set it strait.
IMHO eve if we were to use "buffer" consistently in a sense that, it is a portion of the RAM which may or may not be continuous in the address space used by virtio (guest physical or DMA depending on ...) where chained descriptors describe continuous pieces of the same, we would still have the problem, that in the normal CS world AFAIK a buffer is usually a continuous piece of memory used for a certain purpose.
https://en.wikipedia.org/wiki/Data_bufferWell actually our buffers are continuous in a sense that each descriptor chain defines and has an address space of its own. In a sense that we can talk about the N-th byte of the L long buffer (N < L), but that the difference between addresses of the 0-th and the N-th byte of an virtio buffer described by a descriptor chain in DMA/guest physical address space isn't guaranteed to be N.
Quoted 8 lines
One solution would be to define the terms:
virtqueue buffer: a portion of a RAM that is composed by one or more primitive buffers and a descriptor chain such that at least one descriptor in the chain is pointed to each primitive buffer primitive buffer: a byte array in RAM which is continuous in the address space used by the spec
and use this terms consistently. That is never use buffer without a qualifier.
I would be inclined to avoid saying primitive buffer. saying virtqueue buffer is ok if a bit verbose.
Let's start by locating places in spec which say buffer when they mean descriptor though.
Quoted 3 lines
BTW I don't remember if the our primitive buffers are allowed to cross page boundaries.
Spec doesn't say they shouldn't.
Quoted 56 lines
Quoted 13 lines
This doesn't seem to be the right understanding, so I will update the patch.
Quoted 10 lines
Quoted 9 lines
so a packet will correspond to
multiple buffers (like for example in Linux one buffer for the packet header and one buffer for the payload). I wanted to limit the memory allocated by the driver for RX buffers and TX buffers, so that's why I used 'buffers' for RX. Does it make sense or did I misunderstand what was causing the confusion here?Thanks,
LauraQuoted 8 lines
Quoted 4 lines
As above, a buffer can consist of many descriptors. See e.g. Descriptor Chaining.
I think there are places in spec when say "descriptor" and we should fix them to say one or more descriptors.It would be great if we could fix the spec, so that the relation between a descriptor and a buffer becomes more clear and doesn't leave room for interpretations.
+1
Regards,
HalilQuoted 29 lines
Laura
Quoted 17 lines
Quoted 17 lines
I voted "no" on the ballot, though if others feel we should apply as is and fix up later, that is not too bad.
Also, do we have some sort of packets may not cross virtio buffer boundaries, or even a single packet per single viritio buffer rule for vsock. I did a quick search and could not find any. Did I overlook something? Should we spell this out?
@Michael, Conny: What do you think?
Regards,
HalilQuoted 4 lines
Quoted 4 lines
Amazon Development Center (Romania) S.R.L. registered office: 27A Sf. Lazar Street, UBC5, floor 2, Iasi, Iasi County, 700045, Romania. Registered in Romania. Registration number J22/2621/2005.
Amazon Development Center (Romania) S.R.L. registered office: 27A Sf. Lazar Street, UBC5, floor 2, Iasi, Iasi County, 700045, Romania. Registered in Romania. Registration number J22/2621/2005.
Quoted 84 lines · Michael S. Tsirkin
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
Quoted 68 lines · Halil Pasic
Quoted 65 lines · On Fri, 24 Jun 2022 11:23:31 +0300 Laura Loghin <[email protected]> wrote:
Quoted 64 lines · Michael S. Tsirkin
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
Quoted 52 lines · Laura Loghin
On 6/16/22 19:40, Michael S. Tsirkin wrote:
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
On Tue, Jun 14, 2022 at 01:57:34PM +0200, Halil Pasic wrote:
On Mon, 13 Jun 2022 13:40:38 +0300 Laura Loghin<[email protected]> wrote:
@@ -57,6 +62,25 @@ \subsection{Device configuration layout}\label{sec:Device Types / Socket Device
\hline
\end{tabular}+The following driver-read-only field, \field{data_max_size} only exists if
+VIRTIO_VSOCK_F_SIZE_MAX is set. This field specifies the maximum packet payload
+size for the driver to use.
+
+\devicenormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout} +
+The device MUST NOT change the value exposed through \field{data_max_size}.
+
+\drivernormative{\subsubsection}{Device configuration layout}{Device Types / Socket Device / Device configuration layout} +
+A driver SHOULD negotiateVIRTIO_VSOCK_F_SIZE_MAXif the device offers it.
+
+If the driver negotiatesVIRTIO_VSOCK_F_SIZE_MAX, the receive buffers it
+supplies for a packet MUST have a total size that doesn't exceed the size
+\field{data_max_size} (plus header length).
+
+If the driver negotiatesVIRTIO_VSOCK_F_SIZE_MAX, it MUST NOT transmit packets
+of size exceeding the value of \field{data_max_size} (plus header length).
+Hi and sorry for being late to the party!
I believe I do understand why do we want to put a restriction on the size of the transmitted packets, but I would appreciate if you could explain to me why do we want to limit the receive buffer size.
Also I find the wording regarding a little bit ambiguous because in a networking context it also makes sense to talk about the size of the receive buffer. I guess hear we are talking about a single virtio buffer (a descriptor chain described potentially non-continuous (or compact in the mathematical sense of the word) which is composed from as many continuous chunks of memory as many descriptors are contained within the descriptor chain). If we are indeed talking about a single virtio buffer, I don't understand the plural. If not, I'm not sure what are we talking about.
Quoted 5 lines
I think I agree here, I don't understand the mix of "buffers" and "a packet" either.
The way I was understanding that while reading the spec is that a buffer is corresponding to one descriptor,
what gave this impression? buffers can use any number of descriptors.
Quoted 11 lines
Quoted 11 lines
There are sections in the spec that make you think of a buffer as corresponding to a descriptor chain, and others that don't, for example:
2.6.5 The Virtqueue Descriptor Table: Each descriptor describes a
buffer which is read-only for the device (“device-readable”) or write-only for the device (“device-writable”), but a chain of descriptors can contain both device-readable and device-writable buffers. I remember while reading the spec I was always confused about the buffer
- descriptor (chain) relation, but in the end concluded that the buffer is the memory region to which a single descriptor is pointing to (probably also because when you think of a buffer you would at first assume it is contiguous in memory).
Quoted 4 lines
well we have wording like
Device reports the number of bytes it has written to memory for each buffer it uses. This is referred to as ``used length''.
That's true, there are also sections that make you think of a buffer belonging to the entire descriptor chain. Hopefully once we update the spec, the confusion will no longer be possible.
Quoted 34 lines
Quoted 19 lines
I think in the distant past I have pointed out that the usage of the word buffer in the virtio spec is somewhat confusing. But I never took the time to make a patch which attempts to set it strait.
IMHO eve if we were to use "buffer" consistently in a sense that, it is a portion of the RAM which may or may not be continuous in the address space used by virtio (guest physical or DMA depending on ...) where chained descriptors describe continuous pieces of the same, we would still have the problem, that in the normal CS world AFAIK a buffer is usually a continuous piece of memory used for a certain purpose.
https://en.wikipedia.org/wiki/Data_bufferWell actually our buffers are continuous in a sense that each descriptor chain defines and has an address space of its own. In a sense that we can talk about the N-th byte of the L long buffer (N < L), but that the difference between addresses of the 0-th and the N-th byte of an virtio buffer described by a descriptor chain in DMA/guest physical address space isn't guaranteed to be N.
Quoted 8 lines
One solution would be to define the terms:
virtqueue buffer: a portion of a RAM that is composed by one or more primitive buffers and a descriptor chain such that at least one descriptor in the chain is pointed to each primitive buffer primitive buffer: a byte array in RAM which is continuous in the address space used by the spec
and use this terms consistently. That is never use buffer without a qualifier.I would be inclined to avoid saying primitive buffer. saying virtqueue buffer is ok if a bit verbose.
Let's start by locating places in spec which say buffer when they mean descriptor though.
Quoted 56 lines
Quoted 2 lines
BTW I don't remember if the our primitive buffers are allowed to cross page boundaries.
Spec doesn't say they shouldn't.
Quoted 51 lines
Quoted 12 lines
This doesn't seem to be the right understanding, so I will update the patch.
Quoted 9 lines
Quoted 9 lines
so a packet will correspond to
multiple buffers (like for example in Linux one buffer for the packet header and one buffer for the payload). I wanted to limit the memory allocated by the driver for RX buffers and TX buffers, so that's why I used 'buffers' for RX. Does it make sense or did I misunderstand what was causing the confusion here?Thanks,
LauraQuoted 7 lines
Quoted 4 lines
As above, a buffer can consist of many descriptors. See e.g. Descriptor Chaining.
I think there are places in spec when say "descriptor" and we should fix them to say one or more descriptors.It would be great if we could fix the spec, so that the relation between a descriptor and a buffer becomes more clear and doesn't leave room for interpretations.
+1
Regards,
HalilQuoted 27 lines
Laura
Quoted 17 lines
Quoted 17 lines
I voted "no" on the ballot, though if others feel we should apply as is and fix up later, that is not too bad.
Also, do we have some sort of packets may not cross virtio buffer boundaries, or even a single packet per single viritio buffer rule for vsock. I did a quick search and could not find any. Did I overlook something? Should we spell this out?
@Michael, Conny: What do you think?
Regards,
HalilQuoted 4 lines
Quoted 4 lines
Amazon Development Center (Romania) S.R.L. registered office: 27A Sf. Lazar Street, UBC5, floor 2, Iasi, Iasi County, 700045, Romania. Registered in Romania. Registration number J22/2621/2005.
Amazon Development Center (Romania) S.R.L. registered office: 27A Sf. Lazar Street, UBC5, floor 2, Iasi, Iasi County, 700045, Romania. Registered in Romania. Registration number J22/2621/2005.
Amazon Development Center (Romania) S.R.L. registered office: 27A Sf. Lazar Street, UBC5, floor 2, Iasi, Iasi County, 700045, Romania. Registered in Romania. Registration number J22/2621/2005.
Quoted 6 lines · Laura Loghin
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
There are sections in the spec that make you think of a buffer as corresponding to a descriptor chain, and others that don't, for example:
2.6.5 The Virtqueue Descriptor Table: Each descriptor describes a
buffer which is read-only for the device (“device-readable”) or write-only for the device (“device-writable”), but a chain of descriptors can contain both device-readable and device-writable buffers.
I think this should just refer to memory:
Each descriptor describes
memory which is read-only for the device (``device-readable'') or write-only for the device (``device-writable''), but a chain of descriptors can contain both device-readable and device-writable memory.