From: "Michael K. Edwards" <medwards.linux@gmail.com>
To: "Davide Libenzi" <davidel@xmailserver.org>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
"David M. Lloyd" <dmlloyd@flurg.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: [patch 2/5] signalfd v2 - signalfd core ...
Date: Thu, 8 Mar 2007 08:40:12 -0800 [thread overview]
Message-ID: <f2b55d220703080840xb0a1da0w41051a7c4a7ac4e3@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0703080825420.7015@alien.or.mcafeemobile.com>
On 3/8/07, Davide Libenzi <davidel@xmailserver.org> wrote:
> The reason for the special function, was not to provide a non-blocking
> behaviour with zero timeout (that just a side effect), but to read the
> siginfo. I was all about using read(2) (and v1 used it), but when you have
> to transfer complex structures over it, it becomes hell. How do you
> cleanly compat over a f_op->read callback for example?
Make it a netlink socket and fetch your structures using recvmsg().
siginfo_t belongs in ancillary data.
The UNIX philosophy is "everything's a file". The Berkeley philosophy
is "everything's a socket, except for files, which are feeble
mini-sockets". I'd go with the Berkeley crowd here.
Cheers,
- Michael
next prev parent reply other threads:[~2007-03-08 16:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 1:21 Davide Libenzi
2007-03-08 14:31 ` David M. Lloyd
2007-03-08 15:45 ` Davide Libenzi
2007-03-08 16:22 ` Linus Torvalds
2007-03-08 16:29 ` Davide Libenzi
2007-03-08 16:40 ` Michael K. Edwards [this message]
2007-03-08 17:28 ` Linus Torvalds
2007-03-08 20:53 ` Michael K. Edwards
2007-03-30 23:24 ` Denis Vlasenko
2007-03-08 17:15 ` Linus Torvalds
2007-03-08 19:21 ` Davide Libenzi
2007-03-08 19:27 ` Linus Torvalds
2007-03-08 19:33 ` Davide Libenzi
2007-03-08 20:48 ` Marko Macek
2007-03-08 21:03 ` Marko Macek
2007-03-09 20:22 ` Kent Overstreet
2007-03-08 19:34 ` Avi Kivity
2007-03-08 19:40 ` Davide Libenzi
2007-03-08 23:57 ` Jeremy Fitzhardinge
2007-03-09 0:10 ` Linus Torvalds
2007-03-09 21:33 ` Davide Libenzi
2007-03-08 20:43 Oleg Nesterov
2007-03-08 21:12 ` Davide Libenzi
2007-03-08 21:56 ` Oleg Nesterov
2007-03-08 22:11 ` Linus Torvalds
2007-03-08 22:59 ` Davide Libenzi
2007-03-08 23:05 ` Davide Libenzi
2007-03-09 0:14 ` Oleg Nesterov
2007-03-09 1:16 ` Davide Libenzi
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=f2b55d220703080840xb0a1da0w41051a7c4a7ac4e3@mail.gmail.com \
--to=medwards.linux@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=davidel@xmailserver.org \
--cc=dmlloyd@flurg.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®