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

From	David Howells <dhowells@redhat.com>
Newsgroups	linux.kernel
Subject	Re: [PATCH net-next 06/24] rxrpc: Dup the main conn list for the proc interface
Date	2016-07-05 21:30 +0200
Message-ID	<rREcF-73g-7@gated-at.bofh.it> (permalink)
References	<rRCaR-5LK-27@gated-at.bofh.it> <rRyqB-3hh-3@gated-at.bofh.it> <rRyqC-3hh-39@gated-at.bofh.it> <rRCaR-5LK-27@gated-at.bofh.it>
Organization	Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903

Show all headers | View raw

David Miller <davem@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

Thread

[PATCH net-next 06/24] rxrpc: Dup the main conn list for the proc  interface David Howells <dhowells@redhat.com> - 2016-07-05 15:20 +0200
  Re: [PATCH net-next 06/24] rxrpc: Dup the main conn list for the  proc interface David Miller <davem@davemloft.net> - 2016-07-05 19:20 +0200
    Re: [PATCH net-next 06/24] rxrpc: Dup the main conn list for the proc interface David Howells <dhowells@redhat.com> - 2016-07-05 21:30 +0200
    Re: [PATCH net-next 06/24] rxrpc: Dup the main conn list for the proc interface David Howells <dhowells@redhat.com> - 2016-07-05 22:00 +0200

csiph-web