afs: Use the per-peer app data provided by rxrpc
authorDavid Howells <dhowells@redhat.com>
Thu, 23 Jan 2025 11:01:55 +0000 (11:01 +0000)
committerDavid Howells <dhowells@redhat.com>
Mon, 10 Mar 2025 09:47:15 +0000 (09:47 +0000)
commit40e8b52fe8c8ab6920ea5f59c5469b6918cce624
treead7e4345ee1117368c42da32886704e30350728b
parentf3a123b25429dc03508e3bf598373005220b7203
afs: Use the per-peer app data provided by rxrpc

Make use of the per-peer application data that rxrpc now allows the
application to store on the rxrpc_peer struct to hold a back pointer to the
afs_server record that peer represents an endpoint for.

Then, when a call comes in to the AFS cache manager, this can be used to
map it to the correct server record rather than having to use a
UUID-to-server mapping table and having to do an additional lookup.

Signed-off-by: David Howells <dhowells@redhat.com>
cc: Marc Dionne <marc.dionne@auristor.com>
cc: linux-afs@lists.infradead.org
cc: linux-fsdevel@vger.kernel.org
Link: https://lore.kernel.org/r/20250224234154.2014840-14-dhowells@redhat.com/
Link: https://lore.kernel.org/r/20250310094206.801057-10-dhowells@redhat.com/
fs/afs/addr_list.c
fs/afs/cmservice.c
fs/afs/fs_probe.c
fs/afs/internal.h
fs/afs/proc.c
fs/afs/rxrpc.c
fs/afs/server.c
include/trace/events/afs.h
net/rxrpc/peer_object.c