From: Eric Dumazet <dada1@cosmosbay.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
mingo@elte.hu, tglx@linutronix.de, torvalds@linux-foundation.org
Subject: Re: [PATCHv3 0/4] sys_indirect system call
Date: Mon, 19 Nov 2007 14:52:24 +0100 [thread overview]
Message-ID: <20071119145224.31ee5242.dada1@cosmosbay.com> (raw)
In-Reply-To: <200711170531.lAH5VaXR025225@devserv.devel.redhat.com>
On Sat, 17 Nov 2007 00:31:36 -0500
Ulrich Drepper <drepper@redhat.com> wrote:
>
> union indirect_params i;
> i.file_flags.flags = O_CLOEXEC;
This setup forbids future addons to file_flags
In three years, when we want to add a new indirect feature to socket()
call, do we need a new indirect2() syscall ?
So I suggest using :
union indirect_params i = {
.file_flags.flags = O_CLOEXEC,
};
fd = syscall (__NR_indirect, &r, &i, sizeof (i));
Or better, you could avoid using 'union indirect_params' in user code, and
only use the substructs for each function.
/* define this in some include file of course */
struct file_flags {
int flags;
};
/* use it */
struct file_flags ff = { .flags = O_CLOEXEC};
fd = syscall (__NR_indirect, &r, &ff, sizeof(ff));
This to avoid to copy to kernel un-necessary data, and permitting futures changes.
next prev parent reply other threads:[~2007-11-19 14:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-17 5:31 Ulrich Drepper
2007-11-18 7:44 ` H. Peter Anvin
2007-11-18 9:36 ` Ulrich Drepper
2007-11-18 19:37 ` H. Peter Anvin
2007-11-20 3:28 ` Ulrich Drepper
2007-11-20 4:27 ` H. Peter Anvin
2007-11-19 13:52 ` Eric Dumazet [this message]
2007-11-19 15:12 ` Ulrich Drepper
2007-11-19 15:43 ` Eric Dumazet
2007-11-19 15:48 ` Ulrich Drepper
2007-11-19 16:14 ` Eric Dumazet
2007-11-19 19:08 ` Ingo Molnar
2007-11-20 14:11 ` dean gaudet
2007-11-20 16:16 ` Ulrich Drepper
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=20071119145224.31ee5242.dada1@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=akpm@linux-foundation.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--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®