Linux virtualization list
 help / color / mirror / Atom feed
From: Aaron Paterson <apaterson@pm.me>
To: Miklos Szeredi <miklos@szeredi.hu>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Vivek Goyal <vgoyal@redhat.com>,
	German Maglione <gmaglione@redhat.com>,
	Shuah Khan <shuah@kernel.org>
Cc: "Eugenio Pérez" <eperezma@redhat.com>,
	fuse-devel@lists.linux.dev, linux-fsdevel@vger.kernel.org,
	linux-kselftest@vger.kernel.org, virtualization@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] fuse: report a request refused for a live nodeid
Date: Fri, 28 Aug 2026 02:02:48 +0000	[thread overview]
Message-ID: <20260828020241.92045-1-apaterson@pm.me> (raw)
In-Reply-To: <cover.1787873791.git.apaterson@pm.me>

The measurements in the cover letter were taken on 6.18.5. I have now run
the same comparison on current mainline, so the numbers sit on the tree
the series is posted against: v7.2-15794-g1b78070aaef6, inside the 7.3
merge window.

Both kernels come from the mainline git tree directly rather than from
applying the patches at build time. The unpatched arm is that commit as
it stands; the patched arm is the same commit with these five applied.
So the only difference between the two kernels is the series as posted.

  arm  fs/fuse  virtio_fs  opens    refused
   A   stock    stock      315076   22646 (7.2%)
   D   patched  patched    407169   0

Every refusal on arm A is the contradiction the probe exists to report:
open answered ENOENT while stat on the same path a moment later still
described the file. On arm D there are none.

The refusal rate is lower here than the 14.0% the cover letter reports
for 6.18.5. It is a race, so the rate moves with load and with how fast
the guest gets through its loop, and the arms above were taken while the
host was busy building the other kernel. What does not move is which
side of zero each arm lands on.

The probe is the one described in the cover letter: one process replaces
a file by rename while another opens the same name as fast as it can.
The server is Apple's Virtualization virtio-fs, which releases an inode
as soon as a rename displaces the name it was looked up by, and is what
makes the refusal observable at all.


      parent reply	other threads:[~2026-08-28  2:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27 23:37 [PATCH 0/5] fuse: report a request refused for a live nodeid as stale Aaron Paterson
2026-08-27 23:37 ` [PATCH 1/5] selftests/fuse: ignore the built acl cache test Aaron Paterson
2026-08-27 23:37 ` [PATCH 2/5] selftests/fuse: name the libfuse3 flags for the library Aaron Paterson
2026-08-27 23:37 ` [PATCH 3/5] fuse: report a request refused for a live nodeid as stale Aaron Paterson
2026-08-27 23:38 ` [PATCH 4/5] selftests/fuse: cover a request refused for a live nodeid Aaron Paterson
2026-08-27 23:38 ` [PATCH 5/5] virtiofs: report a request refused for a live nodeid as stale Aaron Paterson
2026-08-28  2:02 ` Aaron Paterson [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=20260828020241.92045-1-apaterson@pm.me \
    --to=apaterson@pm.me \
    --cc=eperezma@redhat.com \
    --cc=fuse-devel@lists.linux.dev \
    --cc=gmaglione@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=shuah@kernel.org \
    --cc=stefanha@redhat.com \
    --cc=vgoyal@redhat.com \
    --cc=virtualization@lists.linux.dev \
    /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