On Monday 05 of September 2011 06:42:35 ron minnich wrote:
> The TSC has been badly abused by the chip makers over the last ten
> years. It went through a period of time where it had poor accuracy. Be
> sure to look at your hardware and make sure it's a later chip which
> will give you reasonable T
On Mon, Sep 5, 2011 at 1:44 AM, Skip Tavakkolian wrote:
> try
>
> ./read time
>
> a better choice is "cl" client, which lets you navigate the namespace
> the file server is serving. the -d flag lets you see what is being
> passed around.
>
> $ ../../srv/examples/timefs &
> [1] 3681
> $ ./read tim
try
./read time
a better choice is "cl" client, which lets you navigate the namespace
the file server is serving. the -d flag lets you see what is being
passed around.
$ ../../srv/examples/timefs &
[1] 3681
$ ./read time
Sun Sep 4 22:32:00 PDT 2011$
$ ./cl
9p> ls
time
inftime
9p> cat time
Sun S
Sorry, wrong thread.
- Leonard
>
On Mon, Sep 5, 2011 at 12:42 AM, ron minnich wrote:
> The TSC has been badly abused by the chip makers over the last ten
> years. It went through a period of time where it had poor accuracy. Be
> sure to look at your hardware and make sure it's a later chip which
> will give you reasonable TSC be
On Mon Sep 5 00:43:49 EDT 2011, rminn...@gmail.com wrote:
> The TSC has been badly abused by the chip makers over the last ten
> years. It went through a period of time where it had poor accuracy. Be
> sure to look at your hardware and make sure it's a later chip which
> will give you reasonable T
> On Sun, Sep 4, 2011 at 9:03 PM, Skip Tavakkolian <
> skip.tavakkol...@gmail.com> wrote:
>
>> ...
>> go9p (Go)
>>
>> ...
>>
>> -Skip
>
>
Compiled and ran go9p/p/srv/examples/timefs.go.
Compiled and ran go9p/p/clnt/examples/read.go.
Output was ...
2011/09/05 00:40:13 invalid arguments
Success?
The TSC has been badly abused by the chip makers over the last ten
years. It went through a period of time where it had poor accuracy. Be
sure to look at your hardware and make sure it's a later chip which
will give you reasonable TSC behavior.
ron
On Sun, Sep 4, 2011 at 9:03 PM, Skip Tavakkolian wrote:
> here are a few you can google for:
>
> styx-n-9p (Java)
> limbo-machine (JavaScript)
> go9p (Go)
>
> they include the customary client and server examples. there are
> implementations in many other languages; however COBOL and FORTRAN
> im
here are a few you can google for:
styx-n-9p (Java)
limbo-machine (JavaScript)
go9p (Go)
they include the customary client and server examples. there are
implementations in many other languages; however COBOL and FORTRAN
implementations are currently missing.
-Skip
On Sun, Sep 4, 2011 at 5:34 P
Dear 9fans,
Looking for a hello world example, between client and server, conversing
with 9p.
A google search for "9p hello world" returned basically nothing.
It seems like there might be a hello world example for libixp ...
http://www.anarchyinthetubes.com/src/hello_libixp
Looking for an exam
On Sun Sep 4 14:34:41 EDT 2011, r...@swtch.com wrote:
> asm(stackaddress) is bogus not because of libmach
> but because asm is defined to disassemble from the
> text file, not from memory. Run 'whatis asm' in acid and
> notice that it says @addr++ not *addr++.
clearly. but that's not what i'm c
On Sun Sep 4 13:48:31 EDT 2011, st...@quintile.net wrote:
> after the recent discussions on nsec()...
>
> does anyone already have the snippet of code to do fine grained
> timeings on the x86 platform using the hardware performance counters?
>
> I would use nsec() but I'am timing systemcalls so
asm(stackaddress) is bogus not because of libmach
but because asm is defined to disassemble from the
text file, not from memory. Run 'whatis asm' in acid and
notice that it says @addr++ not *addr++.
after the recent discussions on nsec()...
does anyone already have the snippet of code to do fine grained
timeings on the x86 platform using the hardware performance counters?
I would use nsec() but I'am timing systemcalls so I expect my results
would be swamped by nsec()'s performance.
Thanks
forgot to include a proposed fix
; diffy -c 8db.c
/n/dump/2011/0904/sys/src/libmach/8db.c:2060,2066 - 8db.c:2060,2066
USED(modifier);
op = mkinstr(map, &instr, pc);
if (op == 0) {
- errstr(buf, n);
+ // errstr(buf, n);
return -1;
it appers that either i386das and i386inst are misnamed, or they
are listed incorrectly in /sys/src/libmach/8db.c. since at least [v7]db
follow the same pattern, i'm pretty sure the header file is wrong.
also i believe the setting of errstr() in i386das and i386inst is incorrect.
(for a demonstra
i've updated avr.9gz, including a few new files, including the MAC code, and
supporting Limbo applications
(which i haven't run recently)
Last week I said:
I will send my code at the end of next week: I
still need time to clean it and to try to resolve
some imperfections and inconsistencies.
I'll be late.
Last week I also said:
Another thing that annoy me is that I receive
swipe-up and swi
19 matches
Mail list logo