tree 6c26857428486f81a45750f1c407d3660046a7ef
parent 1b5750109ef3a365e2c60b112ad35a48f690fbee
author Jeremy Kerr <jk@ozlabs.org> 1486464010 +0800
committer Jeremy Kerr <jk@ozlabs.org> 1498546502 +0800

server: use ringbuffer for all handlers

Currently, we use the a ringbuffer within the socket handler to manage
bursts of data to slower clients.

However, we're also seeing cases where the local tty handler becomes
blocking as well. So, we want to implement a buffer within the tty
handler too.

This change moves the ringbuffer 'up a layer' - from the socket handler
to the core console code.

We remove the ->data_in callback from handlers, and work on the
assumption that handlers have registered their own consumer on the
console's ringbuffer (through a new helper function,
console_ringbuffer_consumer_register()).

Change-Id: Ie8f02d6632578c50bb5e2dfb9bee6ece86432135
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>