From: Francisco J Ballesteros <nemo@lsub.org>
To: erik quanstrom <quanstro@labs.coraid.com>
Cc: 9fans@9fans.net
Subject: Re: [9fans] NIX 64-bit kernel is available
Date: Thu, 15 Sep 2011 16:42:20 +0200 [thread overview]
Message-ID: <CA+N-5baFk3464kjBRr54x+14=3J-tab_h+5D9PiGDezpjxBEhQ@mail.gmail.com> (raw)
In-Reply-To: <f3f098de7f5c908e757a63a8294ca28e@coraid.com>
In the experiments I made I was sending all results through shared memory
(a pointer to the reply).
But I don't think that code is in the main rep.
On Thu, Sep 15, 2011 at 4:13 PM, erik quanstrom
<quanstro@labs.coraid.com> wrote:
> On Thu Sep 15 10:04:54 EDT 2011, nemo@lsub.org wrote:
>> I could run old binaries. Perhaps profiling no longer works for them,
>> didn't even try.
>> Either way, we had no choice. We had to put some stuff in there.
>
> i wasn't complaining. i just wanted to make sure. also, for the
> nixcalls, where does the error string memory go?
>
> - erik
>
>
next prev parent reply other threads:[~2011-09-15 14:42 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAP6exYKf6RL6J8MU1E3vc4y_TarbYzowkeHdTrpZ1Q5ved9faQ@mail.gmail.c>
2011-09-15 4:39 ` erik quanstrom
2011-09-15 7:28 ` Nemo
2011-09-15 9:39 ` Francisco J Ballesteros
2011-09-15 13:17 ` erik quanstrom
2011-09-15 14:02 ` Francisco J Ballesteros
[not found] ` <CA+N-5bYxuADQJ1e2PChv7RZA8DdpHcqvnotX7jSnSPxxYK1Bbw@mail.gmail.c>
2011-09-15 14:13 ` erik quanstrom
2011-09-15 14:42 ` Francisco J Ballesteros [this message]
2011-09-14 21:13 erik quanstrom
-- strict thread matches above, loose matches on Subject: below --
2011-09-14 15:41 ron minnich
2011-09-14 15:58 ` andrey mirtchovski
2011-09-14 16:06 ` Jeff Sickel
2011-09-14 17:32 ` David Leimbach
2011-09-14 17:40 ` ron minnich
2011-09-14 17:51 ` Francisco J Ballesteros
2011-09-14 20:38 ` s s
2011-09-14 20:42 ` John Floren
2011-09-14 20:50 ` Gabriel Díaz López de la Llave
2011-09-14 20:52 ` s s
2011-09-14 21:32 ` Bakul Shah
2011-09-14 21:48 ` John Floren
2011-09-14 22:10 ` Dan Cross
2011-09-17 20:45 ` Brantley Coile
2011-09-14 22:36 ` Nick LaForge
2011-09-14 22:44 ` ron minnich
2011-09-16 17:48 ` Jack Johnson
2011-09-14 20:50 ` Lluís Batlle i Rossell
2011-09-14 21:12 ` ron minnich
2011-09-14 20:56 ` Francisco J Ballesteros
2011-09-14 21:11 ` ron minnich
2011-09-14 19:22 ` Bakul Shah
2011-09-14 19:30 ` Francisco J Ballesteros
2011-09-14 21:10 ` ron minnich
2011-09-14 21:38 ` Bakul Shah
2011-09-14 21:48 ` ron minnich
2011-09-14 22:08 ` yy
[not found] ` <CADErNDukvepbqiUEObGMY7Fba__kG953wmtNdUSFPEwwqSnHVw@mail.gmail.c>
2011-09-14 22:12 ` erik quanstrom
2011-09-14 22:32 ` hiro
2011-09-15 1:10 ` David Leimbach
[not found] ` <CAP6exY+iHDpy+dig3Rvi6WHjv8k8sajOwJ3AjMxKADvoSZqtDw@mail.gmail.c>
2011-09-14 21:14 ` erik quanstrom
2011-09-14 21:33 ` Charles Forsyth
2011-09-14 21:14 ` Don Bailey
2011-09-15 10:19 ` Christian Neukirchen
2011-09-15 10:34 ` Francisco J Ballesteros
2011-09-15 10:39 ` hiro
2011-09-15 10:42 ` Francisco J Ballesteros
2011-09-15 10:50 ` Christian Neukirchen
2011-09-15 11:07 ` Noah Evans
2011-09-15 11:11 ` Noah Evans
2011-09-15 11:57 ` Christian Neukirchen
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='CA+N-5baFk3464kjBRr54x+14=3J-tab_h+5D9PiGDezpjxBEhQ@mail.gmail.com' \
--to=nemo@lsub.org \
--cc=9fans@9fans.net \
--cc=quanstro@labs.coraid.com \
/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).