From: David Howells <dhowells@redhat.com>
To: Rohith Surabattula <rohiths.msft@gmail.com>,
Steve French <smfrench@gmail.com>
Cc: dhowells@redhat.com, Shyam Prasad N <nspmangalore@gmail.com>,
ronnie sahlberg <ronniesahlberg@gmail.com>,
Paulo Alcantara <pc@cjr.nz>,
jlayton@kernel.org, linux-cifs@vger.kernel.org
Subject: Re: cifs conversion to netfslib
Date: Fri, 18 Mar 2022 00:21:28 +0000 [thread overview]
Message-ID: <230153.1647562888@warthog.procyon.org.uk> (raw)
In-Reply-To: <4085703.1647475640@warthog.procyon.org.uk>
Hi Rohith, Steve,
I've updated my cifs-experimental branch. What I have there seems to work
much the same as without the patches.
I've managed to run some xfstests on it. I note that various xfstests fail,
even without my patches, and some of them seem quite slow, again even without
my patches.
Note that I'm comparing the speed to afs which does a lot of directory
management locally compared to other network filesystems, so I might be
comparing apples and oranges. For example, I can run generic/013 on afs in
4-7s, whereas it's 3m-7m on cifs. However, since /013 does a bunch of
directory ops, afs probably has an advantage by caching the entire dir
contents locally, thereby satisfying lookup and readdir from local cache and
using a bulk status fetch to stat files from a dir in batches of 50 or so.
This is probably worth further investigation at some point.
David
next prev parent reply other threads:[~2022-03-18 0:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 8:19 cifs conversion to netfslib David Howells
2022-03-11 8:25 ` David Howells
2022-03-15 3:50 ` Rohith Surabattula
2022-03-15 9:54 ` Rohith Surabattula
2022-03-17 0:07 ` David Howells
2022-03-17 16:16 ` David Howells
2022-03-18 0:21 ` David Howells [this message]
2022-03-18 2:52 ` Steve French
2022-03-21 10:19 ` Rohith Surabattula
2022-03-21 17:18 ` David Howells
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=230153.1647562888@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=jlayton@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=nspmangalore@gmail.com \
--cc=pc@cjr.nz \
--cc=rohiths.msft@gmail.com \
--cc=ronniesahlberg@gmail.com \
--cc=smfrench@gmail.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