[virtio-comment] Re: [virtio-dev] Re: [virtio-comment] [PATCH v13] virtio-net: support inner header hash

["Michael S. Tsirkin" <mst@redhat.com>]

On Thu, Apr 27, 2023 at 10:28:29AM +0800, Heng Qi wrote:
> 
> 
> 在 2023/4/26 下午10:48, Michael S. Tsirkin 写道:
> > On Wed, Apr 26, 2023 at 10:14:30PM +0800, Heng Qi wrote:
> > > This does not mean that every device needs to implement and support all of
> > > these, they can choose to support some protocols they want.
> > > 
> > > I add these because we have scale application scenarios for modern protocols
> > > VXLAN-GPE/GENEVE:
> > > 
> > > +\item In scenarios where the same flow passing through different tunnels is expected to be received in the same queue,
> > > +      warm caches, lessing locking, etc. are optimized to obtain receiving performance.
> > > 
> > > 
> > > Maybe the legacy GRE, VXLAN-GPE and GENEVE? But it has a little crossover.
> > > 
> > > Thanks.
> > But VXLAN-GPE/GENEVE can use source port for entropy.
> > 
> > 	It is recommended that the UDP source port number
> > 	 be calculated using a hash of fields from the inner packet
> > 
> > That is best because
> > it allows end to end control and is protocol agnostic.
> 
> Yes. I agree with this, I don't think we have an argument on this point
> right now.:)
> 
> For VXLAN-GPE/GENEVE or other modern tunneling protocols, we have to deal
> with
> scenarios where the same flow passes through different tunnels.
> 
> Having them hashed to the same rx queue, is hard to do via outer headers.
> > All that is missing is symmetric Toepliz and all is well?
> 
> The scenarios above or in the commit log also require inner headers.

Hmm I am not sure I get it 100%.
Could you show an example with inner header hash in the port #,
hash is symmetric, and you still have trouble?


It kinds of sounds like not enough entropy is not the problem
at this point. You now want to drop everything from the header
except the UDP source port. Is that a fair summary?

> 
> 
> 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: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/