From: Shirley Ma <mashirle@us.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, jasowang@redhat.com
Subject: Re: [PATCH net-next]vhost: fix condition check for # of outstanding dma buffers
Date: Wed, 20 Jul 2011 08:43:09 -0700 [thread overview]
Message-ID: <1311176589.8573.33.camel@localhost.localdomain> (raw)
In-Reply-To: <20110720102831.GA5164@redhat.com>
On Wed, 2011-07-20 at 13:28 +0300, Michael S. Tsirkin wrote:
> On Tue, Jul 19, 2011 at 01:56:25PM -0700, Shirley Ma wrote:
> > On Tue, 2011-07-19 at 22:09 +0300, Michael S. Tsirkin wrote:
> > > On Tue, Jul 19, 2011 at 11:37:58AM -0700, Shirley Ma wrote:
> > > > Signed-off-by: Shirley Ma <xma@us.ibm.com>
> > > > ---
> > > >
> > > > drivers/vhost/net.c | 6 ++++--
> > > > 1 files changed, 4 insertions(+), 2 deletions(-)
> > > >
> > > > diff --git a/drivers/vhost/net.c b/drivers/vhost/net.c
> > > > index 70ac604..83cb738 100644
> > > > --- a/drivers/vhost/net.c
> > > > +++ b/drivers/vhost/net.c
> > > > @@ -189,8 +189,10 @@ static void handle_tx(struct vhost_net
> *net)
> > > > break;
> > > > }
> > > > /* If more outstanding DMAs, queue the
> work */
> > > > - if (unlikely(vq->upend_idx - vq->done_idx
> >
> > > > - VHOST_MAX_PEND)) {
> > > > + if (unlikely((vq->upend_idx - vq->done_idx
> >
> > > > + VHOST_MAX_PEND) ||
> > > > + (vq->upend_idx - vq->done_idx
> >
> > > > + VHOST_MAX_PEND -
> > > UIO_MAXIOV))) {
> > >
> > > Could you please explain why this makes sense please?
> > > VHOST_MAX_PEND is 128 UIO_MAXIOV is 1024 so
> > > the result is negative?
> >
> > I thought it is equal to:
> >
> > if (vq->upend_idx > vq->done_idx)
> > check vq->upend_idx - vq->done_idx > VHOST_MAX_PEND
> > if (vq->upend_idx < vq->done_idx)
> > check vq->upend_idx + UIO_MAXIOV - vq->done_idx >
> VHOST_MAX_PEND
> >
>
> Check it out: upend_idx == done_idx == 0 does not satisfy the
> above conditions but does trigger in your code, right?
We don't hit upend_idx == done_idx == 0. Only upend_idx == done_idx ==
UIO_MAXIOV could happen if the lower device has issue and never DMA any
packets out.
> Better keep it simple. Maybe:
>
> if (unlikely(vq->upend_idx - vq->done_idx > VHOST_MAX_PEND) ||
> (unlikely(vq->upend_idx < vq->done_idx) &&
> unlikely(vq->upend_idx + UIO_MAXIOV - vq->done_idx >
> VHOST_MAX_PEND)))
>
> ?
>
> Also, please add commit log documenting what does the patch
> fix: something like:
> 'the test for # of outstanding buffers returned
> incorrect results when due to wrap around,
> upend_idx < done_idx'?
Sure, will modify it and resubmit.
> > > I thought upend_idx - done_idx is exactly the number
> > > of buffers, so once we get too many we stop until
> > > one gets freed?
> >
> > They are index, so in vhost zerocopy callback, we can get the idx
> right
> > away.
> >
> > >
> > > > tx_poll_start(net, sock);
> > > > set_bit(SOCK_ASYNC_NOSPACE,
> > > &sock->flags);
> > > > break;
> > > >
Thanks
Shirley
next prev parent reply other threads:[~2011-07-20 15:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 18:37 [PATCH net-next]vhost: fix condition check for # of outstanding dma buffers Shirley Ma
2011-07-19 19:09 ` Michael S. Tsirkin
2011-07-19 20:56 ` Shirley Ma
2011-07-20 10:28 ` Michael S. Tsirkin
2011-07-20 15:43 ` Shirley Ma [this message]
2011-07-20 16:17 ` Michael S. Tsirkin
2011-07-20 16:49 ` Shirley Ma
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=1311176589.8573.33.camel@localhost.localdomain \
--to=mashirle@us.ibm.com \
--cc=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.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).