From: Vivek Goyal <vgoyal@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: virtio-fs-list <virtio-fs@redhat.com>,
jose.carlos.venegas.munoz@intel.com, qemu-devel@nongnu.org,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [PATCH] virtiofsd: Use --thread-pool-size=0 to mean no thread pool
Date: Mon, 9 Nov 2020 09:40:49 -0500 [thread overview]
Message-ID: <20201109144049.GC1479853@redhat.com> (raw)
In-Reply-To: <20201109101102.GE3024@work-vm>
On Mon, Nov 09, 2020 at 10:11:02AM +0000, Dr. David Alan Gilbert wrote:
> * Vivek Goyal (vgoyal@redhat.com) wrote:
> > Right now we create a thread pool and main thread hands over the request
> > to thread in thread pool to process. Number of threads in thread pool
> > can be managed by option --thread-pool-size.
> >
> > There is a chance that in case of some workloads, we might get better
> > performance if we don't handover the request to a different thread
> > and process in the context of thread receiving the request.
> >
> > To implement that, redefine the meaning of --thread-pool-size=0 to
> > mean that don't use a thread pool. Instead process the request in
> > the context of thread receiving request from the queue.
> >
> > I can't think how --thread-pool-size=0 is useful and hence using
> > that. If it is already useful somehow, I could look at defining
> > a new option say "--no-thread-pool".
> >
> > I think this patch will be used more as a debug help to do comparison
> > when it is more effecient to do not hand over the requests to a
> > thread pool.
> >
> > Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
>
> I think this is OK, but you need to fix the style to match qemu rather
> than kernel style.
> (See qemu's scripts/checpatch.pl)
Sure. I just posted V2 of the patch and took care of all the issues
reported by qemu's scripts/checkpatch.pl.
Vivek
prev parent reply other threads:[~2020-11-09 14:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 19:44 [PATCH] virtiofsd: Use --thread-pool-size=0 to mean no thread pool Vivek Goyal
2020-11-05 19:52 ` [Virtio-fs] " Vivek Goyal
2020-11-06 20:33 ` Venegas Munoz, Jose Carlos
2020-11-06 22:35 ` Vivek Goyal
2020-11-09 10:02 ` Dr. David Alan Gilbert
2020-11-09 14:39 ` Vivek Goyal
2020-11-12 9:06 ` Miklos Szeredi
2020-11-12 9:57 ` Miklos Szeredi
2020-11-18 20:19 ` Vivek Goyal
2020-11-12 11:00 ` Christian Schoenebeck
2020-11-12 13:01 ` Miklos Szeredi
2020-11-17 16:00 ` Venegas Munoz, Jose Carlos
2020-11-17 16:39 ` Christian Schoenebeck
2020-11-17 18:55 ` Vivek Goyal
2020-11-23 15:06 ` Venegas Munoz, Jose Carlos
2020-11-17 22:24 ` Vivek Goyal
2020-11-23 15:07 ` Venegas Munoz, Jose Carlos
2020-11-18 19:51 ` Vivek Goyal
2020-11-23 9:46 ` Miklos Szeredi
2020-11-09 10:11 ` Dr. David Alan Gilbert
2020-11-09 14:40 ` Vivek Goyal [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=20201109144049.GC1479853@redhat.com \
--to=vgoyal@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jose.carlos.venegas.munoz@intel.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=virtio-fs@redhat.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).