DPDK patches and discussions
 help / color / mirror / Atom feed
From: HePeng <xnhp0320@icloud.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: Ilya Maximets <i.maximets@samsung.com>,
	dev@dpdk.org, Tiwei Bie <tiwei.bie@intel.com>,
	Zhihong Wang <zhihong.wang@intel.com>
Subject: Re: [dpdk-dev] Missing an increment on vq->log_cache_nb_elem ?
Date: Fri, 15 Jun 2018 21:28:13 +0800	[thread overview]
Message-ID: <7B89973D-4D0D-4BF8-B369-D76F9216E7F6@icloud.com> (raw)
In-Reply-To: <c7396a8d-28b8-d8bf-bd63-d3286a7927b3@redhat.com>

Hi, Maxime,

  My name is Peng He. 

  Thanks. 

> 在 2018年6月15日,下午9:24,Maxime Coquelin <maxime.coquelin@redhat.com> 写道:
> 
> Hi,
> 
> On 06/15/2018 02:32 PM, Ilya Maximets wrote:
>>> Hi,
>>> 
>>> 
>>> In the latest dpdk master branch, in the function *vhost_log_cache_page*:
>>> 
>>> 
>>> static __rte_always_inline void
>>> vhost_log_cache_page(struct virtio_net *dev, struct vhost_virtqueue *vq,
>>> 			uint64_t page)
>>> {
>>> 	uint32_t bit_nr = page % (sizeof(unsigned long) << 3);
>>> 	uint32_t offset = page / (sizeof(unsigned long) << 3);
>>> 	int i;
>>> 
>>> 	for (i = 0; i < vq->log_cache_nb_elem; i++) {
>>> 		struct log_cache_entry *elem = vq->log_cache + i;
>>> 
>>> 		if (elem->offset == offset) {
>>> 			elem->val |= (1UL << bit_nr);
>>> 			return;
>>> 		}
>>> 	}
>>> 
>>> 	if (unlikely(i >= VHOST_LOG_CACHE_NR)) {
>>> 		/*
>>> 		 * No more room for a new log cache entry,
>>> 		 * so write the dirty log map directly.
>>> 		 */
>>> 		rte_smp_wmb();
>>> 		vhost_log_page((uint8_t *)(uintptr_t)dev->log_base, page);
>>> 
>>> 		return;
>>> 	}
>>> 
>>> 	vq->log_cache[i].offset = offset;
>>> 	vq->log_cache[i].val = (1UL << bit_nr);
>>> }
>>> 
>>> Did it just miss an increment on vq->log_cache_nb_elem ?
>> Hi. Thanks for pointing that.
>> I looked through the code and I see no updates of 'vq->log_cache_nb_elem'.
>> Looks like it always equal to initial zero value.
>> Maxime, I'm afraid that this means that currently pages logging is not
>> performed at all. Could you please check?
>> Best regards, Ilya Maximets.
> 
> Thanks Ilya for the heads-up and HePeng for reporting the issue.
> It is broken indeed... We didn't noticed corruption when running
> our non-reg tests, I guess they have to be improved.
> 
> I will post a patch shortly to fix this.
> 
> HePeng, how does your name spells in the form "$firstname $lastname"?
> I would need this info to credit you for reporting the issue.
> 
> Regards,
> Maxime

      reply	other threads:[~2018-06-15 13:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-14 12:44 HePeng
     [not found] ` <CGME20180615123208eucas1p1e5d258f95e9621a31c2fcfbf1f494476@eucas1p1.samsung.com>
2018-06-15 12:32   ` Ilya Maximets
2018-06-15 13:24     ` Maxime Coquelin
2018-06-15 13:28       ` HePeng [this message]

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=7B89973D-4D0D-4BF8-B369-D76F9216E7F6@icloud.com \
    --to=xnhp0320@icloud.com \
    --cc=dev@dpdk.org \
    --cc=i.maximets@samsung.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=tiwei.bie@intel.com \
    --cc=zhihong.wang@intel.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 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).