mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ulrich Drepper" <drepper@gmail.com>
To: "Davide Libenzi" <davidel@xmailserver.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"Ingo Molnar" <mingo@elte.hu>
Subject: Re: [patch 0/6] sys_indirect RFC - sys_indirect introduction
Date: Sun, 1 Jul 2007 09:25:40 -0700	[thread overview]
Message-ID: <a36005b50707010925k5c936c1ch2238b560c595a833@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706301529310.2957@alien.or.mcafeemobile.com>

On 6/30/07, Davide Libenzi <davidel@xmailserver.org> wrote:
> This is how all those overloaded syscalls looks like, BTW:
> [...]
> How would you do that with a single shared strcture, w/out adding in all
> signal paths the knowledge of the structure?

You said it yourself: each individual wrapper would look like this.
Generalization really isn't possible, you'll have each wrapper syscall
looking different.  This means there is no reason to try coming up
with some overly complicated data structure which would only be useful
if the processing of that data structure could be centralized.

  reply	other threads:[~2007-07-01 16:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-29 21:48 Davide Libenzi
2007-06-30  1:48 ` Ulrich Drepper
2007-06-30 19:23   ` Davide Libenzi
2007-06-30 21:54     ` Ulrich Drepper
2007-06-30 22:27       ` Davide Libenzi
2007-06-30 22:32         ` Davide Libenzi
2007-07-01 16:25           ` Ulrich Drepper [this message]
2007-07-01 17:09             ` Davide Libenzi
2007-07-02 14:09               ` Ulrich Drepper
2007-07-02 22:37                 ` Davide Libenzi
2007-07-03  0:28                   ` Ulrich Drepper
2007-07-03  0:37                     ` 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=a36005b50707010925k5c936c1ch2238b560c595a833@mail.gmail.com \
    --to=drepper@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=davidel@xmailserver.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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®