From: Greg Kurz <groug@kaod.org>
To: <qemu-devel@nongnu.org>
Cc: Christian Schoenebeck <qemu_oss@crudebyte.com>
Subject: Re: [PATCH 0/3] 9pfs: Improve unreclaim logic
Date: Thu, 21 Jan 2021 18:05:16 +0100 [thread overview]
Message-ID: <20210121180516.038884c1@bahia.lan> (raw)
In-Reply-To: <20210118142300.801516-1-groug@kaod.org>
On Mon, 18 Jan 2021 15:22:57 +0100
Greg Kurz <groug@kaod.org> wrote:
> clone of "master"
>
Drat... this text seems to have leaked from stgit and replaced
the one I had written in git publish:
---
We currently restart the unreclaim loop all over when we detect
that the current iteration yielded execution. This is because
a new fid might have been added to the head of the list.
This is sub-optimal : add new fids to the end of the list instead
to avoid that.
---
I'll have to sort this out...
> Greg Kurz (3):
> 9pfs: Convert V9fsFidState::clunked to bool
> 9pfs: Convert V9fsFidState::fid_list to QSIMPLEQ
> 9pfs: Improve unreclaim loop
>
> hw/9pfs/9p.c | 83 +++++++++++++++++++++++++++++-----------------------
> hw/9pfs/9p.h | 6 ++--
> 2 files changed, 50 insertions(+), 39 deletions(-)
>
I've applied patches 1 and 2 to:
https://gitlab.com/gkurz/qemu/-/tree/9p-next
prev parent reply other threads:[~2021-01-21 17:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 14:22 [PATCH 0/3] 9pfs: Improve unreclaim logic Greg Kurz
2021-01-18 14:22 ` [PATCH 1/3] 9pfs: Convert V9fsFidState::clunked to bool Greg Kurz
2021-01-18 14:42 ` Christian Schoenebeck
2021-01-18 14:22 ` [PATCH 2/3] 9pfs: Convert V9fsFidState::fid_list to QSIMPLEQ Greg Kurz
2021-01-19 13:31 ` Christian Schoenebeck
2021-01-19 14:34 ` Greg Kurz
2021-01-19 15:28 ` Christian Schoenebeck
2021-01-19 17:23 ` Greg Kurz
2021-01-18 14:23 ` [PATCH 3/3] 9pfs: Improve unreclaim loop Greg Kurz
2021-01-21 12:50 ` Christian Schoenebeck
2021-01-21 16:34 ` Greg Kurz
2021-01-21 17:02 ` Christian Schoenebeck
2021-01-21 17:05 ` Greg Kurz [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=20210121180516.038884c1@bahia.lan \
--to=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu_oss@crudebyte.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).