All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ilya Dryomov <ilya.dryomov@inktank.com>
To: Somnath Roy <Somnath.Roy@sandisk.com>
Cc: Chaitanya Huilgol <chaitanya.huilgol@gmail.com>,
	Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: [PATCH] ceph: rbd option listing and tcp_nodelay support
Date: Wed, 21 Jan 2015 22:46:48 +0300	[thread overview]
Message-ID: <CALFYKtAJ5RiwkEiUGD=oVFzC+Rtor9pF7R4_L9Di9Zg4THCviA@mail.gmail.com> (raw)
In-Reply-To: <755F6B91B3BE364F9BCA11EA3F9E0C6F2827C9AA@SACMBXIP02.sdcorp.global.sandisk.com>

On Wed, Jan 21, 2015 at 10:29 PM, Somnath Roy <Somnath.Roy@sandisk.com> wrote:
> Ilya,
> Regarding supported attribute list,  I think it could be a step towards better usability experience during rbd map command. Presently, if user gives wrong option or unsupported option it just errors out saying 'sysfs write failed' or so. User has no idea what went wrong.

# rbd map -o foobar test
rbd: unknown map option 'foobar'
rbd: couldn't parse map options

# rbd map -o fsid=foobar test
rbd: invalid fsid value 'foobar'
rbd: couldn't parse map options

Since about a year ago, rbd cli would try to parse supplied options.
Of course, the list of options it knows about is static, but your
attribute wouldn't solve that problem (or rather it will, but only for
simple boolean yes/no options, like crc or tcp_nodelay) because we also
try to sanity check the value, as the above fsid example shows.

> We can use this supported list from kernel module from rbd cli to show proper error message to the user.
> Another feature that we have implemented is rbd cli to consult the /etc/ceph/ceph.conf and take the rbd kernel supported options from there automatically if user has not provided any option during rbd map. User provided option during rbd map will always get priority though.

Did you mean "and take rbd kernel map options", i.e. take default
map options from ceph.conf?  I think that's a good idea.

Thanks,

                Ilya

  reply	other threads:[~2015-01-21 19:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-21 19:00 [PATCH] ceph: rbd option listing and tcp_nodelay support Chaitanya Huilgol
2015-01-21 19:18 ` Ilya Dryomov
2015-01-21 19:29   ` Somnath Roy
2015-01-21 19:46     ` Ilya Dryomov [this message]
2015-01-21 20:02       ` Somnath Roy
2015-01-22  2:33         ` Chaitanya Huilgol
2015-01-22  8:54         ` Ilya Dryomov
2015-01-22  9:54           ` Chaitanya Huilgol
2015-01-22 12:50             ` Ilya Dryomov
2015-01-22 13:33               ` Chaitanya Huilgol
2015-01-22 14:28                 ` Ilya Dryomov
2015-01-22 14:39                   ` Chaitanya Huilgol
2015-01-22 15:08                     ` Ilya Dryomov
2015-01-22 16:48                       ` Chaitanya Huilgol
2015-01-22 16:52                         ` Ilya Dryomov
2015-01-22 14:40             ` Sage Weil
2015-01-22 17:42           ` Somnath Roy
     [not found] <9E914F5BD7F48A4782456CEB550A42280A75F93C@SACMBXIP01.sdcorp.global.sandisk.com>
2015-01-21 18:32 ` Chaitanya Huilgol

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='CALFYKtAJ5RiwkEiUGD=oVFzC+Rtor9pF7R4_L9Di9Zg4THCviA@mail.gmail.com' \
    --to=ilya.dryomov@inktank.com \
    --cc=Somnath.Roy@sandisk.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=chaitanya.huilgol@gmail.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.