virtio — archive

[PATCH requirements 0/7] virtio net new features requirements

From: Michael S. Tsirkin <[email protected]>
To: [email protected]
Date: Tue, 13 Jun 2023 08:58:00 -0000

On Mon, Jun 12, 2023 at 05:26:04PM +0000, Parav Pandit wrote: > > > From: Heng Qi <[email protected]> > > 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 Pls note a bunch of people are traveling to kvm forum, I'd add a couple of weeks. > 2. Design and its review to finish by July-30 > 3. Spec to review by Aug-30 Wait a second are we talking about 1.4 or 1.3? For 1.3 indeed we need to wrap development up by end of summer - our charter is to produce releases every 12 to 16 months, previous one was July 1st, 2022. > > 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? > We should work on finite requirements that we can converge and deliver. > 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". >