Re: [9fans] going too far?

2013-02-20 Thread Anthony Martin
I sent out a CL that should reduce the time that this takes. Can you try it out? https://codereview.appspot.com/7369044/ Thanks, Anthony

Re: [9fans] going too far?

2013-02-19 Thread Anthony Martin
lu...@proxima.alt.za once said: > I think the Go tool does cover C programs and even (somebody will > correct me if I'm wrong, I hope) assembler ones. It would be silly if > it didn't, or at least hard to use for things like the runtime. One > of Go's weak spots is that a lot of unconventional be

Re: [9fans] going too far?

2013-02-19 Thread lucio
> On 19 February 2013 10:05, Bruce Ellis wrote: > >> i could only presume that the #includes are expected to be in the first >> block. > > > that would be all right, I suppose, but I didn't think the go command > compiled C programs as well > (or at least, that's what I'd read). It's a bit like

Re: [9fans] going too far?

2013-02-19 Thread Charles Forsyth
On 19 February 2013 10:05, Bruce Ellis wrote: > i could only presume that the #includes are expected to be in the first > block. that would be all right, I suppose, but I didn't think the go command compiled C programs as well (or at least, that's what I'd read). It's a bit like PIP, though, so

Re: [9fans] going too far?

2013-02-19 Thread Bruce Ellis
i could only presume that the #includes are expected to be in the first block. On 19 February 2013 20:32, Charles Forsyth wrote: > > On 18 February 2013 19:23, andrey mirtchovski wrote: > >> sorry, not all source files, just the 'import' section. > > > I could see the relevance of reading the co

Re: [9fans] going too far?

2013-02-19 Thread Charles Forsyth
On 18 February 2013 19:23, andrey mirtchovski wrote: > sorry, not all source files, just the 'import' section. I could see the relevance of reading the contents 7 times (since there were separate go clean requests), but it wasn't clear to me why it was apparently reading 4k from each file in th

Re: [9fans] going too far?

2013-02-18 Thread erik quanstrom
On Mon Feb 18 22:10:05 EST 2013, mirtchov...@gmail.com wrote: > > there's 32-bits of tag space. why *can't* 9p do multiple outstanding? > > i wrote it in py9p. it worked fine when we tested it between sandia > and calgary couple of years ago. we promptly forgot about it :) my problem with the us

Re: [9fans] going too far?

2013-02-18 Thread erik quanstrom
that's about 90 minute delay. odd. here are the interesting headers; it seems internal to 9fans.net Received: from gw17.lax01.mailroute.net ([199.89.0.117]) [...] Tue, 19 Feb 2013 03:55:18 + (GMT) Received: from ladd.quanstro.net (ladd.quanstro.net [69.55.170.73]) by gw17.lax

Re: [9fans] going too far?

2013-02-18 Thread erik quanstrom
> i did not receive this message (gmail to blame?), but based on this i am subscribed twice, and 9fans sometimes never sends a message to a particular address. there's no pattern that i've seen - erik

Re: [9fans] going too far?

2013-02-18 Thread Charles Forsyth
On 18 February 2013 19:23, andrey mirtchovski wrote: > sorry, not all source files, just the 'import' section. In nemo's example, it seemed to have wandered off into go/src/cmd, reading 4k from everything there each time, which began to add up, if I've read the iostats correctly. As to caching

Re: [9fans] going too far?

2013-02-18 Thread erik quanstrom
> both 9p's nature and the lack of caching. i was hoping that one of the > new protocols coming up that do streaming and outstanding requests and > caching could help with this. there's 32-bits of tag space. why *can't* 9p do multiple outstanding? - erik

Re: [9fans] going too far?

2013-02-18 Thread andrey mirtchovski
>> I wonder if there's something about nemo's example >> that gets {go clean ...} wandering through all the src/cmd stuff so often. i did not receive this message (gmail to blame?), but based on this snippet I can reply that you're seeing each file referenced at least 7 times in iostats' output be

Re: [9fans] going too far?

2013-02-18 Thread Charles Forsyth
On 19 February 2013 01:36, Charles Forsyth wrote: > I wonder if there's something about nemo's example > that gets {go clean ...} wandering through all the src/cmd stuff so often. > One difference is that I had floren's code outside the go tree, although it would still need to enter that to gathe

Re: [9fans] going too far?

2013-02-18 Thread andrey mirtchovski
> the go tool necessarily needs to read all source files for all > packages sorry, not all source files, just the 'import' section.

Re: [9fans] going too far?

2013-02-18 Thread andrey mirtchovski
the go tool necessarily needs to read all source files for all packages in the program's include tree to build a list of what may be outdated and needs to be recompiled. linux/osx vfs caching makes this a relatively painless operation (although it's still expensive if you flush the caches manually

Re: [9fans] going too far?

2013-02-18 Thread John Floren
"go clean" does the same thing on Linux under strace, reading the headers from all the .go files of each package's dependencies. I have included the strace output of "strace -e open -f go clean github.com/floren/ellipsoid" below. The help for the command says "Clean removes object files from packa