On 15.11.19 13:42, Lange Norbert wrote:
Hello,
Just for consideration, If you can pass both error value and # of successfully
sent packets out of the kernel function,
perhaps you could return the # (if > 0) and still set errno in case of an
(real) error?
It would be somewhat different to Linu
nly
difference (like theres no way to block until all msgs are sent/received).
Norbert
> -Original Message-
> From: Xenomai On Behalf Of Jan Kiszka
> via Xenomai
> Sent: Freitag, 15. November 2019 10:43
> To: Philippe Gerum ; Xenomai
>
> Subject: Re: [PATCH] rtdm: Do not r
On 15.11.19 10:39, Philippe Gerum wrote:
On 11/15/19 10:37 AM, Philippe Gerum via Xenomai wrote:
On 11/14/19 7:59 PM, Jan Kiszka wrote:
From: Jan Kiszka
This is in line with Linux behavior.
We likely still miss an equivalent to sk_err in recvmmsg, though.
Ack. Tracing on early exit due to
On 11/15/19 10:37 AM, Philippe Gerum via Xenomai wrote:
> On 11/14/19 7:59 PM, Jan Kiszka wrote:
>> From: Jan Kiszka
>>
>> This is in line with Linux behavior.
>>
>> We likely still miss an equivalent to sk_err in recvmmsg, though.
>
> Ack. Tracing on early exit due to null vlen in sendmmsg() is
On 11/14/19 7:59 PM, Jan Kiszka wrote:
> From: Jan Kiszka
>
> This is in line with Linux behavior.
>
> We likely still miss an equivalent to sk_err in recvmmsg, though.
Ack. Tracing on early exit due to null vlen in sendmmsg() is still missing;
having this might help in debugging issue(s) at c
