From: Dominique Martinet <asmadeus@codewreck.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christian Schoenebeck <linux_oss@crudebyte.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
v9fs-developer@lists.sourceforge.net
Subject: [GIT PULL] 9p fixes for 6.1
Date: Mon, 10 Oct 2022 14:23:05 +0900 [thread overview]
Message-ID: <Y0OsOYmG+PU2CgcH@codewreck.org> (raw)
The following changes since commit b90cb1053190353cc30f0fef0ef1f378ccc063c5:
Linux 6.0-rc3 (2022-08-28 15:05:29 -0700)
are available in the Git repository at:
https://github.com/martinetd/linux tags/9p-for-6.1
for you to fetch changes up to a8e633c604476e24d26a636582c0f5bdb421e70d:
net/9p: clarify trans_fd parse_opt failure handling (2022-10-07 21:23:09 +0900)
----------------------------------------------------------------
9p-for-6.1: smaller buffers for small messages and fixes
The highlight of this PR is Christian's patch to allocate smaller buffers
for most metadata requests: 9p with a big msize would try to allocate large
buffers when just 4 or 8k would be more than enough; this brings in nice
performance improvements.
There's also a few fixes for problems reported by syzkaller (thanks to
Schspa Shi, Tetsuo Handa for tests and feedback/patches) as well as some
minor cleanup
----------------------------------------------------------------
Christian Schoenebeck (5):
net/9p: split message size argument into 't_size' and 'r_size' pair
9p: add P9_ERRMAX for 9p2000 and 9p2000.u
net/9p: add p9_msg_buf_size()
net/9p: add 'pooled_rbuffers' flag to struct p9_trans_module
net/9p: allocate appropriate reduced message buffers
Dominique Martinet (2):
9p: trans_fd/p9_conn_cancel: drop client lock earlier
net/9p: use a dedicated spinlock for trans_fd
Li Zhong (1):
net/9p: clarify trans_fd parse_opt failure handling
Tetsuo Handa (1):
9p/trans_fd: always use O_NONBLOCK read/write
Xiu Jianfeng (1):
net/9p: add __init/__exit annotations to module init/exit funcs
include/net/9p/9p.h | 3 +++
include/net/9p/transport.h | 5 ++++
net/9p/client.c | 48 +++++++++++++++++++++++++++++++--------
net/9p/protocol.c | 167 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
net/9p/protocol.h | 2 ++
net/9p/trans_fd.c | 50 ++++++++++++++++++++++++++--------------
net/9p/trans_rdma.c | 1 +
net/9p/trans_virtio.c | 1 +
net/9p/trans_xen.c | 5 ++--
9 files changed, 254 insertions(+), 28 deletions(-)
--
Dominique
next reply other threads:[~2022-10-10 5:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 5:23 Dominique Martinet [this message]
2022-10-11 3:43 ` [GIT PULL] 9p fixes for 6.1 pr-tracker-bot
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=Y0OsOYmG+PU2CgcH@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=torvalds@linux-foundation.org \
--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 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).