All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wang Sheng-Hui <shhuiw@gmail.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: wanlong.gao@gmail.com, rusty@rustcorp.com.au,
	virtualization@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] virtio: fix size computation according to the definition of struct vring_used in vring_size
Date: Sun, 28 Aug 2011 20:48:36 +0800	[thread overview]
Message-ID: <4E5A3924.4050006@gmail.com> (raw)
In-Reply-To: <20110828113132.GB4875@redhat.com>

On 2011年08月28日 19:31, Michael S. Tsirkin wrote:
> On Sat, Aug 27, 2011 at 05:52:02PM +0800, Wang Sheng-Hui wrote:
>> On 2011年08月27日 17:34, Wang Sheng-Hui wrote:
>>> On 2011年08月27日 10:49, Wanlong Gao wrote:
>>>> On Sat, 2011-08-27 at 09:07 +0800, Wang Sheng-Hui wrote:
>>>>> The patch is against 3.1-rc3.
>>>>>
>>>>> struct vring_used has two __u16 fields plus array of struct vring_used_elem.
>>>>> Current vring_size counts the __u16 fields to 3. Fix it to 2 in the patch.
>>>>>
>>>>> Signed-off-by: Wang Sheng-Hui <shhuiw@gmail.com>
>>>>> ---
>>>>>  include/linux/virtio_ring.h |    2 +-
>>>>>  1 files changed, 1 insertions(+), 1 deletions(-)
>>>>>
>>>>> diff --git a/include/linux/virtio_ring.h b/include/linux/virtio_ring.h
>>>>> index 4a32cb6..fcda152 100644
>>>>> --- a/include/linux/virtio_ring.h
>>>>> +++ b/include/linux/virtio_ring.h
>>>>> @@ -143,7 +143,7 @@ static inline unsigned vring_size(unsigned int num, unsigned long align)
>>>>>  {
>>>>>  	return ((sizeof(struct vring_desc) * num + sizeof(__u16) * (2 + num)
>>>>>  		 + align - 1) & ~(align - 1))
>>>>> -		+ sizeof(__u16) * 3 + sizeof(struct vring_used_elem) * num;
>>>>> +		+ sizeof(__u16) * 2 + sizeof(struct vring_used_elem) * num;
>>>>>  }
>>>>>  
>>>>>  /* The following is used with USED_EVENT_IDX and AVAIL_EVENT_IDX */
>>>>
>>>> Hi:
>>>> I'm not deep into it, but I think you can see this:
>>>> http://marc.info/?l=git-commits-head&m=130687915816130&w=2
>>>>
>>>> Thanks
>>>> -Wanlong Gao
>>>>
>>>
>>> Thanks.
>>>
>>> I checked the comments, and think we should patch vring_init
>>> and vring_size according to the layout description in the comments.
>>> Right?
>>
>> New patch generated. Please check it. Thanks,
> 
> 
>> [PATCH] virtio: modify vring_init and vring_size to take account of the layout containing *_event_idx
>>
>> The patch is against 3.1-rc3.
>>
>> Based on the layout description in the comments, take account of
>> the *_event_idx in functions vring_init and vring_size.
>>
>> Signed-off-by: Wang Sheng-Hui <shhuiw@gmail.com>
> 
> Is this a bugfix or just a cleanup?
> Alignment makes us get the same values with and without, right?

It's just a cleanup.
For normal case, the value 16 is too small compared with
the alignment, I think.

> 
>> ---
>>  include/linux/virtio_ring.h |    6 +++---
>>  1 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/include/linux/virtio_ring.h b/include/linux/virtio_ring.h
>> index 4a32cb6..300af76 100644
>> --- a/include/linux/virtio_ring.h
>> +++ b/include/linux/virtio_ring.h
>> @@ -135,13 +135,13 @@ static inline void vring_init(struct vring *vr, unsigned int num, void *p,
>>  	vr->num = num;
>>  	vr->desc = p;
>>  	vr->avail = p + num*sizeof(struct vring_desc);
>> -	vr->used = (void *)(((unsigned long)&vr->avail->ring[num] + align-1)
>> -			    & ~(align - 1));
>> +	vr->used = (void *)(((unsigned long)&vr->avail->ring[num] + 16
>> +		+ align-1) & ~(align - 1));
>>  }
>>  
>>  static inline unsigned vring_size(unsigned int num, unsigned long align)
>>  {
>> -	return ((sizeof(struct vring_desc) * num + sizeof(__u16) * (2 + num)
>> +	return ((sizeof(struct vring_desc) * num + sizeof(__u16) * (3 + num)
>>  		 + align - 1) & ~(align - 1))
>>  		+ sizeof(__u16) * 3 + sizeof(struct vring_used_elem) * num;
>>  }
>> -- 
>> 1.7.1
>>


  parent reply	other threads:[~2011-08-28 12:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-27  1:07 [PATCH] virtio: fix size computation according to the definition of struct vring_used in vring_size Wang Sheng-Hui
2011-08-27  2:49 ` Wanlong Gao
2011-08-27  9:34   ` Wang Sheng-Hui
2011-08-27  9:34   ` Wang Sheng-Hui
2011-08-27  9:52     ` Wang Sheng-Hui
2011-08-28 11:31       ` Michael S. Tsirkin
2011-08-28 11:31       ` Michael S. Tsirkin
2011-08-28 12:48         ` Wang Sheng-Hui
2011-08-28 12:48         ` Wang Sheng-Hui [this message]
2011-08-29  2:53       ` Rusty Russell
2011-08-29  2:53       ` Rusty Russell
2011-08-29  6:51         ` Wang Sheng-Hui
2011-08-29  6:51         ` Wang Sheng-Hui
2011-08-29  7:55         ` Wang Sheng-Hui
2011-08-30  0:12           ` Rusty Russell
2011-08-30  0:12           ` Rusty Russell
2011-08-29  7:55         ` Wang Sheng-Hui
2011-08-27  9:52     ` Wang Sheng-Hui
2011-08-27  2:49 ` Wanlong Gao
  -- strict thread matches above, loose matches on Subject: below --
2011-08-27  1:07 Wang Sheng-Hui

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=4E5A3924.4050006@gmail.com \
    --to=shhuiw@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=rusty@rustcorp.com.au \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=wanlong.gao@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.