Clean-up: consumerd: use a specific status code for get_next_subbuffer
authorJérémie Galarneau <jeremie.galarneau@efficios.com>
Fri, 30 Apr 2021 16:12:44 +0000 (12:12 -0400)
committerJérémie Galarneau <jeremie.galarneau@efficios.com>
Fri, 30 Apr 2021 23:07:03 +0000 (19:07 -0400)
commitb6797c8e4aeb3f7c33be9726ab33655e7667e07e
treee1ea6e1b68d2a2d71eed296e05c00f84e3761917
parent6e5e3c512dd7c4ead8ce89bff2de1a56a6d5e360
Clean-up: consumerd: use a specific status code for get_next_subbuffer

The implementation of "get next subbuffer" of the user space and kernel
tracers return different error codes (-ENODATA and -EAGAIN) which are
are confusing to handle in the generic code.

Since the difference between -ENODATA and -EAGAIN makes no material
difference in the current consumerd implementation, those conditions
are abstracted by a common GET_NEXT_SUBBEFFER_STATUS_NO_DATA.

Otherwise, the callers handle 'OK' and the generic 'ERROR' condition
which makes the transport of more specific "errno" values useless for
the moment.

Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>
Change-Id: Ibdb2837396e4b8cd291ffd80f6ca59b39ce3f707
src/common/consumer/consumer.c
src/common/consumer/consumer.h
src/common/kernel-consumer/kernel-consumer.c
src/common/ust-consumer/ust-consumer.c
This page took 0.025687 seconds and 4 git commands to generate.