From: bernd@petrovitsch.priv.at (Bernd Petrovitsch)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Common signal handler system call
Date: Mon, 21 Mar 2011 11:38:25 +0100 [thread overview]
Message-ID: <1300703905.1454.41.camel@thorin> (raw)
In-Reply-To: <AANLkTi=qmrEJPuV4aaien2aDmd09XfbodRPNJ=0=tpTR@mail.gmail.com>
On Son, 2011-03-20 at 13:08 +0530, mohit verma wrote: [...]
> I think it should be there in kernel not because it is my idea but for
> good reasons (personally think so).
... and despite IMHO good reason for not including.
But talk is cheap so prepare and propose a working prototype as patch
and we will see the reaction from others.
I'm not strong against it but I do not see any significant advantage but
at least one open question and the burden to all which do not need/use
it[0].
ad "POSIX compliance": Well, there are lots of system calls (in the
Linux kernel) which are not in POSIX (or SuSv3 or ...) - plain simply
because they are newer than these "standards" or out of the scope of
them.
And (on Linux with and/or without GNU-libc) some system-calls (or
whatever POSIX calls them) are "only" libc functions which are
transformed into other, real existing system-calls.
Bernd
[0]: And that is partly due to my embedded background where you strive
to make everything small and avoid bloat;-)
--
Bernd Petrovitsch Email : bernd at petrovitsch.priv.at
LUGA : http://www.luga.at
next prev parent reply other threads:[~2011-03-21 10:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 19:54 Common signal handler system call mohit verma
2011-03-18 20:02 ` Fwd: " mohit verma
2011-03-18 20:11 ` mohit verma
2011-03-18 20:30 ` Manish Katiyar
2011-03-18 21:12 ` mohit verma
2011-03-19 11:31 ` Bernd Petrovitsch
2011-03-19 14:18 ` mohit verma
2011-03-19 21:43 ` Bernd Petrovitsch
2011-03-20 7:38 ` mohit verma
2011-03-20 14:57 ` Javier Martinez Canillas
2011-03-21 10:38 ` Bernd Petrovitsch [this message]
2011-03-21 12:16 ` mohit verma
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=1300703905.1454.41.camel@thorin \
--to=bernd@petrovitsch.priv.at \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).