Re: [virtio-comment] RE: [virtio] RE: [virtio-comment] [PATCH requirements 5/7] net-features: Add n-tuple receive flow steering requirements

[Heng Qi <hengqi@linux.alibaba.com>]

å 2023/6/13 äå1:26, Parav Pandit åé:
> > From: Heng Qi <hengqi@linux.alibaba.com>
> > Sent: Monday, June 12, 2023 10:35 AM
> > > I will update this details in the v1.
> > Hi, Parav.
> >
> > Do we have a work schedule for the 1.4 features?
> Since n-tuple requirements are straightforward, below is timeline in mind,
> 1. Requirements agree and drafted by June-30
> 2. Design and its review to finish by July-30
> 3. Spec to review by Aug-30

OK, is this timeline for all 1.4 features or individual high priority 
1.4 features?
Do we have a prioritization of 1.4 features? This also facilitates time 
investment for community maintainers.

> > For example, the flow director we are very concerned about recently, because
> > different scenarios have requirements for it.
> >
> > We'd like to work out with you a rough timeline so we can discuss and
> > collaborate better!
> Will above timeline workable for you to work together on it?

This timeline is ok for us. In addition, if it is difficult for the 
community to carry the VF id or there is an unclear
demarcation problem with the design of the group owner management, 
maybe we can skip this first (In any
case, it depends on the opinion of the virtio community).

> We should work on finite requirements that we can converge and deliver.

Yes. Agree.

> First draft was this v0 one.
>
> Otherwise, it can be never ending list that doesn't reach anywhere as steering technology keeps improving.
>
> Slightly unrelated to question, let's call this feature as: "receive flow filters", instead of "flow director".

OK, here's our previous agreement.

Thanks!