From: "Anthony Brock" <brocka@sterlingcgi.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: RE: [uml-devel] Re: SMP skas requirements
Date: Thu, 30 Mar 2006 22:54:08 -0800 [thread overview]
Message-ID: <LEEIJGBJEEABAGOFFGAHAEGJDFAA.brocka@sterlingcgi.com> (raw)
In-Reply-To: <200603302330.00256.blaisorblade@yahoo.it>
> On Thursday 30 March 2006 13:30, Blaisorblade wrote:
> Sorry, forgot to finish. That patch keeps checking TMP,TMPDIR and
> TEMP (don't
> remember the order), but if none is set, it switches the default
> from /tmp
> to /dev/shm.
This makes sense. It does appear that the patch first checks the
environmental variable before using the defaults. While I would like to take
advantage of the neat feature Jeff is working on (hot plug memory), I have a
greater need for consistent and reliable speed.
Thanks!
Tony
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2006-03-31 6:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 4:36 [uml-devel] Re: SMP skas requirements Jeff Dike
2006-03-29 20:38 ` Anthony Brock
2006-03-30 21:03 ` Blaisorblade
2006-03-30 21:29 ` Blaisorblade
2006-03-31 6:54 ` Anthony Brock [this message]
[not found] <20060320210659.GB6474@ccure.user-mode-linux.org>
[not found] ` <200603280032.31190.blaisorblade@yahoo.it>
2006-03-28 19:45 ` Jeff Dike
[not found] ` <200603290040.01268.blaisorblade@yahoo.it>
[not found] ` <20060329004144.GB24121@ccure.user-mode-linux.org>
2006-03-29 2:47 ` Blaisorblade
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=LEEIJGBJEEABAGOFFGAHAEGJDFAA.brocka@sterlingcgi.com \
--to=brocka@sterlingcgi.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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