qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Yuri Benditovich <yuri.benditovich@daynix.com>
Cc: Markus Armbruster <armbru@redhat.com>,
	Andrew Melnychenko <andrew@daynix.com>,
	jasowang@redhat.com, mst@redhat.com, eblake@redhat.com,
	qemu-devel@nongnu.org, yan@daynix.com
Subject: Re: [PATCH v7 4/5] qmp: Added new command to retrieve eBPF blob.
Date: Mon, 18 Dec 2023 13:32:57 +0000	[thread overview]
Message-ID: <ZYBKCUXlfRerzZmi@redhat.com> (raw)
In-Reply-To: <CAOEp5Oc+6T7yiH2qdO=ZPyDn+d4gO+4KZXmxcRU7DoO3BabPPA@mail.gmail.com>

On Mon, Dec 18, 2023 at 03:24:57PM +0200, Yuri Benditovich wrote:
> On Mon, Dec 18, 2023 at 2:54 PM Markus Armbruster <armbru@redhat.com> wrote:
> > > +#
> > > +# Currently, there is a possible eBPF for receive-side scaling (RSS).
> > > +#
> > > +##
> > > +
> > > +##
> > > +# @EbpfObject:
> > > +#
> > > +# An eBPF ELF object.
> > > +#
> > > +# @object: the eBPF object encoded in base64
> > > +#
> > > +# Since: 8.2
> >
> > Won't make 8.2, so bump to 9.0.  More of the same below, not noting it
> > again.
> >
> 
> Will there be 8.3?

No, there is never a N.3.0

QEMU does three releases per year, and the major version
increments for the first release of the year. So the
pattern is always

  N.0.0, N.1.0, N.2.0

where "N" changes each year.  The last digit is reserved
for stable branch releases.


With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2023-12-18 13:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31  6:51 [PATCH v7 0/5] eBPF RSS through QMP support Andrew Melnychenko
2023-08-31  6:51 ` [PATCH v7 1/5] ebpf: Added eBPF map update through mmap Andrew Melnychenko
2023-12-11 13:05   ` Akihiko Odaki
2023-12-11 13:48     ` Yuri Benditovich
2023-12-11 14:07       ` Akihiko Odaki
2023-12-12  3:35         ` Jason Wang
2023-08-31  6:51 ` [PATCH v7 2/5] ebpf: Added eBPF initialization by fds Andrew Melnychenko
2023-12-11 13:07   ` Akihiko Odaki
2023-08-31  6:51 ` [PATCH v7 3/5] virtio-net: Added property to load eBPF RSS with fds Andrew Melnychenko
2023-12-11 13:17   ` Akihiko Odaki
2023-08-31  6:51 ` [PATCH v7 4/5] qmp: Added new command to retrieve eBPF blob Andrew Melnychenko
2023-12-11 13:30   ` Akihiko Odaki
2023-12-18 12:54   ` Markus Armbruster
2023-12-18 13:24     ` Yuri Benditovich
2023-12-18 13:32       ` Daniel P. Berrangé [this message]
2023-08-31  6:51 ` [PATCH v7 5/5] ebpf: Updated eBPF program and skeleton Andrew Melnychenko
2023-09-04 11:22   ` Andrew Melnichenko
2023-09-08  6:42     ` Jason Wang
2023-12-11 11:50       ` Yuri Benditovich
2023-12-12  3:33         ` Jason Wang
2023-12-13  7:23           ` Yuri Benditovich
2023-12-14 10:17             ` Yuri Benditovich
2023-12-18  2:48               ` Jason Wang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZYBKCUXlfRerzZmi@redhat.com \
    --to=berrange@redhat.com \
    --cc=andrew@daynix.com \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yan@daynix.com \
    --cc=yuri.benditovich@daynix.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).