Re: [9fans] Go 1.3b1 cmd/pack test takes too long

2014-05-04 Thread Skip Tavakkolian
thanks; i should have checked that. running it on the fossil+venti server brings it down a bit. still, it's not stellar. bootes% go test PASS ok cmd/pack 81.480s bootes% go test PASS ok cmd/pack 79.719s On Sun, May 4, 2014 at 7:51 PM, Anthony Martin wrote: > Skip Tavakkolian once said: >

Re: [9fans] What happened on lib9p?

2014-05-04 Thread Skip Tavakkolian
that means windows is working as expected :) On Sun, May 4, 2014 at 10:34 PM, wrote: > > PS. I played around with Windows go, and got > much frustrated.☺ > > >

Re: [9fans] What happened on lib9p?

2014-05-04 Thread kokamoto
> I'm checking how I can incorporate your nusb codes > into my 'sources' conservative version usb codes. > Of course, it's should be my personal hiden version.☺ I found it unneccessary. The 'sources' usb/disk recognizes partitions already. However, after I applied 9front's kernel codes (not inclu

Re: [9fans] Go 1.3b1 cmd/pack test takes too long

2014-05-04 Thread lucio
> Your numbers don't look entirely abnormal. That test issues > over a million small writes. (Although it really should be > using bufio). Are you suggesting we ought to change pack? I don't mind doing it if it's likely to be accepted by the developers. On NetBSD and my slow Plan 9 network, ther

Re: [9fans] Go 1.3b1 cmd/pack test takes too long

2014-05-04 Thread Anthony Martin
Skip Tavakkolian once said: > is anyone else seeing similar results for cmd/pack? > > % go test > PASS > ok cmd/pack 172.505s > > this is on an atom (d525 @ 1.8ghz, 4gb). same test on an arm (quad core a9 > @ 1.7ghz, 2gb, linux 3.8) takes much less time: > > % go test > PASS > ok cmd/pac

[9fans] Go 1.3b1 cmd/pack test takes too long

2014-05-04 Thread Skip Tavakkolian
is anyone else seeing similar results for cmd/pack? % go test PASS ok cmd/pack 172.505s this is on an atom (d525 @ 1.8ghz, 4gb). same test on an arm (quad core a9 @ 1.7ghz, 2gb, linux 3.8) takes much less time: % go test PASS ok cmd/pack20.872s

Re: [9fans] New /prog idea

2014-05-04 Thread erik quanstrom
On Sun May 4 18:01:22 EDT 2014, yshu...@lynxline.com wrote: > > Just idea, but seriously, why cannot do something like this: > > # cat /prog/new > $id > # cat /dis/ls.dis > /prog/$id/dis > # echo "/" > /prog/$id/cwd > # echo «Running» > /prog/$id/status > > Not to do it which echo/cat, but to

[9fans] New /prog idea

2014-05-04 Thread Oleksandr Iakovliev
Just idea, but seriously, why cannot do something like this: # cat /prog/new > $id # cat /dis/ls.dis > /prog/$id/dis # echo "/" > /prog/$id/cwd # echo «Running» > /prog/$id/status Not to do it which echo/cat, but to have remote access to /prog/new

Re: [9fans] ehci/uhci interrupts

2014-05-04 Thread erik quanstrom
> Despite what one might think at first, writing documentation is not > easier than writing code, and is, IMHO, harder. To write good manual > pages---the Bell Labs man pages are simply great and from reading the i agree with your points, but i think there are two additional facts to consider. 1

Re: [9fans] ehci/uhci interrupts

2014-05-04 Thread erik quanstrom
> > there are lots of small ways to improve things, too. i'd be happy > > to talk about that on or off list. one thing that immediately springs > > to mind is additions to charles' kernel man pages. > > The list is not very busy and, I hate to admit, somewhat remote from > Bell Labs. As a resul

Re: [9fans] ehci/uhci interrupts

2014-05-04 Thread tlaronde
On Sun, May 04, 2014 at 07:12:10AM +0200, lu...@proxima.alt.za wrote: > > Personally, kernel pages would be a god-send Despite what one might think at first, writing documentation is not easier than writing code, and is, IMHO, harder. To write good manual pages---the Bell Labs man pages are simpl