All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Florensa <fflorensa@online.net>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: kwolf@redhat.com, mreitz@redhat.com, dillaman@redhat.com,
	qemu-devel@nongnu.org, armbru@redhat.com
Subject: Re: [PATCH] block/rbd: Add support for ceph namespaces
Date: Fri, 20 Dec 2019 15:11:43 +0100	[thread overview]
Message-ID: <20191220141125.wxlm4eizbwie6522@flash.localdomain> (raw)
In-Reply-To: <20191219145125.iwhxhzmt5mow5pea@steredhat>

[-- Attachment #1: Type: text/plain, Size: 979 bytes --]

Hello Stefano and Jason,

First of all thanks for the quick reply,
Response inline belowe
> Hi Florian,
> 
> I think we need to add (Since: 5.0).

Are you implying by that (Since: 5.0) that we need to specify its
availability target is qemu 5.0 ?
I guess that maybe a version check would be better ? Like try to do
namespaces stuff only if we have a recent enough librbd in the system ?
Using something like :

int rbd_major;

rbd_version(&rbd_major, NULL, NULL);
/*
 * Target only nautilus+ librbd for namespace support
*/
if (rbd_major >= 14) // tar
 <process namespace>

> 
> The patch LGTM, but I'd like to use 'namespace' instead of cryptic
> 'nspace'. (as BlockdevOptionsNVMe did)
> What do you think?
> 
Yes no worries, I can rename it to 'rbd_namespace' to avoid any possible
confusion, is this Ok for you ?
> 
> With those fixed:
> 
> Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
> 
> Thanks,
> Stefano

Regards,
Florian

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-12-20 14:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-19 13:34 [PATCH] block/rbd: Add support for ceph namespaces Florian Florensa
2019-12-19 14:15 ` Jason Dillaman
2019-12-19 14:51 ` Stefano Garzarella
2019-12-20 14:11   ` Florian Florensa [this message]
2019-12-20 14:56     ` Jason Dillaman
2019-12-20 15:09       ` Stefano Garzarella
2019-12-20 17:17       ` Florian Florensa
2019-12-20 21:05         ` Eric Blake
2019-12-20 21:02 ` Eric Blake

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=20191220141125.wxlm4eizbwie6522@flash.localdomain \
    --to=fflorensa@online.net \
    --cc=armbru@redhat.com \
    --cc=dillaman@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sgarzare@redhat.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 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.