From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
<linux-kernel@vger.kernel.org>, <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] xen/blback: Fit the important information of the thread in 17 characters
Date: Fri, 19 Feb 2016 16:40:04 +0100 [thread overview]
Message-ID: <56C73754.1080303@citrix.com> (raw)
In-Reply-To: <1455726686-23091-1-git-send-email-konrad.wilk@oracle.com>
El 17/2/16 a les 17:31, Konrad Rzeszutek Wilk ha escrit:
> The processes names are truncated to 17, while we had the length
> of the process as name 20 - which meant that while we filled
> it out with various details - the last 3 characters (which had
> the queue number) never surfaced to the user-space.
>
> To simplify this and be able to fit the device name, domain id,
> and the queue number we remove the 'blkback' from the name.
>
> Prior to this patch the device name is "blkback.<domid>.<name>"
> for example: blkback.8.xvda, blkback.11.hda.
>
> With the multiqueue block backend we add "-%d" for the queue.
> But sadly this is already way past the limit so it gets stripped.
>
> Possible solution had been identified by Ian:
> http://lists.xenproject.org/archives/html/xen-devel/2015-05/msg03516.html
>
> "
> If you are pressed for space then the "xvd" is probably a bit redundant
> in a string which starts blkbk.
>
> The guest may not even call the device xvdN (iirc BSD has another
> prefix) any how, so having blkback say so seems of limited use anyway.
>
> Since this seems to not include a partition number how does this work in
> the split partition scheme? (i.e. one where the guest is given xvda1 and
> xvda2 rather than xvda with a partition table)
>
> [It will be 'blkback.8.xvda1', and 'blkback.11.xvda2']
>
> Perhaps something derived from one of the schemes in
> http://xenbits.xen.org/docs/unstable/misc/vbd-interface.txt might be a
> better fit?
>
> After a bit of discussion (see
> http://lists.xenproject.org/archives/html/xen-devel/2015-12/msg01588.html)
> we settled on dropping the "blback" part.
>
> This will make it possible to have the <domid>.<name>-<queue>:
>
> [1.xvda-0]
> [1.xvda-1]
>
> And we enough space to make it go up to:
>
> [32100.xvdfg9-5]
>
> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Acked-by: Roger Pau Monné <roger.pau@citrix.com>
According to:
http://lists.xenproject.org/archives/html/xen-devel/2015-05/msg03505.html
Should this have a:
Reported-by: Jan Beulich <jbeulich@suse.com>
Thanks!
parent reply other threads:[~2016-02-19 15:40 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1455726686-23091-1-git-send-email-konrad.wilk@oracle.com>]
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=56C73754.1080303@citrix.com \
--to=roger.pau@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®