Re: [OE-core] [pseudo] [RFC 1/2] pseudo_ipc.c: Use MSG_NOSIGNAL if available

2018-08-15 Thread Rasmus Villemoes
On 2018-07-11 16:30, Rasmus Villemoes wrote: > MSG_NOSIGNAL has been in Linux since 2.2, and has been standardized in > POSIX 2008. Using that when available avoids the overhead of the two > syscalls to set and restore the SIGPIPE handler. Moreover, we can > eliminate one write() call by making

Re: [OE-core] [pseudo] [RFC 1/2] pseudo_ipc.c: Use MSG_NOSIGNAL if available

2018-08-15 Thread Seebs
On Wed, 15 Aug 2018 10:27:29 +0100 Richard Purdie wrote: > On Wed, 2018-08-15 at 08:59 +0200, Rasmus Villemoes wrote: > > On 2018-07-11 16:30, Rasmus Villemoes wrote: > > > MSG_NOSIGNAL has been in Linux since 2.2, and has been > > > standardized in > > > POSIX 2008. Using that when available

Re: [OE-core] [pseudo] [RFC 1/2] pseudo_ipc.c: Use MSG_NOSIGNAL if available

2018-08-15 Thread Richard Purdie
On Wed, 2018-08-15 at 08:59 +0200, Rasmus Villemoes wrote: > On 2018-07-11 16:30, Rasmus Villemoes wrote: > > MSG_NOSIGNAL has been in Linux since 2.2, and has been standardized > > in > > POSIX 2008. Using that when available avoids the overhead of the > > two > > syscalls to set and restore the

[OE-core] [pseudo] [RFC 1/2] pseudo_ipc.c: Use MSG_NOSIGNAL if available

2018-07-11 Thread Rasmus Villemoes
MSG_NOSIGNAL has been in Linux since 2.2, and has been standardized in POSIX 2008. Using that when available avoids the overhead of the two syscalls to set and restore the SIGPIPE handler. Moreover, we can eliminate one write() call by making use of sendmsg() to do scatter-gather I/O.