Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1437207
| From | David Miller <davem@davemloft.net> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH net-next 06/24] rxrpc: Dup the main conn list for the proc interface |
| Date | 2016-07-05 19:20 +0200 |
| Message-ID | <rRCaR-5LK-27@gated-at.bofh.it> (permalink) |
| References | <rRyqB-3hh-3@gated-at.bofh.it> <rRyqC-3hh-39@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
From: David Howells <dhowells@redhat.com> Date: Tue, 05 Jul 2016 14:12:54 +0100 > The main connection list is used for two independent purposes: primarily it > is used to find connections to reap and secondarily it is used to list > connections in procfs. > > Split the procfs list out from the reap list. This allows the reap list to > be phased out in stages as the client conns and service conns acquire their > own separate connection management strategies. > > Whilst we're at it, use the address information stored in conn->proto when > displaying through procfs rather than accessing the peer record. > > Signed-off-by: David Howells <dhowells@redhat.com> 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?
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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