From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Lieven <pl@kamp.de>
Cc: kwolf@redhat.com, qemu-block@nongnu.org, ct@flyingcircus.io,
qemu-devel@nongnu.org, mreitz@redhat.com, pbonzini@redhat.com,
dillaman@redhat.com
Subject: Re: [PATCH V2 1/7] block/rbd: bump librbd requirement to luminous release
Date: Mon, 15 Feb 2021 11:51:14 +0000 [thread overview]
Message-ID: <20210215115114.GE1542881@redhat.com> (raw)
In-Reply-To: <5cc0ff5a-5360-5d81-2da9-724a2baf9f6d@kamp.de>
On Mon, Feb 15, 2021 at 12:45:01PM +0100, Peter Lieven wrote:
> Am 15.02.21 um 12:41 schrieb Daniel P. Berrangé:
> > On Mon, Feb 15, 2021 at 12:32:24PM +0100, Peter Lieven wrote:
> > > Am 15.02.21 um 11:24 schrieb Daniel P. Berrangé:
> > > > On Tue, Jan 26, 2021 at 12:25:34PM +0100, Peter Lieven wrote:
> > > > > even luminous (version 12.2) is unmaintained for over 3 years now.
> > > > > Bump the requirement to get rid of the ifdef'ry in the code.
> > > > We have clear rules on when we bump minimum versions, determined by
> > > > the OS platforms we target:
> > > >
> > > > https://qemu.readthedocs.io/en/latest/system/build-platforms.html
> > > >
> > > > At this time RHEL-7 is usually the oldest platform, and it
> > > > builds with RBD 10.2.5, so we can't bump the version to 12.2.
> > > >
> > > > I'm afraid this patch has to be dropped.
> > >
> > > I have asked exactly this question before I started work on this series and got reply
> > >
> > > from Jason that he sees no problem in bumping to a release which is already unmaintained
> > >
> > > for 3 years.
> > I'm afraid Jason is wrong here. It doesn't matter what the upstream
> > consider the support status to be. QEMU targets what the OS vendors
> > ship, and they still consider this to be a supported version.
>
>
> Okay, but the whole coroutine stuff would get a total mess with all the ifdef'ry.
Doesn't seem like the write zeros code is adding much more comapred to
the ifdefs that already exist...
> Would it be an option to make a big ifdef in the rbd driver? One with old code for < 12.0.0 and one
>
> with new code for >= 12.0.0?
..but I don't have a strong opinion on that, since I'm not maintaining this
driver.
BTW, we will be free to drop RHEL-7 in the next development cycle of
QEMU, starting after the forthcoming 6.0.0 release is out, as it will
fall out of our OS support matrix.
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 :|
next prev parent reply other threads:[~2021-02-15 11:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 11:25 [PATCH V2 0/7] block/rbd: migrate to coroutines and add write zeroes support Peter Lieven
2021-01-26 11:25 ` [PATCH V2 1/7] block/rbd: bump librbd requirement to luminous release Peter Lieven
2021-02-15 10:11 ` Kevin Wolf
2021-02-15 10:19 ` Daniel P. Berrangé
2021-02-15 11:34 ` Peter Lieven
2021-02-15 12:17 ` Kevin Wolf
2021-02-15 10:24 ` Daniel P. Berrangé
2021-02-15 11:32 ` Peter Lieven
2021-02-15 11:41 ` Daniel P. Berrangé
2021-02-15 11:45 ` Peter Lieven
2021-02-15 11:51 ` Daniel P. Berrangé [this message]
2021-02-15 11:55 ` Peter Lieven
2021-02-15 12:02 ` Daniel P. Berrangé
2021-02-15 12:13 ` Kevin Wolf
2021-02-15 13:28 ` Peter Lieven
2021-02-22 21:48 ` Jason Dillaman
2021-01-26 11:25 ` [PATCH V2 2/7] block/rbd: store object_size in BDRVRBDState Peter Lieven
2021-01-26 11:25 ` [PATCH V2 3/7] block/rbd: update s->image_size in qemu_rbd_getlength Peter Lieven
2021-01-26 11:25 ` [PATCH V2 4/7] block/rbd: add bdrv_attach_aio_context Peter Lieven
2021-02-15 10:20 ` Kevin Wolf
2021-02-15 11:48 ` Peter Lieven
2021-01-26 11:25 ` [PATCH V2 5/7] block/rbd: migrate from aio to coroutines Peter Lieven
2021-01-26 11:25 ` [PATCH V2 6/7] block/rbd: add write zeroes support Peter Lieven
2021-01-26 11:25 ` [PATCH V2 7/7] block/rbd: drop qemu_rbd_refresh_limits Peter Lieven
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=20210215115114.GE1542881@redhat.com \
--to=berrange@redhat.com \
--cc=ct@flyingcircus.io \
--cc=dillaman@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.