diff options
| author | Rick Macklem <rmacklem@FreeBSD.org> | 2026-09-01 13:53:34 +0000 |
|---|---|---|
| committer | Rick Macklem <rmacklem@FreeBSD.org> | 2026-09-01 14:05:20 +0000 |
| commit | f41d83578e8eb1efced76704f00bcf6b201c3821 (patch) | |
| tree | aee1b4615652484dce024f5a58af494022cc684f /sample/https-client.c | |
| parent | b3734c1386dd2b0ade1a7f20d9ebf5f62c01819e (diff) | |
There were a couple of problems detected w.r.t. the
"glue" for the nfsclrdma.ko module.
- When the NFS server has a small reply for a read,
it can choose to not use the reduction chunk
(separate memory area for the read data). I did
not realize this was the case.
- There was a bug in rpc_copy_uio_pages() function
that caused intermittent crashes in memcpy().
This patch fixes the above cases. It uses M_PROTO6
to mark that an RPC reply has used a reduction chunk,
so that read can handle it correctly. Read also now
provides a reduction chunk for all read sizes, since
the worst case for the rest of the read RPC reply is
close to the 1024 byte limit. (NFSv4 uses strings
instead of uid/gid in the attributes and these name
strings can be rather large.)
I wanted to get the "glue" into main so that others
could test the module more easily. Avaliability of
the module will be announced on freebsd-current@ soon.
It should not affect non-RDMA operation.
I've specified a long MFC, since the module still
requires extensive testing and, hopefully, a review.
MFC after: 3 months
Fixes: 884ee8d6c9b4 ("nfscl: Add some glue for client side NFS over RDMA")
Diffstat (limited to 'sample/https-client.c')
0 files changed, 0 insertions, 0 deletions
