From: Igor Zhbanov <izh1979@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Re: Idea: Feature information / extensions dispatcher syscall.
Date: Wed, 22 Apr 2009 18:46:56 +0400 [thread overview]
Message-ID: <f44001920904220746k356550abk6783b8cae003685d@mail.gmail.com> (raw)
In-Reply-To: <f44001920904220732h2d6d18cfwef53af31bb218b87@mail.gmail.com>
2009/4/22 Andi Kleen <andi@firstfloor.org>:
> Igor Zhbanov <izh1979@gmail.com> writes:
>>
>> This allow to use system calls in any extension modules without need to reserve
>> syscall number in kernel source and allow binaries to run correctly on
>> any kernel
>> (where that extension feature can have another syscall number).
>>
>> What do you think?
>
> You're trying to reinvent the vfs / device nodes / ioctls
Perhaps.
But in some cases syscalls are more convenient than reading/writing/ioctling
in /proc, /sys or /dev.
Now as I understand creating new syscalls for "home" use is not encourahed.
It is not guaranteed that tomorrow new syscall will not be introduced
in mainstream kernel. So portability issues is not considered for
"home" modules.
And I suggest to regulate syscalls usage and reserve a set of numbers
"home" modules used in some organizations only.
I don't think that they all will use only devices and /proc and /sys
to communicate
with their modules.
next prev parent reply other threads:[~2009-04-22 14:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 14:12 Igor Zhbanov
2009-04-22 14:18 ` Andi Kleen
[not found] ` <f44001920904220732h2d6d18cfwef53af31bb218b87@mail.gmail.com>
2009-04-22 14:46 ` Igor Zhbanov [this message]
2009-04-22 15:12 ` Alan Cox
2009-04-22 15:22 ` Igor Zhbanov
2009-04-22 15:33 ` Alan Cox
2009-04-22 14:48 ` Igor Zhbanov
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=f44001920904220746k356550abk6783b8cae003685d@mail.gmail.com \
--to=izh1979@gmail.com \
--cc=linux-kernel@vger.kernel.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®