From: "Albert Cahalan" <acahalan@gmail.com>
To: "Eric Dumazet" <dada1@cosmosbay.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
"Davide Libenzi" <davidel@xmailserver.org>
Subject: Re: JIT emulator needs
Date: Sat, 9 Jun 2007 00:12:25 -0400 [thread overview]
Message-ID: <787b0d920706082112v25fb118ew3556eb868c118c1c@mail.gmail.com> (raw)
In-Reply-To: <4669009E.3000702@cosmosbay.com>
On 6/8/07, Eric Dumazet <dada1@cosmosbay.com> wrote:
> Albert Cahalan a écrit :
> > Additions to better support JIT emulators:
> >
> > a. sysctl to set IPC_RMID by default
>
> Not very good, this will break some apps.
As a sysctl, the admin gets to choose between
compatibility and sanity.
I can see such a sysctl also being really helpful for a
shared computer used for an Operating Systems or
System Programming course.
> > b. shmget() flag to set IPC_RMID by default
>
> This is better :)
Both are good. This one requires that all apps using
SysV shared memory be modified to use the flag.
The other requires that a very few apps be modified
to tolerate a behavior change.
> > c. open() flag to unlink a file before returning the fd
>
>
> Well, I assume you would like fd = open("/path/somefile", O_RDWR | O_CREAT |
> O_UNLINK, 0644)
>
> (ie allocate a file handle but no name ?)
Yes.
> Quite difficult to implement this atomically with current vfs, maybe a new
> syscall would be better. (Linus will kill me for that :) )
>
> (We dont need to insert "somefile" in one directory, then unlink it, we only
> need to allocate an unnamed inode to get some backing store)
I suspect that SMB/CIFS has a native call for this. There is
some sort of tmpfile flag defined over in that world.
next prev parent reply other threads:[~2007-06-09 4:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 6:35 JIT emulator needs Albert Cahalan
2007-06-08 7:09 ` Eric Dumazet
2007-06-09 4:12 ` Albert Cahalan [this message]
2007-06-08 11:10 ` Alan Cox
2007-06-08 16:35 ` Nicholas Miell
2007-06-09 5:17 ` Albert Cahalan
2007-06-09 20:00 ` H. Peter Anvin
2007-06-19 15:08 ` William Lee Irwin III
2007-06-20 3:16 ` Albert Cahalan
2007-06-20 16:01 ` William Lee Irwin III
2007-06-20 16:37 ` H. Peter Anvin
2007-06-20 17:54 ` William Lee Irwin III
2007-06-20 18:23 ` H. Peter Anvin
2007-06-20 18:25 ` Albert Cahalan
2007-06-20 18:51 ` H. Peter Anvin
2007-06-21 3:21 ` Albert Cahalan
2007-06-21 3:32 ` H. Peter Anvin
2007-06-21 7:38 ` Albert Cahalan
2007-06-20 18:43 ` Albert Cahalan
2007-06-23 3:52 ` Kyle Moffett
2007-06-24 4:14 ` William Lee Irwin III
2007-06-21 17:44 ` Arjan van de Ven
2007-06-22 5:56 ` Albert Cahalan
2007-06-22 13:43 ` Arjan van de Ven
2007-06-22 14:32 ` Albert Cahalan
2007-06-22 14:42 ` Arjan van de Ven
2007-06-23 2:30 ` Albert Cahalan
[not found] <8tGiE-2Hv-1@gated-at.bofh.it>
[not found] ` <8xNvm-2Tw-29@gated-at.bofh.it>
[not found] ` <8xYTM-3So-13@gated-at.bofh.it>
2007-06-21 11:08 ` Bodo Eggert
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=787b0d920706082112v25fb118ew3556eb868c118c1c@mail.gmail.com \
--to=acahalan@gmail.com \
--cc=dada1@cosmosbay.com \
--cc=davidel@xmailserver.org \
--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;
as well as URLs for NNTP newsgroup(s).