> Very briefly, they are an optimization to avoid a lookup. Instead of
> receiving a port name and looking up the associated object from it,
> we use protected payloads, which are merely user-assigned arbitrary
> values associated to ports, to store the address of the associated
> object directly,
On Tue, Jul 24, 2018 at 08:31:18AM +0200, Joan Lledó wrote:
> > Just to be sure, do you see what protected payloads are ?
>
> I think I don't, to be honest.
Very briefly, they are an optimization to avoid a lookup. Instead of
receiving a port name and looking up the associated object from it,
we
> Just to be sure, do you see what protected payloads are ?
I think I don't, to be honest.
On Sat, Jul 21, 2018 at 10:48:07AM +0200, Joan Lledó wrote:
> I'm blocked with a bug in the lwIP translator that's driving me crazy:
> under some particular circumstances, calling select() over two ports
> results on only one of these io_select RPCs being received by the
> translator. The other one
Hello Hurd,
I'm blocked with a bug in the lwIP translator that's driving me crazy:
under some particular circumstances, calling select() over two ports
results on only one of these io_select RPCs being received by the
translator. The other one is returned to glibc as EOPNOTSUPP.
I debugged enough
