Aravinda VK 0827c74916 Do not allocate memory manually while creating RPC buffer ...

Sunrpc Read buffer was created by allocating `1MiB` each time when
client connects. Go can automatically expand the buffer when required
so now empty buffer is initialized.(`1MiB` per brick connect is `1GB`
for 1000 bricks)

Signed-off-by: Aravinda VK <avishwan@redhat.com>

2018-12-19 14:40:45 +05:30

..

clientcodec.go

Fix minor lint and logging issues

2018-02-22 08:47:05 +05:30

cmux_matcher.go

Import sunrpc into pkg

2018-02-09 11:17:36 +05:30

errors.go

format error strings: error strings should not

2018-06-20 16:21:29 +05:30

message_types.go

Import sunrpc into pkg

2018-02-09 11:17:36 +05:30

portmapper.go

format error strings: error strings should not

2018-06-20 16:21:29 +05:30

procedure_registry.go

format error strings: error strings should not

2018-06-20 16:21:29 +05:30

program_types.go

Import sunrpc into pkg

2018-02-09 11:17:36 +05:30

record.go

Do not allocate memory manually while creating RPC buffer

2018-12-19 14:40:45 +05:30

servercodec.go

Fix #1321: acceptLoop keeps a list of all sessions, and each session keeps a reference to the memory block allocated as a read buffer. This reference is there even if the session closes, so as long as acceptLoop runs, memory keeps growing. This should fix it by doing two things: 1) When session closes, remove the reference to the buffer. But that will still continue to leak sessions, because nothing removes elements from the session list. So, 2) remove the logic that keep track of sessions, instead, run two goroutines for each session, one to keep the session and run the server, and the other to terminate the first one when needed.

2018-12-07 09:07:46 +05:30