Fix: relayd metadata size
authorMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Wed, 25 Jul 2012 21:39:12 +0000 (17:39 -0400)
committerDavid Goulet <dgoulet@efficios.com>
Thu, 26 Jul 2012 16:25:19 +0000 (12:25 -0400)
commitf64161251bd649abe5b6a473531adfa3af9bd6b6
tree68aeb39d04d2a34759b7695ae56fae68e222fc31
parent2c46f0d263b46ca718618f9bf3e471bf3dffb62d
Fix: relayd metadata size

Trying to see better how the metadata size was handled, I ended up doing
a couple of modifications to the size value sent by the sender: given
that this header contains a size value that should cover both the
metadata packet header size, and the following payload size (this is how
kernel splice sent behaves), I modified kernel/UST mmap to do the same.

I therefore changed the recently updated recv_metadata payload size
calculation to match the encoded size, which should hopefully work for
all kernel splice/mmap and UST mmap cases.

Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Signed-off-by: David Goulet <dgoulet@efficios.com>
src/bin/lttng-relayd/main.c
src/common/kernel-consumer/kernel-consumer.c
src/common/ust-consumer/ust-consumer.c
This page took 0.025366 seconds and 4 git commands to generate.