All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: maxime coquelin <maxime.coquelin@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] VhostUserRequest # 20
Date: Thu, 1 Jun 2017 18:20:47 +0100	[thread overview]
Message-ID: <20170601172046.GJ2845@work-vm> (raw)
In-Reply-To: <1509302139.20862844.1495638621196.JavaMail.zimbra@redhat.com>

* Marc-André Lureau (marcandre.lureau@redhat.com) wrote:
> Hi
> 
> ----- Original Message -----
> > * Marc-André Lureau (marcandre.lureau@redhat.com) wrote:
> > > HI
> > > 
> > > ----- Original Message -----
> > > > Hi,
> > > >   libvhost-user.h defines:
> > > >    VHOST_USER_INPUT_GET_CONFIG = 20,
> > > 
> > > That slipped by mistake from my vhost-user-input series WIP, please send a
> > > fix.
> > > (luckily, this is only internal header for now)
> > 
> > OK, just posted.
> > 
> > However, I just spotted, or should I say gcc just spotted another issue:
> > 
> >   CC      tests/vhost-user-bridge.o
> > /home/dgilbert/git/qemu-world3/tests/vhost-user-bridge.c:228:23: warning:
> > variables 'front' and 'iov' used in loop condition not modified in loop body
> > [-Wfor-loop-analysis]
> >     for (cur = front; front != iov; cur++) {
> >                       ^~~~~    ~~~
> > 1 warning generated.
> > 
> > 
> > static void
> > iov_restore_front(struct iovec *front, struct iovec *iov, size_t bytes)
> > {
> >     struct iovec *cur;
> > 
> >     for (cur = front; front != iov; cur++) {
> >         bytes -= cur->iov_len;
> >     }
> > 
> >     cur->iov_base -= bytes;
> >     cur->iov_len += bytes;
> > }
> > 
> > What's that actually intending to do?
> 
> It was meant to revert the effect of iov_discard_front()
> 
> The code should read:
> 
> for (cur = front; cur != iov; cur++) {
> 
> In practice, it doesn't reach the loop since the front sg buffer is big enough to discard the header..
> 
> Does that looks correct to you?

OK, so let me check if I understand;  it's supposed to be called with
'front' being the original struct iovec *, and 'bytes' being the number
of bytes you shaved off using iov_discard_front?
If so then yes I think that makes sense; a comment to explain that
would probably help.
A sanity check for bytes being >=0 after the loop might be worth it as
well.

Dave

> 
> 
> thanks
> 
> > 
> > Dave
> > 
> > > thanks
> > > 
> > > > while
> > > >   vhost-user.c defines:
> > > >    VHOST_USER_NET_SET_MTU = 20,
> > > > 
> > > > who wins?
> > > > 
> > > > Dave
> > > > --
> > > > Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
> > > > 
> > --
> > Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
> > 
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

      reply	other threads:[~2017-06-01 17:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-09 18:49 [Qemu-devel] VhostUserRequest # 20 Dr. David Alan Gilbert
2017-05-09 18:52 ` Marc-André Lureau
2017-05-10 13:32   ` Dr. David Alan Gilbert
2017-05-24 15:10     ` Marc-André Lureau
2017-06-01 17:20       ` Dr. David Alan Gilbert [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=20170601172046.GJ2845@work-vm \
    --to=dgilbert@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=qemu-devel@nongnu.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 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.