From: asmadeus@codewreck.org
To: ron minnich <rminnich@gmail.com>
Cc: evanhensbergen@icloud.com, Eric Van Hensbergen <ericvh@gmail.com>,
Christian Schoenebeck <linux_oss@crudebyte.com>,
v9fs-developer@lists.sourceforge.net,
Latchesar Ionkov <lucho@ionkov.net>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/6] Adjust maximum MSIZE to account for p9 header
Date: Mon, 19 Dec 2022 04:46:43 +0900 [thread overview]
Message-ID: <Y59uIwoECw0yHhf1@codewreck.org> (raw)
In-Reply-To: <CAP6exY+BF+1fjjUKX20vvbTZXiZ2gxUN3zc8+ZaHTY-aX6fRFQ@mail.gmail.com>
ron minnich wrote on Sun, Dec 18, 2022 at 08:50:18AM -0800:
> it's fine. tbh, I doubt the fact that you were fetching 31 vs 32 pages
> mattered as much as the fact that you weren't fetching *4k at a time* :-)
Yes, I think we can just blanket this as +4k and it wouldn't change
much; I've been using 1MB+4k for rdma in previous tests...
We still aren't doing things 4k at a time with this though, I'd suggest
rounding down the rsize > msize check in p9_client_read_once():
if (!rsize || rsize > clnt->msize - P9_IOHDRSZ)
rsize = clnt->msize - P9_IOHDRSZ;
to something that's better aligned; for some reason I thought we had
that already. . . but thinking again the sizes are probably driven by
the cache and will be 4k multiples already?
> > -#define DEFAULT_MSIZE (128 * 1024)
> > +/* DEFAULT MSIZE = 32 pages worth of payload + P9_HDRSZ +
> > + * room for write (16 extra) or read (11 extra) operands.
> > + */
> > +
> > +#define DEFAULT_MSIZE ((128 * 1024) + P9_HDRSZ + 16)
There's P9_IOHDRSZ for that ;)
But I guess with the comment it doesn't matter much either way.
--
Dominique
next prev parent reply other threads:[~2022-12-18 19:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-17 18:52 [PATCH] Improve 9p performance for read operations Eric Van Hensbergen
2022-12-17 18:52 ` [PATCH 1/6] Adjust maximum MSIZE to account for p9 header Eric Van Hensbergen
2022-12-18 14:49 ` Christian Schoenebeck
[not found] ` <CAFkjPTmoQvzaSsSOAgM9_0+knudWsdi8=TnMOTXZj05hT6tneQ@mail.gmail.com>
[not found] ` <51FD8D16-4070-4DCF-AEB5-11640A82762E@icloud.com>
[not found] ` <CAP6exY+BF+1fjjUKX20vvbTZXiZ2gxUN3zc8+ZaHTY-aX6fRFQ@mail.gmail.com>
2022-12-18 19:46 ` asmadeus [this message]
2022-12-18 19:52 ` evanhensbergen
2022-12-17 18:52 ` [PATCH 2/6] Don't assume UID 0 attach Eric Van Hensbergen
2022-12-18 0:07 ` asmadeus
2022-12-18 1:05 ` evanhensbergen
[not found] ` <864E1007-CBCF-40C7-B438-A76C3065AFC9@icloud.com>
2022-12-18 19:49 ` [V9fs-developer] " asmadeus
2022-12-18 19:59 ` evanhensbergen
2022-12-17 18:52 ` [PATCH 3/6] Expand setup of writeback cache to all levels Eric Van Hensbergen
2022-12-17 18:52 ` [PATCH 4/6] Consolidate file operations and add readahead and writeback Eric Van Hensbergen
2022-12-17 20:49 ` kernel test robot
2022-12-17 21:50 ` kernel test robot
2022-12-17 18:52 ` [PATCH 5/6] Remove unnecessary superblock flags Eric Van Hensbergen
2022-12-17 18:52 ` [PATCH 6/6] allow disable of xattr support on mount Eric Van Hensbergen
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=Y59uIwoECw0yHhf1@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=ericvh@gmail.com \
--cc=evanhensbergen@icloud.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=rminnich@gmail.com \
--cc=v9fs-developer@lists.sourceforge.net \
/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 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.