All of
 help / color / mirror / Atom feed
From: Dominique Martinet <>
To: David Howells <>
Cc: Eric Van Hensbergen <>,
	Latchesar Ionkov <>,,,
Subject: Re: [PATCH] 9p: Convert to cut-down fscache I/O API rewrite
Date: Wed, 3 Feb 2021 07:36:44 +0900	[thread overview]
Message-ID: <20210202223644.GA27614@tyr> (raw)
In-Reply-To: <>

Hi David,

David Howells wrote on Tue, Feb 02, 2021 at 11:04:23AM +0000:
> Here's a draft of a patch to convert 9P to use the cut-down part of the
> fscache I/O API rewrite (I've removed all the cookie and object state machine
> changes for now).  It compiles, but I've no way to test it.  This is built on
> top of my fscache-netfs-lib branch:

Thanks for going the extra mile with all this, it's appreciated!

> I'm hoping to ask Linus to pull the netfs lib, afs and ceph changes in the
> next merge window.
> Would you be able to give it a whirl?

I'm afraid I won't have much time to give for the next merge window (in
roughly 2-4 weeks iiuc)
I can probably find some time to run very basic tests from my usual
setup but testing actual fscache capabilities will take more time and
I'm quite short right now -- I honestly have no idea if anyone uses
fscache or if it's even working right now so I'd rather take a moment to
test it properly before/after, and it's time I don't have right now.

OTOH I'd support getting the netfs lib in as planned this merge window,
and I'll definitely take the time to test this patch into my tree before
the next one in ~3months.
I think the whole point of the rework you've done is we can do things
more smoothly and there is no reason to rush it anymore, having the new
lib get tested through afs/ceph in the real world can only be reassuring
for other filesystems.


      reply	other threads:[~2021-02-02 22:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-02 11:04 [PATCH] 9p: Convert to cut-down fscache I/O API rewrite David Howells
2021-02-02 22:36 ` Dominique Martinet [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210202223644.GA27614@tyr \ \ \ \ \ \ \ \

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.