From: Werner Almesberger <wa@almesberger.net>
To: Giuliano Pochini <pochini@shiny.it>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Synchronous signal delivery..
Date: Sat, 15 Feb 2003 02:14:02 -0300 [thread overview]
Message-ID: <20030215021402.F2791@almesberger.net> (raw)
In-Reply-To: <20030215012538.E2791@almesberger.net>; from wa@almesberger.net on Sat, Feb 15, 2003 at 01:25:38AM -0300
I wrote:
> ssize_t overwrite(int fd,
> const void *data_if_empty,size_t size_if_empty,
> const void *data_if_full,size_t size_if_full,
> int *was_empty);
Bah, rubbish. Make this
ssize_t overwrite(int fd,const void *data,size_t size);
If the pipe/queue is empty, don't write, and return 0. Now, this
could probably be implemented with a flag to send(2) (then this
wouldn't work for pipes, but you could use socketpair(2) for a
similar effect). Example:
void add_signal(int signum)
{
static int signal_set = 0;
int new_signal = 1 << signum;
int sent;
signal_set |= new_signal;
sent = send(fd,&signal_set,sizeof(int),MSG_OVERWRITE);
if (!sent) {
send(fd,&new_signal,sizeof(int),0);
signal_set = new_signal;
}
}
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
next prev parent reply other threads:[~2003-02-15 5:04 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 19:46 Synchronous signal delivery Linus Torvalds
2003-02-13 20:22 ` Davide Libenzi
2003-02-13 20:25 ` Linus Torvalds
2003-02-13 22:26 ` Davide Libenzi
2003-02-13 22:54 ` Linus Torvalds
2003-02-14 8:55 ` Abramo Bagnara
2003-02-14 14:24 ` Alan Cox
2003-02-14 13:57 ` Abramo Bagnara
2003-02-15 12:36 ` Ingo Oeser
2003-02-15 17:59 ` Abramo Bagnara
2003-02-16 14:52 ` Ingo Oeser
2003-02-15 0:00 ` Davide Libenzi
2003-02-15 0:06 ` Matti Aarnio
2003-02-15 1:08 ` Linus Torvalds
2003-02-15 1:30 ` Jeff Garzik
2003-02-15 1:23 ` Davide Libenzi
2003-02-15 1:03 ` Linus Torvalds
2003-02-15 2:09 ` Davide Libenzi
2003-02-15 20:08 ` Linus Torvalds
2003-02-15 23:39 ` Davide Libenzi
2003-02-17 2:28 ` Jan Harkes
2003-02-15 5:04 ` Keith Adamson
2003-02-15 19:19 ` James Antill
2003-02-15 22:31 ` Davide Libenzi
2003-02-17 23:34 ` James Antill
2003-02-17 15:26 ` Daniel Heater
2003-02-15 4:08 ` Werner Almesberger
2003-02-15 22:00 ` Davide Libenzi
2003-02-16 0:18 ` Werner Almesberger
2003-02-17 4:46 ` Jamie Lokier
2003-02-13 20:45 ` Paul P Komkoff Jr
2003-02-13 21:25 ` Richard B. Johnson
2003-03-27 21:40 ` watching for file creation completion [was Re: Synchronous signal delivery..] Alexander Kellett
2003-02-14 2:40 ` Synchronous signal delivery Jamie Lokier
2003-02-14 3:11 ` Keith Adamson
2003-02-14 3:54 ` Keith Adamson
2003-02-15 0:04 ` Davide Libenzi
2003-02-15 1:01 ` Jamie Lokier
2003-02-15 1:12 ` Randy.Dunlap
2003-02-15 1:50 ` Davide Libenzi
2003-02-15 2:08 ` Jamie Lokier
2003-02-15 4:09 ` Davide Libenzi
2003-02-15 4:34 ` Jamie Lokier
2003-02-14 10:55 ` Giuliano Pochini
2003-02-14 13:04 ` Keith Adamson
2003-02-15 4:25 ` Werner Almesberger
2003-02-15 5:14 ` Werner Almesberger [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-14 7:09 Dan Kegel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030215021402.F2791@almesberger.net \
--to=wa@almesberger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pochini@shiny.it \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox