linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: axboe@kernel.dk, kvm@vger.kernel.org, linux-scsi@vger.kernel.org,
	asamymuthupa@micron.com, linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	James.Bottomley@HansenPartnership.com,
	Ren Mingxin <renmx@cn.fujitsu.com>,
	tj@kernel.org
Subject: Re: [PATCH] virtio_blk: Add help function to format mass of disks
Date: Tue, 10 Apr 2012 16:34:06 +0300	[thread overview]
Message-ID: <20120410133406.GA18899@redhat.com> (raw)
In-Reply-To: <4F84329A.60703@redhat.com>

On Tue, Apr 10, 2012 at 04:16:10PM +0300, Avi Kivity wrote:
> On 04/10/2012 10:28 AM, Ren Mingxin wrote:
> > The current virtio block's naming algorithm just supports 18278
> > (26^3 + 26^2 + 26) disks. If there are mass of virtio blocks,
> > there will be disks with the same name.
> >
> > Based on commit 3e1a7ff8a0a7b948f2684930166954f9e8e776fe, I add
> > function "virtblk_name_format()" for virtio block to support mass
> > of disks naming.
> >
> > Signed-off-by: Ren Mingxin <renmx@cn.fujitsu.com>
> > ---
> >  drivers/block/virtio_blk.c |   38 ++++++++++++++++++++++++++------------
> >  1 files changed, 26 insertions(+), 12 deletions(-)
> >
> > diff --git a/drivers/block/virtio_blk.c b/drivers/block/virtio_blk.c
> > index c4a60ba..86516c8 100644
> > --- a/drivers/block/virtio_blk.c
> > +++ b/drivers/block/virtio_blk.c
> > @@ -374,6 +374,31 @@ static int init_vq(struct virtio_blk *vblk)
> >  	return err;
> >  }
> >  
> > +static int virtblk_name_format(char *prefix, int index, char *buf, int buflen)
> > +{
> > +	const int base = 'z' - 'a' + 1;
> > +	char *begin = buf + strlen(prefix);
> > +	char *begin = buf + strlen(prefix);
> 
> Duplicate line.
> 
> > +	char *end = buf + buflen;
> > +	char *p;
> > +	int unit;
> > +
> > +	p = end - 1;
> > +	*p = '\0';
> > +	unit = base;
> 
> Why not use 'base' below?  neither unit nor base change.

Yes it's a bit strange, it was the same in Tejun's patch.
Tejun, any idea?

> > +	do {
> > +		if (p == begin)
> > +			return -EINVAL;
> > +		*--p = 'a' + (index % unit);
> > +		index = (index / unit) - 1;
> > +	} while (index >= 0);
> > +
> > +	memmove(begin, p, end - p);
> > +	memcpy(buf, prefix, strlen(prefix));
> > +
> > +	return 0;
> > +}
> > +
> >
> 
> -- 
> error compiling committee.c: too many arguments to function

  reply	other threads:[~2012-04-10 13:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-10  7:28 [PATCH] virtio_blk: Add help function to format mass of disks Ren Mingxin
2012-04-10 13:08 ` Asias He
2012-04-10 13:16 ` Avi Kivity
2012-04-10 13:34   ` Michael S. Tsirkin [this message]
2012-04-10 15:49     ` Tejun Heo
2012-04-10 15:53       ` Michael S. Tsirkin
2012-04-11  1:21         ` Asias He
2012-04-11  1:31           ` Ren Mingxin
2012-04-11  1:28   ` Ren Mingxin
2012-04-11  8:43 ` Michael S. Tsirkin

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=20120410133406.GA18899@redhat.com \
    --to=mst@redhat.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=asamymuthupa@micron.com \
    --cc=avi@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=renmx@cn.fujitsu.com \
    --cc=tj@kernel.org \
    --cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).