log☇︎
199500+ entries in 0.064s
asciilifeform: 'hippi' aha
asciilifeform: (between boards)
asciilifeform: usually there is some interconnection bus.
asciilifeform: but even there, there are not ten thousand on one board
asciilifeform: folks with infinite money do bake own mb, yes
asciilifeform: ever since the '1024 chickens' transition, that is generally how it was done
asciilifeform: can get that many more generic turdboards for same price
asciilifeform: economy of scale
asciilifeform: as always.
asciilifeform: i assume that the folks who a) want this b) can afford it --- have it.
asciilifeform: hell, crossbars.
asciilifeform: (compass arrows)
asciilifeform: or preferably 2d fabric
asciilifeform: ring, yes
asciilifeform: but it got nsa'd
asciilifeform: there was an outfit which sold something quite like this (fpga on sdram stick) and even one in the shape of a cpu, which could sit down in ordinary cpu socket on multisocket mb
asciilifeform: (connection via ram slots is not, as it may appear, lunacy, but could be done with fpga, which would pretend to be a slice of sdram to two boxes at the same time, ignoring refresh cycles and managing locking somehow)
asciilifeform: so the maximal throughputs are virtually never reached in practice
asciilifeform: ethernet, also, has ludicrous cpu overhead
asciilifeform: $$$$$$$
asciilifeform: but i have thought about connecting generic x86 boxen via the ram slots
asciilifeform: and making best use thereof
asciilifeform: nah we're talking about off-the-shelf iron
asciilifeform: (of total ram)
asciilifeform: hell, the 8MB cache of my ancient 'opteron' is more than i had in my 486dx2
asciilifeform: (of the kind i was working on with al schwartz and others)
asciilifeform: good for data-compact number crunching problems
asciilifeform: and no wait-cycles
asciilifeform: (cpu is warm and 'remanence' is a non-issue. think, crypto.)
asciilifeform: i thought about actually making this, some years ago, as it had useful applications
asciilifeform: hypothetically, one could run an x86 box without any ram inserted, given a clever bios made for this occasion.
asciilifeform: (how? 'cache as ram' mode of x86 cpu)
asciilifeform: x86 never runs from rom. not even on warmup when sdram waitstate timer is not yet initialized
asciilifeform: you can - but it takes planning
asciilifeform: but in rom, you need a ram stack/heap and can't simply shit where you eat
asciilifeform: the reason is that you can do local vars ('static' to a 'c' programmer) in ram
asciilifeform: (not one of these things had an mmu, nor was there any conceivable need for such a thing on a single-process os)
asciilifeform: decimation: it was a single address space no matter what
asciilifeform: arguably none of the others needed to be learned..
asciilifeform: the two most useful 'basic' keywords, yes.
asciilifeform: mircea_popescu: 'peek' and 'poke' were sop on c64 and most micros of the time, aha
asciilifeform: exercise for readers: describe -why- it was common (as is today) not to run directly from rom.
asciilifeform: ah
asciilifeform: mircea_popescu: interpreter wasn't in rom on your thing ?
asciilifeform: decimation: c64 was not a z80 box
asciilifeform: definitely after my time.
asciilifeform: vhs tape can hold a surprising amount (helical scan head!) but tends to rot rather quickly
asciilifeform: as late as early 2000s
asciilifeform: incidentally, long after connecting analogue tape decks to computer was a forgotten misery in the west, ru folks were connecting vcr and getting respectable (10-20G) backup
asciilifeform: no special hardware needed
asciilifeform: tape was the mega-storage because just about everyone could beg/borrow/steal a deck
asciilifeform: (his school didn't have tape decks, you had to bring yer own if family had one)
asciilifeform: we didn't have the thing at home. just the tapes
asciilifeform as a boy sometimes listened to his brother's 'bk-0010' tapes
asciilifeform has trouble believing that this came to any good unless you lived next door to the station
asciilifeform: where else are you gonna store
asciilifeform: that was sop
asciilifeform: (see excellent old thread re: this subject)
asciilifeform: we'll know when it comes when the folks who have skin in the game say it did..
asciilifeform: which is why i think that at a certain point the advantage of a 'bitcoin' which can be -understood- will outweigh the danger of failing to enumerate every possible corner case of the original turd when crafting the ada safety-critical bitcoinatron
asciilifeform: even aside from cryptozoological animals like gcc errata
asciilifeform: decimation has a point in that even a very trivial cpp proggy can have very peculiar manifest behaviour
asciilifeform does it regularly, does not relish
asciilifeform: decimation: reading disasm of cpp crapolade is a misery
asciilifeform: bought with dollars ?!
asciilifeform: they had genuine z80 !?
asciilifeform: (on top of the mass-produced sinclair clones)
asciilifeform: decimation: i think every sovblok pesthole had at least two dozen homebrew published z80 things
asciilifeform: the latter is the only reasonable goal, and the only reasonable purpose of the former is to advance it
asciilifeform: alternatively 'i need to fit the code in head'
asciilifeform: decimation: you call it 'i need to instrument the thing in real time and find out'
asciilifeform: decimation: common parlance, as always, is uselessly broad
asciilifeform: a great many ciphertrons sold by nato cocksucker nations (western europe) were actually electronicized versions of 'enigma'-style rotors ☟︎
asciilifeform: in late '80s - early '90s, laughably weak symmetric crypto (even rotor machines !) were still in use worldwide, for instance
asciilifeform: but more broadly against crypto research outside of the castle walls, as a class
asciilifeform: incidentally, it would be a mistake to conclude that nsa was specifically raging against rsa and only it
asciilifeform: (btw it was a very spiffy encyclopaedia and unjustly gets shat on today)
asciilifeform: 'the great soviet encyclopaedia' and the 'corrections' mailed to owners, complete with razor for slicing out 'unpersons', notwithstanding
asciilifeform: (one nice thing about dead trees is that they cannot be doctored remotely)
asciilifeform: i have the dead tree
asciilifeform: http://log.bitcoin-assets.com/?date=29-05-2015#1147415 << this is beautifully and amply documented in 'the electronic privacy papers' by (yes) schneier (pre-lobotomy) ☝︎
asciilifeform: to each man, his favourite crevice
asciilifeform: which comes with 32MB
asciilifeform: mircea_popescu: i want the thing to shoehorn into, e.g., 'hootoo tripmate'
asciilifeform: which is, memory which ought to have been freed, but can -no longer ever be-
asciilifeform: decimation: 'leak' has a precise technical definition
asciilifeform: in that the total footprint does not exceed a certain size
asciilifeform: any that monotonically increases is candidate for a leak. but mod6's test (and mine) suggests that there are no longer leaks in the classical sense
asciilifeform: mircea_popescu: snapshot lets you take counts of live allocs as often as you like
asciilifeform: to do this, you need http://therealbitcoin.org/ml/btc-dev/2015-May/000095.html
asciilifeform: which is running still.
asciilifeform: mircea_popescu: nah this is an entirely other animal, 'igprof.' takes malloc byte counts from a living (!) process
asciilifeform: mircea_popescu: plz read log. these are not leaks...
asciilifeform: there is a hard-ram-bound option, presently unused, and entirely separate from the locks constant. see link in log.
asciilifeform: according to docs, this is not a hard necessity.
asciilifeform: just for bdb
asciilifeform: mircea_popescu: i get a ballooning all the way to ~23M during first few hours of runtime, where it stays (based on pmap data)
asciilifeform: mircea_popescu: re: which ?
asciilifeform: not before.
asciilifeform: if, -after we nuke all of the powerranger cruft- - we end up having to go there - then we go there.