8 ms·
RISC creator is pushing open source chips
- reitzensteinm 12y agoAssuming Moore's Law is slowing down, and there's no rabbit about to be pulled out of a hat by Intel or others, it's going to close the gap significantly between what is possible on an $x billion and an $x million budget. This makes it a great time for initiatives such as this to take place. In 2001, an unexpected delay of 18 months could mean that you release to competition running at 2ghz instead of 1ghz. These days, Intel's 32nm, 22nm chips (and 14nm, from what is known about Broadwell) are more or less identical from a consumer's perspective. As an aside, Patterson's book (coauthored with Hennessey), Computer Architecture: A Quantitative Approach, is one of the best I've ever read. Right up there with SICP.
- richardwhiuk 12y agoDefinitely agree about the quality of Hennessey and Patterson's Computer Architecture book. I think the reason that the 32nm, 22nm and 14nm chips are identical from a consumer approach is because of two issues. One is marketing - we no longer have convincing benchmarks that are as persuasive as the GHz a chip would support. It was a questionable metric anyway, but it now isn't being pursued (for a whole number of reasons). The second is an application space problem - consumer applications are no longer exploiting CPU improvements in the same manner. That's partially because we now get more parallelism rather than single threaded speed, but it's partial a testament to the success of the previous generation as to the breadth of tasks a current PC will happily perform in a reasonable time frame.
- pjmlp 12y agoYes, the time to update the computer every three years to keep up with the progress is now gone. Maybe when we finally get to quantum computers a similar cycle will happen, but to the dismay of OEMs the cycle is gone. Even mobiles already reached the same peak and are mostly driven by contract renewals nowadays, not features.
- XorNot 12y agoDisagree on the causes. We're limited by mobile energy storage. Desktops are as powerful as anyone needs - largely because you just buy the appropriate size - at least at the consumer level. Laptops, phones? Definitely not. But the push for more isn't being limited by our performance, it's being limited by energy demands. I'm shopping for a new laptop at the moment, and my overriding requirement is to get the most WHr's of battery into a low energy configuration. And even there, to some extent the problem is also not where you'd think - you can take a modern i5 down to something like 1.5W idle consumption. Most of the losses are switching circuits or the screen.
- pjmlp 12y agoThe issue, as you correctly state, is power consumption and there we still have quite some room for improvement. Other than that, we also have same hybrid multi-core devices on our pockets that we have on our desks. Coupled with all the hardware sensors one can imagine. So besides the power consumption point you rise, there is hardly anything else to improve at hardware level. Except maybe, for things like better voice recognition experience or holographic displays a la Star Wars.
- TeMPOraL 12y ago> but to the dismay of OEMs the cycle is gone Don't worry, they won't give up without a fight. I bet they'll try to push some artificial reasons for people to keep throwing away perfectly good machines every two years.
- jarek 12y agoMaybe they can put some really fragile components in a computer people carry around? Have them be really shiny and look great to help marketing too.
- TeMPOraL 12y agoAnd then maybe they could make it impossible to repair the broken part for less than a third of a new device. "Tight integration streamlines the production, makes everything cheaper", they could say.
- darkmighty 12y agoI think we're at a bridging moment. Most computing tasks we came up on the last decades which were very hard to get done are now trivial with some optimization. Yet the general purpose ("universal") algorithms we dreamed of are still not in reach -- it's easy to think of an evolutionary algo huge neural net to do AI, but in practice universality implies (still) inaccessible search spaces. So hrdware looks as if standing still.
- userbinator 12y agoAs someone who has watched the "RISC revolution" and the claims its proponents have been making since the 80s, I'm not so optimistic on what will happen. Initially it was all about increasing clock frequency to make up for increased instruction counts and decreased code density, but Intel's Netburst showed that this strategy was a dead end. Then the focus was on power efficiency, which is still a close battle today. I don't think it's a matter of budget; AMD has much less to spend than Intel, yet it makes x86 CPUs that are still quite competitive even if they're not as fast - the gap between them is nowhere near their differences in budget. It seems that things are more like "fast, cheap, power-efficient: pick two". This related paper is an interesting read: http://research.cs.wisc.edu/vertical/papers/2013/isa-power-struggles-tr.pdf http://research.cs.wisc.edu/vertical/papers/2013/isa-power-s... I think x86 still has plenty of room for optimisation, and Intel are just doing it slowly according to market conditions. An open-source x86 core would be great - in fact, pre-MMX-level x86 is fully open, as all the patents on that have expired now.
- pjmlp 12y agoI also lived through it, but I would say that RISC won in the end, just not exactly as its proponents thought. x86 are no longer real CISC, as they moved the internal architecture to RISC, starting with the Pentium 4. And all the other processors that matter are also RISC. The real loosers were the VLIW proponents.
- taeric 12y agoSounds suspicious to claim victory while redefining terms. :) I'm curious which processors that matter are all RISC. I mean, I realize there are a fair bit of chips out there. I wouldn't have thought many of them really fit the original RISC mold. Sure, they have less instructions than some of the old behemoths. But, that is a far cry from the aims of RISC. There is also the rise in specialized processors. Combining that with the increased focus on consolidating everything into one chip, and much of the debate is just weird nowdays.
- pjmlp 12y ago
- DCKing 12y agoWell there's two predictions you can think about that could happen sometime in the future: 1. Nobody can put more than XXX transistors on a square millimeter (where XXX is some physical limit to chip material) 2. "Everybody" can put YYY transistors on a square millimeter (where YYY is a number sufficiently close to XXX so that the difference does not matter much) The first means some stagnation in the chip market: not only does Moore's Law not apply anymore, but not even does a weak version of Moore's Law ("chips tend to get faster/cheaper over time") apply. But if that scenario becomes true, it doesn't necessarily mean that the democratization of the second scenario becomes true. The ability to put YYY transistors on a square millimeter could still be limited to a select few companies investing billions in the production of these chips. After all, how many fabs worldwide are currently capable of producing 45nm chips, which could be considered "commodity" [1]? Is it really true that it becomes much cheaper to produce chips on smaller process nodes over time? Sure it becomes cheaper since less original R&D is necessary, but is it reasonable to think that producing 20nm chips ever becomes a question of investing anything less than, say, 100s of millions? Does the second scenario ever become true, at least in the forseeable future? I don't know much about chip fabs so I wonder if someone more knowledgeable could share some insight on this. [1]: I genuinely don't know the answer to this, but I don't suppose it's very widespread?
- mechagodzilla 12y agoThese days, Intel is an unusual model in that they own the whole 'stack', from processor design to fabrication, packaging, etc. To replicate that costs 10s of billions of dollars. To get your own chip produced using a 'pure-play' fab (which, these days, basically means TSMC, and to a lesser extent Samsung and GloFo), however, is much cheaper. If you want a 20nm chip, you design your chip (basically the cost is just engineering effort + CAD tools..a few million $$), send it to TSMC (getting masks made is another few million $$), and they send you back chips. Reality is slightly more complicated, in that you're using using an integrator to manage the relationship with TSMC, the packaging company, the testing company, etc., but a startup with $10-20 million could probably scrape together a decent 20nm chip. Once TSMC has built a new fab though, the longer it is 'relevant' the cheaper they can make the wafers, as they have more wafers to amortize the ~$10 billion or whatever it cost to build the fab over.
- stephencanon 12y ago> These days, Intel's 32nm, 22nm chips (and 14nm, from what is known about Broadwell) are more or less identical from a consumer's perspective. That’s a little bit of a stretch. 32nm was Westmere -> Sandybridge, which doubled FP throughput and L1 load bandwidth, among other changes. Haswell doubled FP throughput again, doubled integer SIMD throughput, and doubled L1 load and store bandwidth, among several other significant changes, and there’s also been a steady ~10% per generation improvement in generic IPC. Consumers don’t care about those numbers, but they do care about some of the operations they enable getting faster. (In fairness, this often lags the release of the processors by a year or two as SW re-optimization is required to take advantage of new features; the full benefit of the changes isn’t available to consumers until some time after the processors are released, by which time we’ve all forgotten just how slow our old hardware was.) The energy footprint of those processors has shrunken considerably in the same time, which is a huge improvement for portables.
- valarauca1 12y ago>The energy footprint of those processors has shrunken considerably in the same time, which is a huge improvement for portables. Yes and no. The Westermere, Sandybridge, Ivybridge, Haskell, Devil Cannon's line isn't really targeted for the mobile market. The shinking power budget is caused by 2 things. 1) To stay competitive against 64bit ARM processors. Intel processors are barely used in mobile devices. But eventually ARM will attempt to transition into laptop/desktop/server and compete with Intel directly, this is where lower power comes into play. 2) Feature set. New features (functionality) on chip cost not just dye space, but cost power and heat. The heat and power are the far most critical issues. The second issue is commedically addressed in, "The Cold Winter" a satirical document about hardware engineering. "The idea of creating more and more cores ran into an issue. Most people don't use their computer simulating 4 nuclear explosions while rendering Avatar in 1080p. They use their computer for precisely 10 things, of which 6 of things involve pornography. The other issue was the 600 core dub 'Hydra of Destiny' was so smart that its design document was the best chess player in the facility. The issue was it required its own dedicated coal fired plant, and would run so hot that it would melt its way into the earth's core." - The Cold Winter (paraphased)
- asb 12y agoIf you'd like to be paid to work on a fully open-source RISC-V SoC, we're hiring. See http://lowrisc.org http://lowrisc.org
- igravious 12y agoTalking about the RISC-V Instruction Set Architecture http://riscv.org/ http://riscv.org/ Why would you need 128bit addressing? Isn't 64bit address space plenty big? This isn't a "nobody'll need more than 640k scenario, right?" https://gigaom2.files.wordpress.com/2014/08/requirements-table.gif https://gigaom2.files.wordpress.com/2014/08/requirements-tab...
- unwind 12y agoThere's motivation in the relevant part (RV128I Base Integer Instruction Set), starting on page 81 of the 2.0 ISA specification (https://s3-us-west-1.amazonaws.com/riscv.org/riscv-spec-v2.0.pdf https://s3-us-west-1.amazonaws.com/riscv.org/riscv-spec-v2.0...). A choice quote: It is not clear when a flat address space larger than 64 bits will be required. At the time of writing, the fastest supercomputer in the world as measured by the Top500 benchmark had over 1 PB of DRAM, and would require over 50 bits of address space if all the DRAM resided in a single address space. Some warehouse-scale computers already contain even larger quantities of DRAM, and new dense solid-state non-volatile memories and fast interconnect technologies might drive a demand for even larger memory spaces. Exascale systems research is targeting 100 PB memory systems, which occupy 57 bits of address space. At historic rates of growth, it is possible that greater than 64 bits of address space might be required before 2030.
- userbinator 12y agoif all the DRAM resided in a single address space Key point, and that's a huge "if". All large systems are NUMA, and trying to treat that like a uniform address space will be absolutely horrible because of the extreme latencies that arise.
- rch 12y agoYou're correct of course, but I wanted to point out that people shouldn't dismiss everything >64 bit out of hand based on this reasoning. There are architectures that can make use of those extra bits, and not just for addressing a universe of RAM. The Transmeta processors weren't perfect or anything, but there's merit in the VLIW approach. The first generation Crusoe chip was a 128 bit part, and the second was 256 bit; this was a decade ago, in chips designed for ultra-light consumer laptops. As I understand it, some key people from Transmeta ended up at P.A. Semi, which of course was acquired by Apple in 2008. I wouldn't be at all surprised if we're talking about VLIW architectures again by 2016 or at least 2020. - https://en.wikipedia.org/wiki/Transmeta_Efficeon https://en.wikipedia.org/wiki/Transmeta_Efficeon - https://en.wikipedia.org/wiki/Very_long_instruction_word https://en.wikipedia.org/wiki/Very_long_instruction_word
- deleted 12y ago[deleted]
- Narishma 12y agoFrom the article: "Popular chip architectures historically have been locked down behind strict licensing rules by companies such as Intel, ARM and IBM (although IBM has opened this up a bit for industry partners with its OpenPower foundation)." IBM's new openness isn't really open at all. It's just what ARM has always been doing: they allow you to pay them a lot of money so you can use their ISA in your CPU.
- PinguTS 12y agoPlease explain: What would be the benefit of an open source chip? At the end of the day, the chip is a physical thing that have to be produced by someone. As long as there is no 3D printer, which can build nano structures to makes chips, I can only implement it into a FPGA. The main FPGA providers are either Altera or Xilinx and both a very expansive. So they are good for prototyping or very low volume. But for anything beyond, I need a specific implementation. Okay, I could go to a foundry like Samsung (or other) and order according to my design. But, even that requires a very high volume in the millions to make it affordable and viable from a business perspective. Especially, if it is intended for the IoT market. On the other side, I can buy ARM Cortex M0 and Cortex M1 for cheap from NXP and other for less than $1. They are power full and power consumption is very low. Just to mention, the other day the WRTnode[1] was released for less den $25 or look at an Raspberry PI Compute. Don't get me wrong, Yes, I would like to see those with an open source chip. But would that be really a viable business case, except from the University context? [1] http://wrtnode.com/ http://wrtnode.com/
- sp332 12y agoI can buy ARM Cortex M0 and Cortex M1 for cheap from NXP and other for less than $1 So imagine how cheap these new CPUs could be!
- FigBug 12y agoArm licensing fees are about 1% - 2%, so these new chips would be less than $0.98?
- worklogin 12y agoWhat's the point of an open source operating system? Most people buy their computing device with the OS installed, so the cost is marginal.
- PinguTS 12y agoYou are not from the hardware business? In hardware design you cannot build a "minimal viable product" and then do "continuous integration" from that on. A hardware product either works within its defined limits or it doesn't. Then, depending on your limitations, you need additional approval by FCC, FDA, and such organizations within the US alone. The same thing then with their counterparts in every different country. Chip design is then the next level up. Because changing a mask later on, because you found a bug, means you produced a million chips just for the dust bin. That means the entry barrier into hardware, especially chips, is very high.
- Zigurd 12y agoThis paper http://www.eecs.berkeley.edu/Pubs/TechRpts/2014/EECS-2014-146.pdf http://www.eecs.berkeley.edu/Pubs/TechRpts/2014/EECS-2014-14... pointed to in the article posted here, claims higher performance per Mhz and lower power consumption than ARM in table 2. Still, that requires some chip maker to build a SoC around a RISC-V CPU that attains these efficiencies in the real world. The paper makes these arguments for RISC-V: • Greater innovation via free-market competition from many more designers, including open vs. proprietary implementations of the ISA. • Shared open core designs, which would mean shorter time to market, lower cost from reuse, fewer errors given many more eyeballs3 , and transparency that would make it hard, for example, for government agencies to add secret trap doors. • Processors becoming affordable for more devices, which helps expand the Internet of Things (IoTs), which could cost as little as $1 The first point is not very concrete. China has long had some of their own MIPS-based RISC CPU designs, and they are most likely to act on the transparency issue. That leaves super-cheap processors for IoT. ARM may be able to deliver pricing and value that's better than free. And all this assumes very low friction in the form of, say, Android adding this ISA to the standard set of compilation targets for native code, and, to ART pre-compilation.
- comatose_kid 12y agoDavid gave a nice lecture on RAID over a decade ago when I was taking a computer architecture class at Stanford. Perhaps the next edition of his textbook (bible for computer architecture) should use RISC-V, it would probably help as a learning aid and spread the gospel about RISC-V. Of course, it's possible that the current edition of the text already does this.
- alricb 12y agoChicken, meet egg: We did not include special instruction set support for over ow checks on integer arithmetic operations. Most popular programming languages do not support checks for integer overflow, partly because most architectures impose a signicant runtime penalty to check for overflow on integer arithmetic and partly because modulo arithmetic is sometimes the desired behavior. [1] Please Regehr, don't hurt them. [2] [1] Spec, section 2.4 https://s3-us-west-1.amazonaws.com/riscv.org/riscv-spec-v2.0.pdf https://s3-us-west-1.amazonaws.com/riscv.org/riscv-spec-v2.0... [2] http://blog.regehr.org/archives/1154 http://blog.regehr.org/archives/1154
- tachyonbeam 12y agoI happen to be implementing my own JavaScript JIT compiler and I can tell you that SpiderMonkey, V8 and my compiler all perform a lot of overflow checks. This is because in JavaScript, all numbers are doubles, but JITs typically try to represent them as integers where possible, because integer operations have lower latency. Scheme and Common Lisp also rely on overflow checks to optimize small integers as "fixnums" instead of always using arbitrary precision arithmetic. Not having hardware support for overflow checks would complicate the implementation of many dynamic languages, and reduce their performance significantly. Not sure what this guy was thinking. It can't be that hard to implement some overflow flag you can branch on, I mean, adders basically produces that information for free, don't they? Seems like a poor design choice.
- ajb 12y agoHmm; carry is free, not sure about overflow. But more generally, it's an extra output, for what would otherwise be one-output operations. Put it this way - if a lot of javascript operations could modify a piece of global state, that would be trivial on a trivial interpreter, but I bet it would add a lot of complexity to your JIT. Same goes for CPUs - no problem for simple implementations, but it would add complexity to an out-of-order or other clever microarchitecture.
- kps 12y ago> Hmm; carry is free, not sure about overflow. Overflow is just the final carry out XOR the second-last carry bit, so it's practically free. Of course RISC-V doesn't have a carry bit either!
- TheMagicHorsey 12y agoIs licensing an ARM core really a barrier in a business/community venture, once you take into account the enormous costs of just getting a fab to make your chip? I feel like the fabbing cost is so high, that at that scale, the CPU license fee is really nothing. Correct me if I am wrong. This is coming from the mind of someone who knows next to nothing about how hardware is really made.
- aidenn0 12y agoI think the bigger consideration is that the ARM IP is encumbered. You can't tweak it and publish the changes you made.
- ksec 12y agoExactly my thoughts. Licensing the ARMv8 is cheap, getting it to fab is expensive. And the current trends goes more advance nodes will be more expensive. Hence the move to smaller node will no longer be as much about getting cheaper. Until 450mm wafer comes out, which still does not have a proper schedule.
- krmboya 12y agoMaybe a bit OT, but I've just started learning programming for MMIX, Donald Knuth's RISC computer. I've been wondering when, or if, it could one day be implemented in hardware.
- niix 12y agoEvery time I hear "RISC Architecture" I think of the movie Hackers.
- ChuckMcM 12y agoPerhaps the most important contribution Linux has made to the world is that because of its impact, you can run an OS on nearly any instruction set architecture (ISA). That drops a pretty huge barrier in terms of getting to something from nothing. On RISC-V though, unless it was some sort of SoC (which most people won't build) I don't see the impact. But carrying that line a bit further ... One of the challenges that Microchip has faced was that the affinity for C that the ATMega architecture had from rival Atmel meant it lost a few significant design wins (Arduino perhaps the most serious). They could use RISC-V to try to offset the Atmel SAM series. But other than that I don't see the motivation for folks to not use ARM, granted a full processor license would be expensive but if you are looking at volumes where that would be an advantage, it isn't that expensive.