[PATCH net-next 06/24] rxrpc: Dup the main conn list for the proc interface

David Howells dhowells at redhat.com
Tue Jul 5 12:21:38 PDT 2016


David Miller <davem at davemloft.net> wrote:

> Wouldn't it be better to just code the proc stuff to walk whatever
> table the rest of the stack uses to hold all of the connections
> as TCP et al. do?

There won't be "a table" that the rest of the stack uses.  There will be more
than one.  Service conns and client conns will be handled separately, they
will have different lifecycle strategies, different lifetimes and separate
object handling code.  It's almost worth actually having separate structs for
them, but there's sufficient common ground that it doesn't actually make
sense, I think.

David



More information about the linux-afs mailing list