Re: Running out of buffers?

[Robert Elz <kre%munnari.OZ.AU@localhost>]

    Date:        Fri, 27 Apr 2018 05:18:16 +0100
    From:        Roy Marples <roy%marples.name@localhost>
    Message-ID:  <58598dae-238e-44a5-e74f-bbb2fdd7bdfc%marples.name@localhost>

  | No-one has yet weighed in on how this should be resolved.

Go back to silently discarding the error (at least, by default).
Datagram type services (which is what the routing socket,
and others like it, are) generally are just "best effort" with
no error reporting at all.   The higher level protocol needs to
cope.

However, some kind of sockioctl() to enable error reporting
would be OK, for applications that actually need to know
(but they still need to cope with data lost for other reasons.)

What might be interesting to discover however, is just why
there are so many routing socket errors with the buffer space
exhausted - particularly on a huge system like Paul's.  I would
have expected this to be rare assuming everything else is
working correctly.

kre