kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: martinez.javier@gmail.com (Javier Martinez Canillas)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Common signal handler system call
Date: Sun, 20 Mar 2011 15:57:01 +0100	[thread overview]
Message-ID: <AANLkTinUXuqAA3tuWBmz3-QMSvkxC=FeMVby8cPYuHvX@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=qmrEJPuV4aaien2aDmd09XfbodRPNJ=0=tpTR@mail.gmail.com>

On Sun, Mar 20, 2011 at 8:38 AM, mohit verma <mohit89mlnc@gmail.com> wrote:
>> Well, you can implement your idea as a library function too.
>> Apart from the "just for fun" factor or to learn how to implement a new
>> system call, I see no real gain to move that into kernel.
>
> I think it should be there in kernel not because it is my idea but for good
> reasons (personally think so).
>>

Hi Mohit,

A problem I see with your idea is that it is not POSIX-compliant.
Linux being a Unix-like operating system tries to adhere to the
standard as much as possible. Although is true that it is not tied to
the specification. Whenever a change has strong arguments (an more
important valid use cases) Linux can deviate from the standard.

But as Bernd says, taking to the kernel something that can be done in
users-pace with no real gain and also breaking POSIX signals semantics
is something that will be hard to merge into the kernel.

Also, to implement a syscall you have to convince not only the kernel
developers that this change makes sense but also propose a patch to
glibc to implement a function library that uses your new syscall.

Best regards,

-----------------------------------------
Javier Mart?nez Canillas
(+34) 682 39 81 69
PhD Student in High Performance Computing
Computer Architecture and Operating System Department (CAOS)
Universitat Aut?noma de Barcelona
Barcelona, Spain

  reply	other threads:[~2011-03-20 14:57 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 [this message]
2011-03-21 10:38               ` Bernd Petrovitsch
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='AANLkTinUXuqAA3tuWBmz3-QMSvkxC=FeMVby8cPYuHvX@mail.gmail.com' \
    --to=martinez.javier@gmail.com \
    --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).