search for: victork

This set of two patches adds a new field called default_mtu to the configuration area of network devices. The motivation is to allow libvirt to set initial MTU different from 1500 on guests virtual NICs. We also propose to use this new field to report MTU changes by the guest OS to the device to facilitate debugging and mtu tunning. The first patch just clarify the definition of existing fields

This set of two patches adds a new field called default_mtu to the configuration area of network devices. The motivation is to allow libvirt to set initial MTU different from 1500 on guests virtual NICs. We also propose to use this new field to report MTU changes by the guest OS to the device to facilitate debugging and mtu tunning. The first patch just clarify the definition of existing fields

...w MTU is assigned by the guest OS. > > In addition, in order to support backward and forward > compatibility, we introduce a new feature bit called > VIRTIO_NET_F_DEFAULT_MTU. > > Added conformance statements for a device and a driver. > > Signed-off-by: Victor Kaplansky <victork at redhat.com> > > Signed-off-by: Victor Kaplansky <victork at redhat.com> > --- > content.tex | 25 +++++++++++++++++++++++++ > 1 file changed, 25 insertions(+) > > diff --git a/content.tex b/content.tex > index 342183b..439d005 100644 > --- a/content.tex &...

...d description is > > vague about configuration layout and fields offsets when some of > > the fields are non valid. > > > > Also clarify that validity of two status bits depends on two > > different feature flags. > > > > Signed-off-by: Victor Kaplansky <victork at redhat.com> > > --- > > + > > +\item [\field{max_virtqueue_pairs}] tells the driver the maximum > > + number of each of virtqueues (receiveq1\ldots receiveqN and > > + transmitq1\ldots transmitqN respectively) that can be configured > > + on the de...

...d description is > > vague about configuration layout and fields offsets when some of > > the fields are non valid. > > > > Also clarify that validity of two status bits depends on two > > different feature flags. > > > > Signed-off-by: Victor Kaplansky <victork at redhat.com> > > --- > > + > > +\item [\field{max_virtqueue_pairs}] tells the driver the maximum > > + number of each of virtqueues (receiveq1\ldots receiveqN and > > + transmitq1\ldots transmitqN respectively) that can be configured > > + on the de...

...the mac, status and max_virtqueue_pairs fields. Specifically, the old description is vague about configuration layout and fields offsets when some of the fields are non valid. Also clarify that validity of two status bits depends on two different feature flags. Signed-off-by: Victor Kaplansky <victork at redhat.com> --- content.tex | 42 +++++++++++++++++++++++++++++++----------- 1 file changed, 31 insertions(+), 11 deletions(-) diff --git a/content.tex b/content.tex index d989d98..342183b 100644 --- a/content.tex +++ b/content.tex @@ -3115,23 +3115,14 @@ were needed. \subsection{Device co...

...U from driver to the device when a new MTU is assigned by the guest OS. In addition, in order to support backward and forward compatibility, we introduce a new feature bit called VIRTIO_NET_F_DEFAULT_MTU. Added conformance statements for a device and a driver. Signed-off-by: Victor Kaplansky <victork at redhat.com> Signed-off-by: Victor Kaplansky <victork at redhat.com> --- content.tex | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/content.tex b/content.tex index 342183b..439d005 100644 --- a/content.tex +++ b/content.tex @@ -3078,6 +3078,12 @@ fea...

...>> vague about configuration layout and fields offsets when some of >>> the fields are non valid. >>> >>> Also clarify that validity of two status bits depends on two >>> different feature flags. >>> >>> Signed-off-by: Victor Kaplansky <victork at redhat.com> >>> --- >>> + >>> +\item [\field{max_virtqueue_pairs}] tells the driver the maximum >>> + number of each of virtqueues (receiveq1\ldots receiveqN and >>> + transmitq1\ldots transmitqN respectively) that can be configured >>&...

..._pairs fields. Specifically, the old description is > vague about configuration layout and fields offsets when some of > the fields are non valid. > > Also clarify that validity of two status bits depends on two > different feature flags. > > Signed-off-by: Victor Kaplansky <victork at redhat.com> > --- > content.tex | 42 +++++++++++++++++++++++++++++++----------- > 1 file changed, 31 insertions(+), 11 deletions(-) > > diff --git a/content.tex b/content.tex > index d989d98..342183b 100644 > --- a/content.tex > +++ b/content.tex > @@ -3115,23 +31...

On Mon, Aug 17, 2015 at 11:07:15AM +0800, Jason Wang wrote: > > > On 08/16/2015 09:42 PM, Victor Kaplansky wrote: > > @@ -3128,6 +3134,7 @@ struct virtio_net_config { > > u8 mac[6]; > > le16 status; > > le16 max_virtqueue_pairs; > > + le16 default_mtu; > > Looks like "mtu" is ok, consider we use

On Mon, Aug 17, 2015 at 11:07:15AM +0800, Jason Wang wrote: > > > On 08/16/2015 09:42 PM, Victor Kaplansky wrote: > > @@ -3128,6 +3134,7 @@ struct virtio_net_config { > > u8 mac[6]; > > le16 status; > > le16 max_virtqueue_pairs; > > + le16 default_mtu; > > Looks like "mtu" is ok, consider we use