From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: virtio-comment-return-941-cohuck=redhat.com@lists.oasis-open.org Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 4C6B6985CAF for ; Mon, 25 Nov 2019 07:33:44 +0000 (UTC) Date: Mon, 25 Nov 2019 02:33:33 -0500 From: "Michael S. Tsirkin" Message-ID: <20191125022719-mutt-send-email-mst@kernel.org> References: <20191101052632-mutt-send-email-mst@kernel.org> <20191110095305-mutt-send-email-mst@kernel.org> <20191111092046-mutt-send-email-mst@kernel.org> <20191120081531-mutt-send-email-mst@kernel.org> <20191124100825-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 In-Reply-To: Subject: [virtio-comment] Re: [EXT] Re: [virtio-comment] Re: [PATCH] virtio-net: Add equal-sized receive buffers feature Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline To: Jason Wang Cc: Vitaly Mireyno , "virtio-comment@lists.oasis-open.org" List-ID: On Mon, Nov 25, 2019 at 11:31:09AM +0800, Jason Wang wrote: >=20 > On 2019/11/24 =E4=B8=8B=E5=8D=8811:30, Michael S. Tsirkin wrote: > > On Sun, Nov 24, 2019 at 03:02:05PM +0000, Vitaly Mireyno wrote: > > >=20 > > > > -----Original Message----- > > > > From: Michael S. Tsirkin > > > > Sent: Wednesday, 20 November, 2019 15:23 > > > > To: Vitaly Mireyno > > > > Cc: Jason Wang ; virtio-comment@lists.oasis- > > > > open.org > > > > Subject: Re: [EXT] Re: [virtio-comment] Re: [PATCH] virtio-net: Add= equal- > > > > sized receive buffers feature > > > >=20 > > > > On Thu, Nov 14, 2019 at 03:49:59PM +0000, Vitaly Mireyno wrote: > > > > >=20 > > > > > > -----Original Message----- > > > > > > From: Michael S. Tsirkin > > > > > > Sent: Monday, 11 November, 2019 17:05 > > > > > > To: Vitaly Mireyno > > > > > > Cc: Jason Wang ; virtio-comment@lists.oasi= s- > > > > > > open.org > > > > > > Subject: Re: [EXT] Re: [virtio-comment] Re: [PATCH] virtio-net:= Add > > > > > > equal- sized receive buffers feature > > > > > >=20 > > > > > > On Mon, Nov 11, 2019 at 01:58:51PM +0000, Vitaly Mireyno wrote: > > > > > > >=20 > > > > > > > > -----Original Message----- > > > > > > > > From: Michael S. Tsirkin > > > > > > > > Sent: Sunday, 10 November, 2019 17:35 > > > > > > > > To: Vitaly Mireyno > > > > > > > > Cc: Jason Wang ; virtio-comment@lists.= oasis- > > > > > > > > open.org > > > > > > > > Subject: Re: [EXT] Re: [virtio-comment] Re: [PATCH] virtio-= net: > > > > > > > > Add > > > > > > > > equal- sized receive buffers feature > > > > > > > >=20 > > > > > > > > On Sun, Nov 10, 2019 at 02:13:14PM +0000, Vitaly Mireyno wr= ote: > > > > > > > > > > -----Original Message----- > > > > > > > > > > From: virtio-comment@lists.oasis-open.org > > > > > > > > > > On Behalf Of Mic= hael S. > > > > > > > > > > Tsirkin > > > > > > > > > > Sent: Tuesday, 5 November, 2019 20:52 > > > > > > > > > > To: Jason Wang > > > > > > > > > > Cc: Vitaly Mireyno ; > > > > > > > > > > virtio-comment@lists.oasis- open.org > > > > > > > > > > Subject: [EXT] Re: [virtio-comment] Re: [PATCH] virtio-= net: Add > > > > > > > > > > equal-sized receive buffers feature > > > > > > > > > >=20 > > > > > > > > > > External Email > > > > > > > > > >=20 > > > > > > > > > > -------------------------------------------------------= -------- > > > > > > > > > > --- > > > > > > > > > > --- > > > > > > > > > > - On Fri, Nov 01, 2019 at 03:22:26PM +0800, Jason Wang = wrote: > > > > > > > > > > > On 2019/11/1 =E4=B8=8B=E5=8D=8812:09, Michael S. Tsir= kin wrote: > > > > > > > > > > > > On Thu, Oct 31, 2019 at 10:46:55AM +0000, Vitaly Mi= reyno wrote: > > > > > > > > > > > > > The feature is limited to receive buffers only. > > > > > > > > > > > > > A driver decides on receive buffer length. The on= ly > > > > > > > > > > > > > limitation is that this > > > > > > > > > > length has to be the same for all receive virtqueue buf= fers. > > > > > > > > > > > > > The driver configures receive buffer length to th= e device > > > > > > > > > > > > > during device > > > > > > > > > > initialization, and the device reads it and may use it = for > > > > > > > > > > optimal > > > > > > operation. > > > > > > > > > > > > > No changes for transmit buffers. > > > > > > > > > > > > >=20 > > > > > > > > > > > > > -----Original Message----- > > > > > > > > > > > > > From: virtio-comment@lists.oasis-open.org > > > > > > > > > > > > > On Behalf O= f Jason > > > > > > > > > > > > > Wang > > > > > > > > > > > > > Sent: Thursday, 31 October, 2019 12:15 > > > > > > > > > > > > > To: Vitaly Mireyno ; > > > > > > > > > > > > > virtio-comment@lists.oasis-open.org > > > > > > > > > > > > > Cc: Michael S. Tsirkin > > > > > > > > > > > > > Subject: [virtio-comment] Re: [PATCH] virtio-net:= Add > > > > > > > > > > > > > equal-sized receive buffers feature > > > > > > > > > > > > >=20 > > > > > > > > > > > > >=20 > > > > > > > > > > > > > On 2019/10/31 =E4=B8=8B=E5=8D=885:23, Vitaly Mire= yno wrote: > > > > > > > > > > > > > > Some devices benefit from working with receive = buffers > > > > > > > > > > > > > > of a > > > > > > > > > > predefined constant length. > > > > > > > > > > > > > > Add a feature for drivers that allocate equal-s= ized > > > > > > > > > > > > > > receive buffers, and > > > > > > > > > > devices that benefit from predefined receive buffers le= ngth. > > > > > > > > > > > > > > Signed-off-by: Vitaly Mireyno > > > > > > > > > > > > > > --- > > > > > > > > > > > > > > content.tex | 29 ++++++++++++++++++++++++++= +-- > > > > > > > > > > > > > > 1 file changed, 27 insertions(+), 2 deletio= ns(-) > > > > > > > > > > > > > Is there any other networking device that has thi= s feature? > > > > > > > > > > > > >=20 > > > > > > > > > > > > >=20 > > > > > > > > > > > > > > diff --git a/content.tex b/content.tex index > > > > > > > > > > > > > > b1ea9b9..c9e67c8 > > > > > > > > > > > > > > 100644 > > > > > > > > > > > > > > --- a/content.tex > > > > > > > > > > > > > > +++ b/content.tex > > > > > > > > > > > > > > @@ -2811,6 +2811,10 @@ \subsection{Feature > > > > > > > > > > > > > > bits}\label{sec:Device > > > > > > > > > > Types / Network Device / Feature bits > > > > > > > > > > > > > > \item[VIRTIO_NET_F_CTRL_MAC_ADDR(23)] Set M= AC > > > > > > > > > > > > > > address > > > > > > > > > > through control > > > > > > > > > > > > > > channel. > > > > > > > > > > > > > > +\item[VIRTIO_NET_F_CONST_RXBUF_LEN(58)] Driver > > > > > > > > > > > > > > +allocates all > > > > > > > > > > receive buffers > > > > > > > > > > > > > > + of the same constant length. Device benefi= ts from > > > > > > > > > > > > > > + working > > > > > > with > > > > > > > > > > > > > > + receive buffers of equal length. > > > > > > > > > > > > > > + > > > > > > > > > > > > Problem is, I don't think linux will use this for s= kbs > > > > > > > > > > > > since it breaks buffer accounting. This is because = it is > > > > > > > > > > > > important to make skbs as small as you can. So even= if you > > > > > > > > > > > > see "device would > > > > > > benefit" > > > > > > > > > > > > there is no way to balance this with the benefit to= linux. > > > > > > > > > > > > How do you know which benefit is bigger? > > > > > > > > > > >=20 > > > > > > > > > > > I guess the idea is e.g for Linux driver, it can refu= se this feature. > > > > > > > > > > Okay. What uses it? > > > > > > > > > >=20 > > > > > > > > > > > > You also never explained how does device benefit. M= y guess > > > > > > > > > > > > is this allows device to calculate the # of descrip= tors to > > > > > > > > > > > > fetch that are needed for a packet. Right? > > > > > > > > > > > > Assuming this, I think a rough estimate should be e= nough. > > > > > > > > > > > > If device fetches too much it can discard extra, if= it does > > > > > > > > > > > > not fetch enough it can fetch extra. > > > > > > > > > > > >=20 > > > > > > > > > > > > Let us not forget that express packets are 256 byte= s so up > > > > > > > > > > > > to > > > > > > > > > > > > 16 descriptors fit in a packet, there is no benefit= most of > > > > > > > > > > > > the time in knowing whether e.g. 1 or 2 descriptors= are needed. > > > > > > > > > > > >=20 > > > > > > > > > > > >=20 > > > > > > > > > > > > Let us not forget these are buffers, not descriptor= s. > > > > > > > > > > >=20 > > > > > > > > > > > I guess maybe the initial motivation is constant desc= riptor length. > > > > > > > > > >=20 > > > > > > > > > > That conflicts with requirement framing is up to driver= . > > > > > > > > > >=20 > > > > > > > > > >=20 > > > > > > > > > I was using the wrong terminology. The feature is about c= onstant > > > > > > > > *descriptor* length. In other words, the value that driver = puts in > > > > > > > > Packed Virtqueue "Element Length" field (or 'len' field in = the > > > > 'pvirtq_desc' > > > > > > struct). > > > > > > > > OK so this conflicts with "2.6.4 Message Framing" which req= uires > > > > > > > > that drivers can split buffers into as many descriptors as = they like. > > > > > > > > Right? > > > > > > > >=20 > > > > > > > > > Does it make more sense now, or you still see an issue wi= th Linux > > > > driver? > > > > > > > > I think there's an issue with the flexible framing requirem= ents > > > > > > > > and there's an issue with Linux driver. > > > > > > > >=20 > > > > > > > > > The motivation is to allow the device to calculate the ex= act > > > > > > > > > number of > > > > > > > > descriptors to consume, before fetching the descriptors. Th= is is > > > > > > > > beneficial for devices for which overconsuming or undercons= uming > > > > > > > > descriptors come at a high cost. > > > > > > > >=20 > > > > > > > > So I guess we can agree getting the # of descriptors *exact= ly* > > > > > > > > right isn't all that important. Right? My question is how d= oes the > > > > > > > > driver balance the device versus Linux needs? > > > > > > > >=20 > > > > > > > > One idea is if we assume this is best effort, does not have= to be > > > > > > > > exact, then how about just having the device assume descrip= tor > > > > > > > > sizes stay more or less constant and use that to estimate t= he > > > > > > > > amount? If it under/over estimates, things just go a bit sl= ower. > > > > > > > > This way driver can adjust the sizes and device will react > > > > > > > > automatically, with time. > > > > > > > >=20 > > > > > > > >=20 > > > > > > > I see that "2.6.4 Message Framing" allows a full flexibility = of > > > > > > > descriptor lengths, and I presume it's applicable to Packet > > > > > > > Virtqueues as well, though defined under Split Virtqueues sec= tion. > > > > > > That's a good point. Probably makes sense to move it out to a c= ommon > > > > > > section, right? > > > > > >=20 > > > > > > > The example > > > > > > > talks about transmit virtqueue, and it makes perfect sense. > > > > > > > However, wouldn't a typical driver place equal-sized *receive= * > > > > > > > descriptors > > > > > > anyway? So if a device can benefit from it, the driver might as= well > > > > > > negotiate this new feature. > > > > > >=20 > > > > > > Having buffer size jump around wildly doesn't seem too useful, = I agree. > > > > > > OTOH being able to adjust it gradually has been in the past > > > > > > demontrated to help performance measureably. > > > > > >=20 > > > > > > > This could be especially relevant for devices, for which adju= sting > > > > > > > the number > > > > > > of used descriptors is impractical after descriptors have alrea= dy been > > > > fetched. > > > > > > > I agree that if this requirement conflicts with specific driv= er > > > > > > > needs, it will not > > > > > > be negotiated, and the device will either underperform in certa= in > > > > > > scenarios, or will not come up at all. > > > > > >=20 > > > > > > Right so that makes it a challenge. Device says it prefers fixe= d > > > > > > buffers. Is that preference more or less important than ability= to > > > > > > efficiently support workloads such as TCP small queues? > > > > > > Driver has no idea and I suspect neither does the device. > > > > > > So I don't see how will a Linux driver know that it should enab= le > > > > > > this, neither how will device know it's okay to just refuse fea= tures_ok. > > > > > >=20 > > > > > >=20 > > > > > > On the other hand, current drivers already have logic that trie= s to > > > > > > change buffer sizes in a smooth way. So simply caching the las= t > > > > > > buffer size and assuming all the others will be exactly the sam= e will > > > > > > go a long way towards limiting how much does device need to fet= ch. > > > > > > This does imply extra logic on the device to recover if things = change > > > > > > and the first read did not fetch enough buffers, but then it wo= uld be > > > > > > required anyway if as you say above the failure is not catastro= phic. > > > > > >=20 > > > > > >=20 > > > > > > The feature thus only seems useful for small, feature-restraine= d > > > > > > devices > > > > > > - which are prepared to sacrifice some performance to cut costs= , and > > > > > > which can't recover at all. Is this what you are trying to do? > > > > > >=20 > > > > > The intention is to enable devices with this specific limitation = to > > > > > offer virtio offload. The feature can be redefined such that it = would > > > > > only be offered by devices that are unable to handle dynamically > > > > > changing descriptor lengths. How does that sound? > > > > So it makes more sense when mergeable buffers are disabled (since t= hen > > > > buffers are practically all same size). > > > >=20 > > > Actually, mergeable buffers are not a problem. They could be enabled, > > > as long as each descriptor is the same length. So implementations tha= t > > > prefer optimizing memory utilization over jumbo frame performance can > > > negotiate VIRTIO_NET_F_MRG_RXBUF and allocate smaller buffers. > > So my point was, without VIRTIO_NET_F_MRG_RXBUF, all buffers are same > > length anyway. So if we are talking about cheap simple hardware, I gues= s > > it can just not have VIRTIO_NET_F_MRG_RXBUF and be done with it? > > If device does care about memory utilization then I think > > it needs to give driver the flexibility it needs/uses. > > No? > >=20 > > Again I can see how we might want to disallow crazy setups with e.g. 1 > > byte per buffer. That's just abuse, no guest does that anyway. So askin= g > > e.g. for a minimal buffer size sounds very reasonable. >=20 >=20 > One question here is that, the minimal buffer size should depends on vari= ous > factors. E.g the ring size. Consider a 256 entries ring, the minimal size > should be 64K/256=3D256 ... I guess you are right. We can make this driver programmable I guess? Basically pass min_buf_len to the device. >=20 > > But an option that > > disables functionality that a popular guest uses needs a lot of > > documentation to help device writers figure out whether they want that > > option or not, and I'd worry that even with documentation will be > > misunderstood even if we write it. When do you enable this? > > When you don't care about performance? When you don't care about Linux? >=20 >=20 > It looks to me the feature proposal here is something related to the > descriptor pre fetching. In the case of packed virtqueue. Having > avail/producer index may help more or less here? >=20 > Thanks Isn't this addressed by VIRTIO_F_NOTIFICATION_DATA? At least that's one of the things it's supposed to do ... >=20 > >=20 > > > > With that in mind, I have an idea: scsi and block already have max = sg field. > > > > How about we add a writeable max sg field, maybe even make it > > > > programmable per vq? > > > >=20 > > > > Thus driver tells device what is it's max s/g value for rx. Worst c= ase device > > > > fetches a bit more than it needs. Discarding extra shouldn't be exp= ensive. This > > > > looks like it will help even smart devices. What do you think? > > > >=20 > > > > This nicely avoids conflicting with the flexible framing requiremen= t. > > > >=20 > > > My intention was to avoid any descriptor length variations, for > > > devices that unable fetching or discarding extra descriptors. (If in > > > the pipelined HW processing the decision on number of descriptors is > > > made in the early stage, and it cannot be undone in a later stage). > > Frankly discarding unused descriptors looks to me like something that > > shouldn't have a high cost in the hardware. I can see how trying to > > predict descriptor length, and fetching extra if not enough was fetched > > can have a high cost, so to me extensions to remove the guesswork > > from the device have value. However a lot of effort went into trying t= o > > reduce e.g. number of pci express packets needed to fetch descriptors. > > Each packet fetches 256 bytes anyway, does it not? Not having an > > ability to use that information seems like an obvious waste, and that > > means ability to keep some fetched descriptors around even if they are > > not used for a given packet. Again just my $.02. > >=20 > > > Defining max s/g sounds like an interesting feature by itself. > > But assuming we have max RX s/g, I guess hardware can set max s/g =3D 1= ? > > Then since with !VIRTIO_NET_F_MRG_RXBUF all buffers are forced to > > be same length. > >=20 > > > > > > > Could you specify what issue do you see with the Linux driver= ? > > > > > > See logic around struct ewma. > > > > > >=20 > > > > > > The first relevant commit is I guess > > > > > > commit ab7db91705e95ed1bba1304388936fccfa58c992 > > > > > > virtio-net: auto-tune mergeable rx buffer size for improved > > > > > > performance > > > > > >=20 > > > > > > this claims a gain of about 10% with large packets which isn't = earth > > > > > > shattering but also not something we can ignore completely. And= I > > > > > > suspect it can be bigger with smaller packets. > > > > > >=20 > > > > > > > > > > > > So device does not really know the exact # of descr= iptors: > > > > > > > > > > > > current drivers do 1 descriptor per buffer but noth= ing > > > > > > > > > > > > prevents more. > > > > > > > > > > > >=20 > > > > > > > > > > > >=20 > > > > > > > > > > > > Thoughts? > > > > > > > > > > > >=20 > > > > > > > > > > > >=20 > > > > > > > > > > > > > > \item[VIRTIO_NET_F_RSC_EXT(61)] Device can = process > > > > > > > > > > > > > > duplicated > > > > > > > > > > ACKs > > > > > > > > > > > > > > and report number of coalesced segments= and > > > > > > > > > > > > > > duplicated ACKs @@ -2854,8 +2858,8 @@ > > > > > > \subsubsection{Legacy Interface: > > > > > > > > > > Feature bits}\label{sec:Device Types / Network > > > > > > > > > > > > > > \subsection{Device configuration > > > > > > > > > > > > > > layout}\label{sec:Device Types / > > > > > > > > > > Network Device / Device configuration layout} > > > > > > > > > > > > > > \label{sec:Device Types / Block Device / Fe= ature > > > > > > > > > > > > > > bits / Device configuration layout} -Three > > > > > > > > > > > > > > driver-read-only configuration fields are curre= ntly defined. > > > > > > > > > > > > > > The \field{mac} address field -always exists (t= hough is > > > > > > > > > > > > > > only valid if VIRTIO_NET_F_MAC is set), and > > > > > > > > > > > > > > +The driver-read-only \field{mac} address field= always > > > > > > > > > > > > > > +exists (though is only valid if VIRTIO_NET_F_M= AC is > > > > > > > > > > > > > > +set), and > > > > > > > > > > > > > > \field{status} only exists if VIRTIO_NET_F_= STATUS is set. > > > > Two > > > > > > > > > > > > > > read-only bits (for the driver) are current= ly > > > > > > > > > > > > > > defined for the status > > > > > > > > > > field: > > > > > > > > > > > > > > VIRTIO_NET_S_LINK_UP and VIRTIO_NET_S_ANNOU= NCE. > > > > > > > > > > > > > > @@ -2875,12 +2879,17 @@ \subsection{Device > > > > > > > > > > > > > > configuration > > > > > > > > > > layout}\label{sec:Device Types / Network Device > > > > > > > > > > > > > > VIRTIO_NET_F_MTU is set. This field specifi= es the > > > > > > > > > > > > > > maximum MTU for > > > > > > > > > > the driver to > > > > > > > > > > > > > > use. > > > > > > > > > > > > > > +The device-read-only field \field{rx_buf_len} = only > > > > > > > > > > > > > > +exists if > > > > > > > > > > > > > Should be driver-read-only. > > > > > > > > > > > > >=20 > > > > > > > > > > > > >=20 > > > > > > > > > > > > > > +VIRTIO_NET_F_CONST_RXBUF_LEN is negotiated. Th= is field > > > > > > > > > > > > > > +specifies the receive buffers length. > > > > > > > > > > > > > > + > > > > > > > > > > > > > > \begin{lstlisting} > > > > > > > > > > > > > > struct virtio_net_config { > > > > > > > > > > > > > > u8 mac[6]; > > > > > > > > > > > > > > le16 status; > > > > > > > > > > > > > > le16 max_virtqueue_pairs; > > > > > > > > > > > > > > le16 mtu; > > > > > > > > > > > > > > + le32 rx_buf_len; > > > > > > > > > > > > > > }; > > > > > > > > > > > > > > \end{lstlisting} > > > > > > > > > > > > > > @@ -2933,6 +2942,13 @@ \subsection{Device confi= guration > > > > > > > > > > > > > > layout}\label{sec:Device Types / Network Device > > > > > > > > > > > > > > A driver SHOULD negotiate the VIRTIO_NET_F_= STANDBY > > > > > > > > > > > > > > feature if > > > > > > > > > > the device offers it. > > > > > > > > > > > > > > +A driver SHOULD accept the > > > > > > VIRTIO_NET_F_CONST_RXBUF_LEN > > > > > > > > > > feature if offered. > > > > > > > > > > > > > > + > > > > > > > > > > > > > > +If VIRTIO_NET_F_CONST_RXBUF_LEN feature has be= en > > > > > > > > negotiated, > > > > > > > > > > > > > > +the driver MUST set \field{rx_buf_len}. > > > > > > > > > > > > > I think it's device that set the field? > > > > > > > > > > > > Makes more sense for the driver, but if you want th= is set e.g. > > > > > > > > > > > > before buffers are added, you must say so. > > > > > > > > > > > >=20 > > > > > > > > > > > > > > + > > > > > > > > > > > > > > +A driver MUST NOT modify \field{rx_buf_len} on= ce it > > > > > > > > > > > > > > +has been > > > > > > > > set. > > > > > > > > > > > > > > + > > > > > > > > > > > > This seems very unflexible. I can see how e.g. XDP = would > > > > > > > > > > > > benefit from big buffers while skbs benefit from sm= all buffers. > > > > > > > > > > > >=20 > > > > > > > > > > > > This calls for ability to change this. > > > > > > > > > > >=20 > > > > > > > > > > > Yes, but it requires non trivial cleanups for the old= length > > > > > > > > > > > and place them with new ones. > > > > > > > > > > >=20 > > > > > > > > > > > Thanks > > > > > > > > > >=20 > > > > > > > > > > Let's see: > > > > > > > > > > 1=09- making buffer smaller: just update config space, > > > > > > > > > > =09 then make new buffers smaller > > > > > > > > > >=20 > > > > > > > > > > 2=09- making buffers bigger: add larger buffers, > > > > > > > > > > =09once all small ones are consumed update config space > > > > > > > > > >=20 > > > > > > > > > > 2 is tricky I agree. Thoughts? > > > > > > > > > >=20 > > > > > > > > > >=20 > > > > > > > > > Agree. It's doable, provided that the driver will follow = the > > > > > > > > > update > > > > > > > > procedure. > > > > > > > > > > > > > > \subsubsection{Legacy Interface: Device > > > > > > > > > > > > > > configuration > > > > > > > > > > layout}\label{sec:Device Types / Network Device / Devic= e > > > > > > > > > > configuration layout / Legacy Interface: Device configu= ration > > > > > > > > > > layout} > > > > > > > > > > > > > > \label{sec:Device Types / Block Device / Fe= ature > > > > > > > > > > > > > > bits / Device > > > > > > > > > > configuration layout / Legacy Interface: Device configu= ration > > > > > > > > > > layout} > > > > > > > > > > > > > > When using the legacy interface, transition= al > > > > > > > > > > > > > > devices and drivers @@ > > > > > > > > > > > > > > -3241,6 +3257,11 @@ \subsubsection{Setting Up R= eceive > > > > > > > > > > Buffers}\label{sec:Device Types / Network Devi > > > > > > > > > > > > > > If VIRTIO_NET_F_MQ is negotiated, each of > > > > > > > > > > > > > > receiveq1\ldots > > > > > > > > > > receiveqN > > > > > > > > > > > > > > that will be used SHOULD be populated with = receive > > > > buffers. > > > > > > > > > > > > > > +If VIRTIO_NET_F_CONST_RXBUF_LEN feature has be= en > > > > > > > > negotiated, > > > > > > > > > > > > > > +the driver MUST initialize all receive virtque= ue > > > > > > > > > > > > > > +descriptors \field{len} field with the value > > > > > > > > > > > > > > +configured in \field{rx_buf_len} device config= uration > > > > > > > > > > > > > > +field, and allocate receive > > > > > > > > > > buffers accordingly. > > > > > > > > > > > > > > + > > > > > > > > > > > > > > \devicenormative{\paragraph}{Setting Up Rec= eive > > > > > > > > > > > > > > Buffers}{Device Types / Network Device / Device > > > > > > > > > > > > > > Operation / Setting Up Receive Buffers} > > > > > > > > > > > > > > The device MUST set \field{num_buffers} to = the > > > > > > > > > > > > > > number of descriptors used to @@ -3396,6 +3417,= 10 @@ > > > > > > > > > > \subsubsection{Processing of Incoming Packets}\label{se= c:Device > > > > > > > > > > Types / Network > > > > > > > > > > > > > > checksum (in case of multiple encapsulated > > > > > > > > > > > > > > protocols, one > > > > > > level > > > > > > > > > > > > > > of checksums is validated). > > > > > > > > > > > > > > +If VIRTIO_NET_F_CONST_RXBUF_LEN has been negot= iated, > > > > > > the > > > > > > > > > > device > > > > > > > > > > > > > > +MAY use \field{rx_buf_len} as a buffer length = (instead > > > > > > > > > > > > > > +of reading it from virtqueue descriptor \field= {len} field). > > > > > > > > > > > > > Is this safe? What if driver submit a small buffe= r, then > > > > > > > > > > > > > device can read > > > > > > > > > > more than what is allowed? > > > > > > > > > > > > > Thanks > > > > > > > > > > > > >=20 > > > > > > > > > > > > >=20 > > > > > > > > > > > > > > + > > > > > > > > > > > > > > \drivernormative{\paragraph}{Processing of = Incoming > > > > > > > > > > > > > > Packets}{Device Types / Network Device / De= vice Operation > > > > / > > > > > > > > > > > > > > Processing of Incoming Packets} This publicly archived list offers a means to provide input to the=0D OASIS Virtual I/O Device (VIRTIO) TC.=0D =0D In order to verify user consent to the Feedback License terms and=0D to minimize spam in the list archive, subscription is required=0D before posting.=0D =0D Subscribe: virtio-comment-subscribe@lists.oasis-open.org=0D Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org=0D List help: virtio-comment-help@lists.oasis-open.org=0D List archive: https://lists.oasis-open.org/archives/virtio-comment/=0D Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf= =0D List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lis= ts=0D Committee: https://www.oasis-open.org/committees/virtio/=0D Join OASIS: https://www.oasis-open.org/join/