virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	virtualization@lists.linux-foundation.org
Subject: Re: virtq questions
Date: Wed, 2 Oct 2019 09:27:34 -0400	[thread overview]
Message-ID: <20191002132734.GA6972@redhat.com> (raw)
In-Reply-To: <CAJfpegsGNoT4NUai-=HHkqOrmjgMb=4TDk79EgxDBCd8fxCGZA@mail.gmail.com>

On Wed, Oct 02, 2019 at 09:40:11AM +0200, Miklos Szeredi wrote:
> Looking at the ugly retry logic in virtiofs and have some questions.

Hi Miklos,

What are you thinking w.r.t cleanup of retry logic. As of now we put
requests in a list and retry later with the help of a worker.

Other option will probably be block the submitter if queue is full. Make
it sleep, wake up after a while and retry submission.

> First one is, where do these features come from:
> 
> VIRTIO_F_RING_PACKED
> VIRTIO_RING_F_INDIRECT_DESC

Looks like these feature bits are supposed to be advertised by the device
if device supports these capabilities.

I see in qemu code that bunch of drivers are advertisig this capability.
(virtio_scsi, virtio_blk etc).

> 
> I see that in virtiofs "packed" is off and "indirect" is on.  Is this
> guaranteed?

I can't find specifying any feature bits in vhost-user-fs.c. So we
probably are getting a default value.

Thanks
Vivek

       reply	other threads:[~2019-10-02 13:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJfpegsGNoT4NUai-=HHkqOrmjgMb=4TDk79EgxDBCd8fxCGZA@mail.gmail.com>
2019-10-02 13:27 ` Vivek Goyal [this message]
     [not found]   ` <CAJfpegvJGTFiJh5MFRNQF8dQQo7KS5f0Ei7vEYOBTw4RzVtA2w@mail.gmail.com>
2019-10-03 19:45     ` virtq questions Vivek Goyal
2019-10-02 14:52 ` Dr. David Alan Gilbert

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=20191002132734.GA6972@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=miklos@szeredi.hu \
    --cc=stefanha@redhat.com \
    --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).