Wikipedia - Benutzerbeiträge [de]

Kubernetes

2017-06-13T09:09:32Z

Intgr: /* History */ Remove, looks like WP:LEADCLUTTER; Wikipedia is not a dictionary.

{{Infobox software
| title = Kubernetes
| name = Kubernetes
| logo = [[File:Kubernetes (container engine).png|75px]]
| caption =
| developer =
| released = {{Start date and age|2014|06|07|df=yes}}<ref name="github first-commit">{{cite web|url=https://github.com/kubernetes/kubernetes/commit/2c4b3a562ce34cddc3f8218a2c4d11c7310e6d56 |title=First GitHub commit for Kubernetes |work=github.com | date=2014-06-07}}</ref>
| latest release version = 1.6.4<ref name="github releases">{{cite web|url=https://github.com/kubernetes/kubernetes/releases |title=GitHub Releases page |work=github.com | date=2017-05-19}}</ref>
| latest release date = {{release date and age|2017|05|19}}
| status = Active
| programming language = [[Go (programming language)|Go]]
| operating system = [[Cross-platform]]
| genre = [[Computer cluster#Cluster management|Cluster management software]]
| license = [[Apache License]] 2.0
| website = {{URL|kubernetes.io}}
| posix compliant =
}}

'''Kubernetes''' (commonly referred to as "[[Numeronym|K8s]]") is an [[open-source]] system for automating deployment, scaling and management of [[Container (virtualization)|containerized]] applications<ref>{{Cite web|url=http://github.com/kubernetes/kubernetes/|title=kubernetes/kubernetes|website=GitHub|language=en|access-date=2017-03-28}}</ref> that was originally designed by [[Google]] and donated to the [[Cloud Native Computing Foundation]]. It aims to provide a "platform for automating deployment, scaling, and operations of application containers across clusters of hosts".<ref>{{Cite web|url=https://kubernetes.io/docs/concepts/overview/what-is-kubernetes/|title=What is Kubernetes?|website=Kubernetes|access-date=2017-03-31}}</ref> It supports a range of container tools, including [[Docker (software)|Docker]].

== History ==
Kubernetes (Greek for "[[helmsman]]" or "pilot") was founded by Joe Beda, Brendan Burns and Craig McLuckie,<ref>{{Cite web|url=https://www.wired.com/2015/06/google-kubernetes-says-future-cloud-computing/|title=Google Made Its Secret Blueprint Public to Boost Its Cloud|language=en-US|access-date=2016-06-27}}</ref> was quickly joined by other Google engineers including Brian Grant and Tim Hockin, and was first announced by Google in mid-2014.<ref>{{cite web|title=Google Open Sources Its Secret Weapon in Cloud Computing|url=https://www.wired.com/2014/06/google-kubernetes/|website=Wired|accessdate=24 September 2015}}</ref> Its development and design are heavily influenced by [[Google Borg|Google's Borg system]],<ref>{{cite journal|author1=Abhishek Verma|author2=Luis Pedrosa|author3=Madhukar R. Korupolu|author4=David Oppenheimer|author5=Eric Tune|author6=John Wilkes|title=Large-scale cluster management at Google with Borg|journal=Proceedings of the European Conference on Computer Systems (EuroSys)|date=April 21–24, 2015|url=https://research.google.com/pubs/pub43438.html}}</ref><ref>{{Cite web|url=http://queue.acm.org/detail.cfm?id=2898444|title=Borg, Omega, and Kubernetes - ACM Queue|website=queue.acm.org|access-date=2016-06-27}}</ref> and many of the top contributors to the project previously worked on Borg. The original codename for Kubernetes within Google was Project [[Seven of Nine|Seven]], a reference to a [[Star Trek]] character that is a 'friendlier' [[Borg (Star Trek)|Borg]].<ref>{{Cite news|url=http://www.eweek.com/cloud/early-stage-startup-heptio-aims-to-make-kubernetes-friendly.html|title=Early Stage Startup Heptio Aims to Make Kubernetes Friendly|access-date=2016-12-06}}</ref> The seven spokes on the wheel of the Kubernetes logo is a nod to that codename.

Kubernetes v1.0 was released on July 21, 2015.<ref>{{cite web|title=As Kubernetes Hits 1.0, Google Donates Technology To Newly Formed Cloud Native Computing Foundation|url=http://techcrunch.com/2015/07/21/as-kubernetes-hits-1-0-google-donates-technology-to-newly-formed-cloud-native-computing-foundation-with-ibm-intel-twitter-and-others/|website=TechCrunch|accessdate=24 September 2015}}</ref> Along with the Kubernetes v1.0 release, Google partnered with the [[Linux Foundation]] to form the [[Linux Foundation#Cloud Native Computing Foundation|Cloud Native Computing Foundation]] (CNCF)<ref>{{cite web|url=https://cncf.io/|title=Cloud Native Computing Foundation}}</ref> and offered Kubernetes as a seed technology.

[[Rancher Labs]] includes a Kubernetes distribution in its Rancher container management platform.<ref>{{Cite news|url=http://rancher.com/kubernetes/|title=Deploy and Manage Kubernetes Clusters {{!}} Rancher Labs|work=Rancher Labs|access-date=2017-04-15|language=en-US}}</ref> It is also being used by [[Red Hat]] for its OpenShift product,<ref>{{cite web|title=OpenShift v3 Platform Combines Docker, Kubernetes|url=https://blog.openshift.com/openshift-v3-platform-combines-docker-kubernetes-atomic-and-more/|website=blog.openshift.com|accessdate=14 August 2014}}</ref><ref>{{cite web|title=Why Red Hat Chose Kubernetes for OpenShift|url=https://blog.openshift.com/red-hat-chose-kubernetes-openshift/|website=blog.openshift.com|accessdate=7 November 2016}}</ref> CoreOS for its Tectonic product, and [[IBM]] for its IBM Spectrum Conductor for Containers product.<ref>{{cite web|title=IBM Spectrum Conductor for Containers|url=https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/W1559b1be149d_43b0_881e_9783f38faaff|website=ibm.com/developerWorks|access-date=2017-05-19|language=en-US}}</ref>{{Primary source inline|date=May 2017}}

== Design ==
Kubernetes defines a set of building blocks ("primitives") which collectively provide mechanisms for deploying, maintaining, and scaling applications. The components which make up Kubernetes are designed to be [[Loose coupling|loosely coupled]] and extensible so that it can meet a wide variety of different workloads. The extensibility is provided in large part by the Kubernetes API, which is used by internal components as well as extensions and containers running on Kubernetes.<ref name="do-intro">{{cite web|title=An Introduction to Kubernetes|url=https://www.digitalocean.com/community/tutorials/an-introduction-to-kubernetes|website=DigitalOcean|accessdate=24 September 2015}}</ref>

=== Pods ===
The basic scheduling unit in Kubernetes is called a "pod". It adds a higher level of abstraction to containerized components. A pod consists of one or more containers that are guaranteed to be co-located on the host machine and can share resources.<ref name="do-intro" /> Each pod in Kubernetes is assigned a unique (within the cluster) [[IP address]], which allows applications to use ports without the risk of conflict.<ref name="kubernetes-101-networking">{{cite web |url=http://www.dasblinkenlichten.com/kubernetes-101-networking/ |title=Kubernetes 101 – Networking |last=Langemak |first=Jon |work=Das Blinken Lichten |date=2015-02-11 |accessdate=2015-11-02 }}</ref> A pod can define a volume, such as a local disk directory or a network disk, and expose it to the containers in the pod.<ref name="kubernetes-for-developers">{{cite web |last=Strachan |first=James |url=https://medium.com/fabric8-io/kubernetes-for-developers-2a9c7202fcd3#.b6u76jxar |title=Kubernetes for Developers |work=[[Medium (publishing platform)]] |date=2015-05-21 |accessdate=2015-11-02 }}</ref> Pods can be manually managed through the Kubernetes [[API]], or their management can be delegated to a controller.<ref name="do-intro" />

=== Labels and selectors ===
Kubernetes enables clients (users or internal components) to attach key-value pairs called "labels" to any API object in the system, such as pods and nodes{{Definition needed|date=February 2017}}. Correspondingly, "label selectors" are queries against labels that resolve to matching objects.<ref name="do-intro" />

Labels and selectors are the primary grouping mechanism in Kubernetes, and are used to determine the components to which an operation applies.<ref name="containerizing-docker-on-Kubernetes">{{cite news |last=Surana |first=Ramit |url=https://www.linkedin.com/pulse/containerizing-docker-kubernetes-ramit-surana |title=Containerizing Docker on Kubernetes |work=[[LinkedIn]] |date=2015-09-16 |accessdate=2015-11-02 }}</ref>

For example, if the Pods of an application have labels for a system <code>tier</code> ("<code>front-end</code>", "<code>back-end</code>", for example) and a <code>release_track</code> ("<code>[[Feature toggle#Canary release|canary]]</code>", "<code>production</code>", for example), then an operation on all of the "<code>back-end</code>" and "<code>canary</code>" nodes could use a label selector such as the following:<ref name="redhat-docker-and-kubernetes-training-labels-examples">{{cite web |url=http://christianposta.com/slides/docker/generated/day2.html#/label-examples |title=Intro: Docker and Kubernetes training - Day 2 |publisher=[[Red Hat]] |date=2015-10-20 |accessdate=2015-11-02}}</ref>
<blockquote><code>tier=back-end AND release_track=canary</code></blockquote>

=== Controllers ===
A controller is a reconciliation loop that drives actual cluster state toward the desired cluster state.<ref name="coreos-replication-controller">{{cite web |url=https://coreos.com/kubernetes/docs/latest/replication-controller.html |title=Overview of a Replication Controller |work=Documentation |publisher=[[CoreOS]] |accessdate=2015-11-02 }}</ref> It does this by managing a set of pods. One kind of controller is a "Replication Controller," which handles replication and scaling by running a specified number of copies of a pod across the cluster. It also handles creating replacement pods if the underlying node fails.<ref name="coreos-replication-controller" /> Other controllers that are part of the core Kubernetes system include a "DaemonSet Controller" for running exactly one pod on every machine (or some subset of machines), and a “Job Controller” for running pods that run to completion, e.g. as part of a batch job.<ref name="exciting-experimental-features">{{cite web |url=http://www.livewyer.com/blog/2015/10/02/kubernetes-exciting-experimental-features |title=Kubernetes: Exciting Experimental Features |last=Sanders |first=Jake |work=Livewyer |date=2015-10-02 |accessdate=2015-11-02 }}</ref> The set of pods that a controller manages is determined by label selectors that are part of the controller’s definition.<ref name="redhat-docker-and-kubernetes-training-labels-examples"/>

=== Services ===
A Kubernetes service is a set of pods that work together, such as one tier of a [[Multitier architecture|multi-tier]] application. The set of pods that constitute a service are defined by a label selector.<ref name="do-intro" />
Kubernetes provides [[service discovery]] and request routing by assigning a stable IP address and [[DNS name]] to the service, and load balances traffic in a [[Round-robin DNS|round-robin]] manner to network connections of that IP address among the pods matching the selector (even as failures cause the pods to move from machine to machine).<ref name="kubernetes-101-networking" /> By default a service is exposed inside a cluster (e.g. [[Front and back ends|back end]] pods might be grouped into a service, with requests from the front-end pods load-balanced among them), but a service can also be exposed outside a cluster (e.g. for clients to reach frontend pods)<ref name="kubernetes-101-external-access">{{cite web |url=http://www.dasblinkenlichten.com/kubernetes-101-external-access-into-the-cluster/ |title=Kubernetes 101 – External Access Into The Cluster |last=Langemak |first=Jon |work=Das Blinken Lichten |date=2015-02-15 |accessdate=2015-11-02 }}</ref>

== Architecture ==
[[File:kubernetes.png|600px|thumb|Kubernetes architecture diagram]]

Kubernetes follows the [[Master/slave (technology)|master-slave architecture]].The components of Kubernetes can be divided into those that manage an individual [[Node (networking)|node]] and those that are part of the control plane.<ref name="do-intro" /><ref name=":0">{{cite web|title=Kubernetes Infrastructure|url=https://docs.openshift.org/latest/architecture/infrastructure_components/kubernetes_infrastructure.html|website=OpenShift Community Documentation|publisher=OpenShift|accessdate=24 September 2015}}</ref>

=== Kubernetes control plane ===
The Kubernetes Master is the main controlling unit of the cluster that manages its workload and directs communication across the system. The Kubernetes control plane consists of various components, each its own process, that can run both on a single master node or on multiple masters supporting [[high-availability cluster]]s.<ref name=":0" /> The various components of Kubernetes control plane are as follows:

==== etcd ====
'''[https://github.com/coreos/etcd etcd]''' is a persistent, lightweight, distributed, key-value data store developed by [[CoreOS]] that reliably stores the configuration data of the cluster, representing the overall state of the cluster at any given point of time. Other components watch for changes to this store to bring themselves into the desired state.<ref name=":0" />

==== API server ====
The API server is a key component and serves the Kubernetes [[Application programming interface|API]] using [[JSON]] over [[Hypertext Transfer Protocol|HTTP]], which provides both the internal and external interface to Kubernetes.<ref name="do-intro" /><ref name=":1">{{Cite web|url=http://kamalmarhubi.com/blog/2015/09/06/kubernetes-from-the-ground-up-the-api-server/|title=Kubernetes from the ground up: API server|last=Marhubi|first=Kamal|date=2015-09-26|website=|publisher=kamalmarhubi.com|access-date=2015-11-02}}</ref> The API server processes and validates [[Representational state transfer|REST]] requests and updates state of the [[Application programming interface|API]] objects in [https://github.com/coreos/etcd etcd], thereby allowing clients to configure workloads and containers across Worker nodes.

==== Scheduler ====
The scheduler is the pluggable component that selects which node an unscheduled pod (the basic entity managed by the scheduler) should run on based on resource availability. Scheduler tracks resource utilization on each node to ensure that workload is not scheduled in excess of the available resources. For this purpose, the scheduler must know the resource requirements, resource availability and a variety of other user-provided constraints and policy directives such as quality-of-service, affinity/anti-affinity requirements, data locality and so on. In essence, the scheduler’s role is to match resource “supply” to workload “demand”. <ref>{{cite web|url=http://rancher.com/three-pillars-kubernetes-container-orchestration/|title=The Three Pillars of Kubernetes Container Orchestration - Rancher Labs|date=18 May 2017|website=rancher.com|accessdate=22 May 2017}}</ref>

==== Controller manager ====
The controller manager is the process that the core Kubernetes controllers like DaemonSet Controller and Replication Controller run in. The controllers communicate with the API server to create, update and delete the resources they manage (pods, service endpoints, etc.)<ref name=":1" />

=== Kubernetes node ===
The Node also known as Worker or Minion is the single machine (or [[virtual machine]]) where containers(workloads) are deployed. Every node in the cluster must run the container [[Runtime system|runtime]] (such as [[Docker (software)|Docker]]), as well as the below mentioned components, for communication with master for network configuration of these containers.

==== Kubelet ====
Kubelet is responsible for the running state of each node (that is, ensuring that all containers on the node are healthy). It takes care of starting, stopping, and maintaining application containers (organized into pods) as directed by the control plane.<ref name="do-intro" /><ref>{{Cite web|url=http://kamalmarhubi.com/blog/2015/08/27/what-even-is-a-kubelet/|title=What [..] is a Kubelet?|last=Marhubi|first=Kamal|date=2015-08-27|website=|publisher=kamalmarhubi.com|access-date=2015-11-02}}</ref>

Kubelet monitors the state of a pod and if not in the desired state, the pod will be redeployed to the same node. The node status is relayed every few seconds via heartbeat messages to the master. Once the master detects a node failure, the Replication Controller observes this state change and launches pods on other healthy nodes.{{citation needed|date=October 2016}}

==== Kube-proxy ====
The kube-proxy is an implementation of a [[Proxy server|network proxy]] and a [[Load balancing (computing)|load balancer]], and it supports the service abstraction along with other networking operation.<ref name="do-intro" /> It is responsible for routing traffic to the appropriate container based on IP and port number of the incoming request.

==== cAdvisor ====
cAdvisor is an agent that monitors and gathers resource usage and performance metrics such as CPU, memory, file and network usage of containers on each node.

== References ==
{{Reflist|30em}}

== External links ==
* {{Official website|http://kubernetes.io/}}
* {{GitHub|https://github.com/kubernetes/kubernetes}}

{{Virtualization software}}
{{Linux Containers}}

[[Category:Cloud infrastructure]]
[[Category:Free software for cloud computing]]
[[Category:Free software programmed in Go]]
[[Category:Linux Containerization]]
[[Category:Software using the Apache license]]
[[Category:Virtualization-related software for Linux]]

Kubernetes

2017-05-19T21:50:00Z

Intgr: Copyedit; request non-primary source

{{Infobox software
| title = Kubernetes
| name = Kubernetes
| logo = [[File:Kubernetes (container engine).png|75px]]
| caption =
| developer =
| released = {{Start date and age|2014|06|07|df=yes}}<ref name="github first-commit">{{cite web|url=https://github.com/kubernetes/kubernetes/commit/2c4b3a562ce34cddc3f8218a2c4d11c7310e6d56 |title=First GitHub commit for Kubernetes |work=github.com | date=2014-06-07}}</ref>
| latest release version = 1.6.1<ref name="github releases">{{cite web|url=https://github.com/kubernetes/kubernetes/releases |title=GitHub Releases page |work=github.com | date=2017-04-03}}</ref>
| latest release date = {{release date and age|2017|04|03}}
| status = Active
| programming language = [[Go (programming language)|Go]]
| operating system = [[Cross-platform]]
| genre = [[Computer cluster#Cluster management|Cluster management software]]
| license = [[Apache License]] 2.0
| website = {{URL|kubernetes.io}}
| posix compliant =
}}

'''Kubernetes''' (commonly referred to as "[[Numeronym|K8s]]") is an [[open-source]] system for automating deployment, scaling and management of [[Container (virtualization)|containerized]] applications<ref>{{Cite web|url=http://github.com/kubernetes/kubernetes/|title=kubernetes/kubernetes|website=GitHub|language=en|access-date=2017-03-28}}</ref> that was originally designed by [[Google]] and donated to the [[Cloud Native Computing Foundation]]. It aims to provide a "platform for automating deployment, scaling, and operations of application containers across clusters of hosts".<ref>{{Cite web|url=https://kubernetes.io/docs/concepts/overview/what-is-kubernetes/|title=What is Kubernetes?|website=Kubernetes|access-date=2017-03-31}}</ref> It supports a range of container tools, including [[Docker (software)|Docker]].

== History ==
Kubernetes (from κυβερνήτης: Greek for "helmsman" or "pilot", pronounced 'koo-ber-nay'-tace') was founded by Joe Beda, Brendan Burns and Craig McLuckie,<ref>{{Cite web|url=https://www.wired.com/2015/06/google-kubernetes-says-future-cloud-computing/|title=Google Made Its Secret Blueprint Public to Boost Its Cloud|language=en-US|access-date=2016-06-27}}</ref> was quickly joined by other Google engineers including Brian Grant and Tim Hockin, and was first announced by Google in mid-2014.<ref>{{cite web|title=Google Open Sources Its Secret Weapon in Cloud Computing|url=https://www.wired.com/2014/06/google-kubernetes/|website=Wired|accessdate=24 September 2015}}</ref> Its development and design are heavily influenced by [[Google Borg|Google's Borg system]],<ref>{{cite journal|author1=Abhishek Verma|author2=Luis Pedrosa|author3=Madhukar R. Korupolu|author4=David Oppenheimer|author5=Eric Tune|author6=John Wilkes|title=Large-scale cluster management at Google with Borg|journal=Proceedings of the European Conference on Computer Systems (EuroSys)|date=April 21–24, 2015|url=https://research.google.com/pubs/pub43438.html}}</ref><ref>{{Cite web|url=http://queue.acm.org/detail.cfm?id=2898444|title=Borg, Omega, and Kubernetes - ACM Queue|website=queue.acm.org|access-date=2016-06-27}}</ref> and many of the top contributors to the project previously worked on Borg. The original codename for Kubernetes within Google was Project [[Seven of Nine|Seven]], a reference to a [[Star Trek]] character that is a 'friendlier' [[Borg (Star Trek)|Borg]].<ref>{{Cite news|url=http://www.eweek.com/cloud/early-stage-startup-heptio-aims-to-make-kubernetes-friendly.html|title=Early Stage Startup Heptio Aims to Make Kubernetes Friendly|access-date=2016-12-06}}</ref> The seven spokes on the wheel of the Kubernetes logo is a nod to that codename.

Kubernetes v1.0 was released on July 21, 2015.<ref>{{cite web|title=As Kubernetes Hits 1.0, Google Donates Technology To Newly Formed Cloud Native Computing Foundation|url=http://techcrunch.com/2015/07/21/as-kubernetes-hits-1-0-google-donates-technology-to-newly-formed-cloud-native-computing-foundation-with-ibm-intel-twitter-and-others/|website=TechCrunch|accessdate=24 September 2015}}</ref> Along with the Kubernetes v1.0 release, Google partnered with the [[Linux Foundation]] to form the [[Linux Foundation#Cloud Native Computing Foundation|Cloud Native Computing Foundation]] (CNCF)<ref>{{cite web|url=https://cncf.io/|title=Cloud Native Computing Foundation}}</ref> and offered Kubernetes as a seed technology.

It is also being used by [[Red Hat]] for its OpenShift product,<ref>{{cite web|title=OpenShift v3 Platform Combines Docker, Kubernetes|url=https://blog.openshift.com/openshift-v3-platform-combines-docker-kubernetes-atomic-and-more/|website=blog.openshift.com|accessdate=14 August 2014}}</ref><ref>{{cite web|title=Why Red Hat Chose Kubernetes for OpenShift|url=https://blog.openshift.com/red-hat-chose-kubernetes-openshift/|website=blog.openshift.com|accessdate=7 November 2016}}</ref> CoreOS for its Tectonic product, [[Rancher Labs]] for its Rancher container management platform,<ref>{{Cite news|url=http://rancher.com/kubernetes/|title=Deploy and Manage Kubernetes Clusters {{!}} Rancher Labs|work=Rancher Labs|access-date=2017-04-15|language=en-US}}</ref> and [[IBM]] for its IBM Spectrum Conductor for Containers product.<ref>{{cite web|title=IBM Spectrum Conductor for Containers|url=https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/W1559b1be149d_43b0_881e_9783f38faaff|website=ibm.com/developerWorks|access-date=2017-05-19|language=en-US}}</ref>{{Primary source inline|date=May 2017}}

== Design ==
Kubernetes defines a set of building blocks ("primitives") which collectively provide mechanisms for deploying, maintaining, and scaling applications. The components which make up Kubernetes are designed to be [[Loose coupling|loosely coupled]] and extensible so that it can meet a wide variety of different workloads. The extensibility is provided in large part by the Kubernetes API, which is used by internal components as well as extensions and containers running on Kubernetes.<ref name="do-intro">{{cite web|title=An Introduction to Kubernetes|url=https://www.digitalocean.com/community/tutorials/an-introduction-to-kubernetes|website=DigitalOcean|accessdate=24 September 2015}}</ref>

=== Pods ===
The basic scheduling unit in Kubernetes is called a "pod". It adds a higher level of abstraction to containerized components. A pod consists of one or more containers that are guaranteed to be co-located on the host machine and can share resources.<ref name="do-intro" /> Each pod in Kubernetes is assigned a unique (within the cluster) [[IP address]], which allows applications to use ports without the risk of conflict.<ref name="kubernetes-101-networking">{{cite web |url=http://www.dasblinkenlichten.com/kubernetes-101-networking/ |title=Kubernetes 101 – Networking |last=Langemak |first=Jon |work=Das Blinken Lichten |date=2015-02-11 |accessdate=2015-11-02 }}</ref> A pod can define a volume, such as a local disk directory or a network disk, and expose it to the containers in the pod.<ref name="kubernetes-for-developers">{{cite web |last=Strachan |first=James |url=https://medium.com/fabric8-io/kubernetes-for-developers-2a9c7202fcd3#.b6u76jxar |title=Kubernetes for Developers |work=[[Medium (publishing platform)]] |date=2015-05-21 |accessdate=2015-11-02 }}</ref> Pods can be manually managed through the Kubernetes [[API]], or their management can be delegated to a controller.<ref name="do-intro" />

=== Labels and selectors ===
Kubernetes enables clients (users or internal components) to attach key-value pairs called "labels" to any API object in the system, such as pods and nodes{{Definition needed|date=February 2017}}. Correspondingly, "label selectors" are queries against labels that resolve to matching objects.<ref name="do-intro" />

Labels and selectors are the primary grouping mechanism in Kubernetes, and are used to determine the components to which an operation applies.<ref name="containerizing-docker-on-Kubernetes">{{cite news |last=Surana |first=Ramit |url=https://www.linkedin.com/pulse/containerizing-docker-kubernetes-ramit-surana |title=Containerizing Docker on Kubernetes |work=[[LinkedIn]] |date=2015-09-16 |accessdate=2015-11-02 }}</ref>

For example, if the Pods of an application have labels for a system <code>tier</code> ("<code>front-end</code>", "<code>back-end</code>", for example) and a <code>release_track</code> ("<code>[[Feature toggle#Canary release|canary]]</code>", "<code>production</code>", for example), then an operation on all of the "<code>back-end</code>" and "<code>canary</code>" nodes could use a label selector such as the following:<ref name="redhat-docker-and-kubernetes-training-labels-examples">{{cite web |url=http://christianposta.com/slides/docker/generated/day2.html#/label-examples |title=Intro: Docker and Kubernetes training - Day 2 |publisher=[[Red Hat]] |date=2015-10-20 |accessdate=2015-11-02}}</ref>
<blockquote><code>tier=back-end AND release_track=canary</code></blockquote>

=== Controllers ===
A controller is a reconciliation loop that drives actual cluster state toward the desired cluster state.<ref name="coreos-replication-controller">{{cite web |url=https://coreos.com/kubernetes/docs/latest/replication-controller.html |title=Overview of a Replication Controller |work=Documentation |publisher=[[CoreOS]] |accessdate=2015-11-02 }}</ref> It does this by managing a set of pods. One kind of controller is a "Replication Controller," which handles replication and scaling by running a specified number of copies of a pod across the cluster. It also handles creating replacement pods if the underlying node fails.<ref name="coreos-replication-controller" /> Other controllers that are part of the core Kubernetes system include a "DaemonSet Controller" for running exactly one pod on every machine (or some subset of machines), and a “Job Controller” for running pods that run to completion, e.g. as part of a batch job.<ref name="exciting-experimental-features">{{cite web |url=http://www.livewyer.com/blog/2015/10/02/kubernetes-exciting-experimental-features |title=Kubernetes: Exciting Experimental Features |last=Sanders |first=Jake |work=Livewyer |date=2015-10-02 |accessdate=2015-11-02 }}</ref> The set of pods that a controller manages is determined by label selectors that are part of the controller’s definition.<ref name="redhat-docker-and-kubernetes-training-labels-examples"/>

=== Services ===
A Kubernetes service is a set of pods that work together, such as one tier of a [[Multitier architecture|multi-tier]] application. The set of pods that constitute a service are defined by a label selector.<ref name="do-intro" />
Kubernetes provides [[service discovery]] and request routing by assigning a stable IP address and [[DNS name]] to the service, and load balances traffic in a [[Round-robin DNS|round-robin]] manner to network connections of that IP address among the pods matching the selector (even as failures cause the pods to move from machine to machine).<ref name="kubernetes-101-networking" /> By default a service is exposed inside a cluster (e.g. [[Front and back ends|back end]] pods might be grouped into a service, with requests from the front-end pods load-balanced among them), but a service can also be exposed outside a cluster (e.g. for clients to reach frontend pods)<ref name="kubernetes-101-external-access">{{cite web |url=http://www.dasblinkenlichten.com/kubernetes-101-external-access-into-the-cluster/ |title=Kubernetes 101 – External Access Into The Cluster |last=Langemak |first=Jon |work=Das Blinken Lichten |date=2015-02-15 |accessdate=2015-11-02 }}</ref>

== Architecture ==
[[File:kubernetes.png|600px|thumb|Kubernetes architecture diagram]]

Kubernetes follows the [[Master/slave (technology)|master-slave architecture]].The components of Kubernetes can be divided into those that manage an individual [[Node (networking)|node]] and those that are part of the control plane.<ref name="do-intro" /><ref name=":0">{{cite web|title=Kubernetes Infrastructure|url=https://docs.openshift.org/latest/architecture/infrastructure_components/kubernetes_infrastructure.html|website=OpenShift Community Documentation|publisher=OpenShift|accessdate=24 September 2015}}</ref>

=== Kubernetes control plane ===
The Kubernetes Master is the main controlling unit of the cluster that manages its workload and directs communication across the system. The Kubernetes control plane consists of various components, each its own process, that can run both on a single master node or on multiple masters supporting [[high-availability cluster]]s.<ref name=":0" /> The various components of Kubernetes control plane are as follows:

==== etcd ====
'''[https://github.com/coreos/etcd etcd]''' is a persistent, lightweight, distributed, key-value data store developed by [[CoreOS]] that reliably stores the configuration data of the cluster, representing the overall state of the cluster at any given point of time. Other components watch for changes to this store to bring themselves into the desired state.<ref name=":0" />

==== API server ====
The API server is a key component and serves the Kubernetes [[Application programming interface|API]] using [[JSON]] over [[Hypertext Transfer Protocol|HTTP]], which provides both the internal and external interface to Kubernetes.<ref name="do-intro" /><ref name=":1">{{Cite web|url=http://kamalmarhubi.com/blog/2015/09/06/kubernetes-from-the-ground-up-the-api-server/|title=Kubernetes from the ground up: API server|last=Marhubi|first=Kamal|date=2015-09-26|website=|publisher=kamalmarhubi.com|access-date=2015-11-02}}</ref> The API server processes and validates [[Representational state transfer|REST]] requests and updates state of the [[Application programming interface|API]] objects in [https://github.com/coreos/etcd etcd], thereby allowing clients to configure workloads and containers across Worker nodes.

==== Scheduler ====
The scheduler is the pluggable component that selects which node an unscheduled pod should run on based on resource availability. Scheduler tracks resource utilization on each node to ensure that workload is not scheduled in excess of the available resources. For this purpose, the scheduler must know the resource availability and their existing workloads assigned across servers.

==== Controller manager ====
The controller manager is the process that the core Kubernetes controllers like DaemonSet Controller and Replication Controller run in. The controllers communicate with the API server to create, update and delete the resources they manage (pods, service endpoints, etc.)<ref name=":1" />

=== Kubernetes node ===
The Node also known as Worker or Minion is the single machine (or [[virtual machine]]) where containers(workloads) are deployed. Every node in the cluster must run the container [[Runtime system|runtime]] (such as [[Docker (software)|Docker]]), as well as the below mentioned components, for communication with master for network configuration of these containers.

==== Kubelet ====
Kubelet is responsible for the running state of each node (that is, ensuring that all containers on the node are healthy). It takes care of starting, stopping, and maintaining application containers (organized into pods) as directed by the control plane.<ref name="do-intro" /><ref>{{Cite web|url=http://kamalmarhubi.com/blog/2015/08/27/what-even-is-a-kubelet/|title=What [..] is a Kubelet?|last=Marhubi|first=Kamal|date=2015-08-27|website=|publisher=kamalmarhubi.com|access-date=2015-11-02}}</ref>

Kubelet monitors the state of a pod and if not in the desired state, the pod will be redeployed to the same node. The node status is relayed every few seconds via heartbeat messages to the master. Once the master detects a node failure, the Replication Controller observes this state change and launches pods on other healthy nodes.{{citation needed|date=October 2016}}

==== Kube-proxy ====
The kube-proxy is an implementation of a [[Proxy server|network proxy]] and a [[Load balancing (computing)|load balancer]], and it supports the service abstraction along with other networking operation.<ref name="do-intro" /> It is responsible for routing traffic to the appropriate container based on IP and port number of the incoming request.

==== cAdvisor ====
cAdvisor is an agent that monitors and gathers resource usage and performance metrics such as CPU, memory, file and network usage of containers on each node.

== References ==
{{Reflist|30em}}

== External links ==
* {{Official website|http://kubernetes.io/}}
* {{GitHub|https://github.com/kubernetes/kubernetes}}

{{Virtualization software}}
{{Linux Containers}}

[[Category:Cloud infrastructure]]
[[Category:Free software for cloud computing]]
[[Category:Free software programmed in Go]]
[[Category:Linux Containerization]]
[[Category:Software using the Apache license]]
[[Category:Virtualization-related software for Linux]]

Open Container Initiative

2017-03-20T16:59:27Z

Intgr: +Category:Standards organizations; +Category:Linux Containerization; +Category:Linux Foundation projects using HotCat

The '''Open Container Initiative''' ('''OCI''') is a [[Linux Foundation]] project to design open standards for [[operating-system-level virtualization]], most importantly [[Linux containers]].<ref>http://www.informationweek.com/open-container-initiative-finds-footing-in-linux-foundation/d/d-id/1323439</ref> There are currently two specifications in development and in use: Runtime Specification (runtime-spec) and the Image Specification (image-spec).

OCI develops '''runC''', a container runtime that implements their specification and serves as a basis for other higher-level tools.

==References==
{{Reflist}}

==External links==
*[https://www.opencontainers.org/ Open Container Initiative website]
*[https://github.com/opencontainers/ Open Container Initiative] on [[GitHub]]

[[Category:Standards organizations]]
[[Category:Linux Containerization]]
[[Category:Linux Foundation projects]]

{{Linux-stub}}

Open Container Initiative

2017-03-16T11:40:53Z

Intgr: Expand article

Open Container Initiative

2017-03-16T11:09:48Z

Intgr: Restore stub article, this redirect is simply misleading. OCI isn't a part of CoreOS or Container Linux, it's just one OCI member and consumer of OCI standards

The '''Open Container Initiative''' is an open standards project associated with the [[Linux Foundation]].<ref>http://www.informationweek.com/open-container-initiative-finds-footing-in-linux-foundation/d/d-id/1323439</ref>

==References==
{{Reflist}}

==External links==
*[https://www.opencontainers.org/ Open Container Initiative website]
*[https://github.com/opencontainers/ Open Container Initiative] on [[GitHub]]

{{Linux-stub}}

Dezentralisierte Autonome Organisation

2016-04-07T15:09:47Z

Intgr: Add space after punctuation

{{refimprove|date=February 2015}}
A '''decentralized autonomous organization''' or '''distributed autonomous organization''' (DAO) can be thought of as a self-governing organization under the control of an incorruptible set of business rules. These rules are typically implemented as publicly auditable open-source software distributed across the computers of their stakeholders. A human becomes a stakeholder by buying digital tokens, similar to shares in a company, or by being paid in those tokens to provide services for the company. These tokens may entitle its owner to a share of the profits of the DAO, participation in its growth, and/or a say in how it is run.<ref name=david-johnston1>[https://github.com/DavidJohnstonCEO/DecentralizedApplications#the-emerging-wave-of-decentralized-applications "The Emerging Wave of Decentralized Applications"]. GitHub. Retrieved 2 July 2014.</ref>
<ref>[https://blog.slock.it/a-primer-to-the-decentralized-autonomous-organization-dao-69fb125bd3cd#.689omrijv "A primer to the Decentralized Autonomous Organization (DAO)"]. Slock.it blog. Retrieved 26 March 2016.</ref>

If the organization take a [[corporation|corporate]] or [[company]] form, that of a business, then a DAO may be referred to as a '''fully automated business entity''' (FAB), or '''distributed autonomous corporation/company''' (DAC).

== Terminology ==

=== Autonomous agents ===

In an autonomous agent, there is no necessary specific human involvement outside of some degree of the human effort necessary to build the hardware that the agent runs on. Outside of that, there is no need for any humans to exist that are aware of the agent’s existence. One example of an autonomous agent that already exists today would be a computer virus; the virus survives by replicating itself from machine to machine without deliberate human action.<ref name=vitalik-buterin3>{{cite web|author1=Vitalik Buterin|url=https://blog.ethereum.org/2014/05/06/daos-dacs-das-and-more-an-incomplete-terminology-guide/|website=etherum blog|accessdate=13 August 2014|date=May 6, 2014|title=DAOs, DACs, DAs and More: An Incomplete Terminology Guide}}</ref>

=== Decentralized applications (Dapps) ===

A [[smart contract]] is the simplest form of decentralized automation. It is a mechanism involving [[digital assets]] and two or more parties, where some or all of the parties put assets in and assets are automatically redistributed among those parties according to a formula based on certain data that is not known at the time the contract is initiated. The formula is instantiated in a series of voluntary [[contract]]s that set terms that are known at the time the contract is executed.

A decentralized application is similar to a smart contract, but different in two key ways. First of all, a decentralized application has an unbounded number of participants on all sides of the market. Second, a decentralized application need not be necessarily financial. [[BitTorrent]] qualifies as a decentralized application, as do [[Popcorn Time]], [[Tor (anonymity network)|Tor]], [[Maidsafe]] and [[Crypti]] (note that Maidsafe and Crypti are also platforms for other decentralized applications).<ref name=vitalik-buterin3 />

=== Distributed organizations (DOs) ===

A human organization can be defined as a combination of two things: a set of [[property]], and a [[Communications protocol|protocol]] for a [[Set (abstract data type)|set]] of individuals (which may or may not be divided into certain classes with different conditions for entering or leaving the set) to interact with each other, including rules for under what circumstances the individuals may use certain parts of the property.

The idea of a distributed organization takes the same concept of an organization, and decentralizes it. Instead of a hierarchical structure managed by a set of humans interacting in person and controlling property via the [[legal system]], a distributed organization involves a set of humans interacting with each other according to a protocol specified in code, and enforced on the [[Block chain (database)|blockchain]].<ref name=vitalik-buterin3 /> The earliest prototype software to link up such a protocol to a blockchain was the Eris 0.1 prototype in June 2014.<ref>{{Cite web|title = Eris - The Dawn of Distributed Autonomous Organizations and The Future of Governance - h+ Media|url = http://hplusmagazine.com/2014/06/17/eris-the-dawn-of-distributed-autonomous-organizations-and-the-future-of-governance/|website = h+ Media|accessdate = 2015-11-02}}</ref>

=== Decentralized autonomous organizations (DAOs) ===

[[File:Quadrant Chart for Classifying DAOs.png|thumb|400px|Vitalik Buterin's Quadrant Chart for Classifying DAOs]]
The main difference between a DO and a DAO is that a DAO has internal capital;{{inconsistent}} that is, a DAO contains some kind of internal property that is valuable in some way, and it has the ability to use that property as a mechanism for incentivizing certain activities. [[BitTorrent]] has no internal property, and [[Maidsafe]]-like systems have reputation but that reputation is not a saleable asset. [[Bitcoin]] and [[Namecoin]], on the other hand, do, and the DAO that Slock.it has been designing has the advantage of holding internal capital outright as opposed to most digital currency type DAOs that create internal capital by debasing their own currency. However, plain old DOs also have internal capital.{{cn|date=April 2016}}

DOs and DAOs are both vulnerable to collusion attacks, where a significant percentage of a certain type of members collude to specifically direct its activity. However, in a DO collusion attacks are treated as a bug, whereas in a DAO they are a feature (such as [[majority vote]] in a [[democracy]]).{{Citation needed|date=February 2016}}

An AI is completely autonomous, whereas a DAO still requires heavy involvement from humans specifically interacting according to a protocol defined by the DAO in order to operate.<ref name=vitalik-buterin3 />

==== Decentralized autonomous corporations/companies ====

Organizations more generally may take the form of a [[corporation]] or [[company]]. In this case, the specific type of DAO is a DAC.

DACs are basically a subclass of DAOs that pays [[dividend]]s on purchasable and tradeable [[Share (finance)|shares]] which potentially entitle their holders to continual receipts based on the DAC’s success, to the point where the profit mechanism and the consensus mechanism are not the same thing.<ref name=vitalik-buterin3 /> According to Stan Larimer, President of Invictus Innovations, Inc. (a developer of DACs), an open source DAC with its state information kept public has these characteristics:<ref name=stan-larimer1>Larimer, Stan. [http://letstalkbitcoin.com/bitcoin-and-the-three-laws-of-robotics/#.UpKv78Ssi-2 "Bitcoin and the Three Laws of Robotics"]. ''Let's Talk Bitcoin''. Retrieved 2 July 2014.</ref>
* They are '''corporations''' – they are free and independent persons (but don’t have [[legal personality]]).
* They are '''autonomous''' – once up to speed, they no longer need (or heed) their creators.
* They are '''distributed''' – there are no central points of control or failure that can be attacked.
* They are '''transparent''' – their books and business rules are auditable by all.
* They are '''confidential''' – customer information is securely (and incorruptibly) protected.
* They are '''trustworthy''' – because no interaction with them depends on trust.
* They are '''fiduciaries''' – acting solely in their customers’ and shareholders’ interests.
* They are '''self-regulating''' – they robotically obey their own rules.
* They are '''incorruptible''' – no one can exercise seductive or coercive influence over them.
* They are '''sovereign''' – over their digital resources (but don't have [[Capacity (law)|legal capacity]]).

An example of a currently running DAC is the [[Nu Network]] (based on the open source [[Peershares]] template), which manages the world's first stable digital currency [[NuBits]].{{citation needed|date=November 2015}}

===== Criticism of terminology =====
Some of those interested in new models for building successful and massively scalable applications reject the term, arguing that the classification reintroduces legacy hierarchy-based structures with their regulatory and compliance issues, unnecessarily burdening those involved in their development. For example, in their white paper ''The Emerging Wave of Decentralized Applications'', David Johnston, et al., argue that while the term "Distributed Autonomous Organization" is not problematic, the term "Distributed Autonomous Corporation" shouldn't be used:<ref name=david-johnston1 />

<blockquote class="templatequote">
It is worthwhile to note that the authors of this paper agree with many of the concepts proposed by the Invictus authors and the spirit and ethics they [uphold] we embrace wholeheartedly. The point on which we disagree is one of property terminology, “Distributed” and “Autonomous” are great terms, we don’t believe “Corporation” in particular is a desirable term for these entities. One of our primary reservations with using the term is, “Corporation” carries a lot of historical and legal baggage that won’t necessarily best serve the community of developers and entrepreneurs seeking to describe and build these new projects. If you Google the definition of “Corporation” the result is: “a company or group of people authorized to act as a single entity (legally a person) and recognized as such in law.”
</blockquote>

== Economic theory ==

In economic theory, the role of the [[Business|firm]]{{lopsided|date=April 2016}} is played by the DAO, and the role of the [[Entrepreneurial economics|entrepreneur]] is played by the programmers who develop the DAO.

=== Firm ===

In its typical implementation as publicly auditable rules distributed across the computers of the stakeholders, the DAO can be thought of in a [[Neoclassical economics|neoclassical]] sense as a [[production function]] or [[Production–possibility frontier|production possibilities set]], a black box that transforms inputs into outputs. The DAO can be modeled as a single actor, facing a series of mathematical calculations, implicit in the non-self-verifying data, determined by the characteristics of the production function. The reason that the DAO can exist is because market coordination without it fails due to lack of necessary intersubjective points of orientation, that is, lack of so-called [[Focal point (game theory)|Schelling points]]. The emergence of behavior-coordinating Schelling points is a characteristic of the way that the DAO is coded.<ref name=h-malmgren1>Malmgren, H. B. (1961). "Information, Expectations and the Theory of the Firm". ''Quarterly Journal of Economics'' '''75''': 399-421.</ref>

=== Entrepreneur ===

The entrepreneurship of the DAO's development process can be thought of in a [[Joseph Schumpeter|Schumpeterian]] sense as an exceptional occurrence of massive importance. The programmers who develop and launch the DAO are persons who by introducing "new combinations" shake the economy out of its previous equilibrium, starting a process Schumpeter termed [[creative destruction]].<ref name=marcus-becker1>Becker, Marcus C.; Thorbjørn Knudsen (2003). "The Entrepreneur at a Crucial Juncture in Schumpeter’s Work: Schumpeter’s 1928 Handbook Entry Entrepreneur". ''Advances in Austrian Economics'' '''6''': 199–234.</ref> This speaks to the tenuous relationship between the developers and the DAO they own or contract with, because Schumpeterian entrepreneurship is ''[[sui generis]]'' (independent of its environment).<ref name=nicolai-foss1>Foss NJ, Klein PG. ''Organizing Entrepreneurial Judgment: A New Approach to the Firm''. Cambridge University Press. (2012). ISBN 9780521874427</ref><ref>Foss NJ, Klein PG. Authors Forum:''Organizing Entrepreneurial Judgment: A New Approach to the Firm''. 2012 Austrian Scholars Conference, recorded 8 March 2012 at the Ludwig von Mises Institute in Auburn, Alabama. [https://www.youtube.com/watch?v=a0rJtEBjTA4]</ref>

== Legal issues ==

{{Asof|2014}}, DAOs had no way to indemnify users since they lack [[legal personality]] and may have either no cash-flow or no assets. Accordingly, recovery in the event that a given DAO fails could turn out to be extremely difficult in practice. Consequently, for example, if a DAO had funds, they would typically be able to indemnify specific users (namely exchanges) through corporate insurance (a [[Bond (finance)|bond]]).<ref name=swanson1>{{cite web|last1=Swanson|first1=Tim|title=Mitigating the Legal Risks of Issuing Securities on a Cryptoledger|url=http://cointelegraph.com/news/112034/mitigating-the-legal-risks-of-issuing-securities-on-a-cryptoledger|website=Cointelegraph|publisher=Cointelegraph|accessdate=11 July 2014}}</ref>
According to Austin Brister, a Houston-based attorney:
<blockquote class="templatequote">Consumer protection laws can be far-reaching and quite unforgiving. Ordinary businesses do just fine in navigating these laws, even if they don't realize it, because they can adjust their interactions with consumers in "real-time" in order to be reasonable, well-centered, and act in good faith in dealing with consumers. However, the problem with smart contracts, decentralized autonomous organizations, and the like, is that they are hard-wired to act in one way, whether it makes sense or not.

Unforeseeable circumstances practically always present themselves to businesses of all types, and by definition, these circumstances cannot be foreseen or planned for. These systems need to adequately plan for this possibility, and be prepared to be properly insured or adequately bonded in the event things go wrong, and customers are hurt. Similarly, consumers should be aware that they are not dealing with living breathing people, but rather a machine subject only to 0's and 1's.<ref name="swanson1"/>
</blockquote>

== Key architectural principles ==

* '''The [[Black swan theory|Black Swan]] principle''': Because of the impossibility of calculating the risks of consequential rare events and predicting their occurrence, an implementation must be based on ''nonpredictive'' decision-making under uncertainty, with more upside than downside from random events.
* '''The Chessmaster principle''': In general, an implementation must treat people like pawns in a [[chess]] game, patiently moving them into places that often seem harmless or pointless, and getting them to do all the heavy computational lifting. The best implementations will have layers of misdirection and backup plans in case some [[Hacker (computer security)|hacker]] attempts to defraud them, for instance, causing the attacker to do some work for them in the attempt.{{cn|date=April 2016}}
* '''[[Finagle's Law]]''': In general, an implementation of a DAO must assume that if there are two or more ways to do something, and one of those ways can result in a catastrophe for the DAO, then someone will choose it. The best implementations rely on low trust protocols and [[behavior-shaping constraint]]s to protect themselves. (Being merely narrow AI, they cannot make nuanced trust judgments and are potentially easy to scam.{{cn|date=April 2016}})

== A DAO protocol suite ==

[[File:Layers in the DAC protocol suite.svg|thumb|This is a diagram of the layers in the protocol suite for a Decentralized Autonomous Organization (DAO).]]

=== Economic layer ===

An economic layer may be composed of Type I and Type II{{what|date=April 2016}} decentralized applications, the payment systems being based on the cryptographic money systems with their existing blockchains, having independent protocols and tokens of their own.<ref name=david-johnston1 />

=== Self-modification layer ===

This layer handles allowing humans to modify the DAO so as to future-proof it, e.g. changing APIs and source code. This layer allows DACs to improve themselves by purchasing the services of humans via bilateral hostage contracts, for instance.<ref name=oleg-andreev1>Andreev, Oleg. [http://blog.oleganza.com/post/58240549599/contracts-without-trust-or-third-parties "Contracts without trust or third parties"]. ''Personal Blog''. Retrieved 2 July 2014.</ref> This layer also allows the DAO to set an upper bound on the losses caused by any malicious collusion.<ref>DeFigueiredo, Dimitri do B. [http://dimitrietal.com/trustdavis.pdf "TrustDavis: A Non-Exploitable Online Reputation System"]. Department of Computer Science, University of California at Davis. Retrieved 2 July 2014.</ref> [[A/B testing]] can be used to determine if the delivered work is really better than the old one or not, and only releasing the payment if the results of the test are positive. Alternatively, a quorum of [[Dispute resolution organization|dispute mediators]] can be specified, and they decide if the contract was met or not. This layer depends on the Economic layer and the Memory layer.{{cn|date=April 2016}}

=== Output layer ===

This layer interacts with the world using multiparty-signed API requests in a decentralized way. This may include APIs that allow for renting server capacity and then remotely controlling that server, for example, or the ability to post human-readable contracts to [[freelancer]] forums or the [[Amazon Mechanical Turk|Mechanical Turk]]. DACs can expose their services to humans (or other DACs) by selecting a name and then registering it with [[Namecoin]]. Using DNS hierarchies and Namecoin together allows interested parties to monitor for new agents coming online: the act of registering a name under a particular part of the tree automatically advertises its existence. This layer depends on the Economic layer, the Memory layer, and the Data Gathering layer.{{cn|date=April 2016}}

This layer is composed of Type III Decentralized Applications, having their own independent protocols and tokens.<ref name=david-johnston1 />

== Hiring employees ==

Making a fine-grained evaluation of an individual human employee is likely impossible. The best solution is likely to simply use monetary incentives to direct people’s actions on a coarse level, and then let the community self-organize to make the fine-grained adjustments. The extent to which a DAO targets a community for investment and participation, rather than discrete individuals, is the choice of its original developers.<ref>{{cite AV media
| year=2014
| title=Engineering Economic Security
| medium=YouTube
| url=https://www.youtube.com/watch?v=4CFlA8TdWmk&feature=youtu.be
| accessdate=August 11, 2014
| location=Silicon Valley Ethereum Meetup
| publisher=EtherCasts
}}</ref> On the one hand, targeting a community can allow your human support to work together to solve problems in large groups. On the other hand, keeping everyone separate prevents collusion, and in that way reduces the likelihood of a hostile takeover.<ref name=vitalik-buterin1>Buterin, Vitalik. [http://bitcoinmagazine.com/7119/bootstrapping-an-autonomous-decentralized-corporation-part-2-interacting-with-the-world/ "Bootstrapping An Autonomous Decentralized Corporation, Part 2: Interacting With the World"]. ''Bitcoin Magazine™''. Coin Publishing Ltd. Retrieved 22 November 2013.</ref>

== Hostile takeovers ==

A hostile takeover of a DAO handling money means that the attacker gains the ability to drain the DAO’s entire wallet. Countering hostile takeovers requires certain economic measures to establish consensus:
* '''[[Proof of work]]''' is used to deter denial of service attacks by requiring some work from the service requester that is moderately hard (but feasible) on the requester side but easy to check for the service provider. This is commonly referred to as "mining".<ref name=david-johnston1 />
* '''Proof of stake''' or '''Collateralized Secure Voting'''<ref>{{Cite web|url=https://dashtalk.org/threads/self-sustainable-decentralized-governance-by-blockchain.4708/|title=Self-sustainable Decentralized Governance by Blockchain {{!}} DashTalk|website=dashtalk.org|access-date=2016-03-27}}</ref> is used to deter other service abuses such as a [[Sybil attack]].

Another counter-measure might simply be to allow the decentralized corporation to have shareholders, so that shareholders get some kind of special voting privileges, along with the right to a share of the profits, in exchange for investing. (Shareholders benefit if the price goes up, so shareholders are encouraged to do things that increase the price.) This would incentivize the shareholders to protect their investment.

=== Sybil attacks ===
{{see also | Sybil attack}}
A hostile takeover could be accomplished by a successful Sybil attack, say through a [[botnet]], overwhelming the resource-democracy mechanism by controlling over half of the servers in the network.

Requiring each participating node to show proof that it controls some moderately large amount of cryptocurrency would prevent this kind of attack. Then implementing a hostile takeover would require more resources than all of the legitimate nodes committed together. The moderately large amount of crypto-currency could even be moved to a multisignature address partially controlled by the network as a [[surety bond]], both discouraging nodes from cheating and giving their owners a great incentive to act and even get together to keep the corporation alive.

== Examples ==

=== Applications ===

There are three major categories of industries where DACs will be able to survive on their own merits and provide genuine value to society: ''natural monopolies'', ''illegal entities'', and ''entities of extremely low profitability''.

{{example farm|section|date=July 2014}}

==== Natural monopolies ====

A [[natural monopoly]] is a monopoly in an industry in which it is most efficient (involving the lowest long-run average cost) for production to be concentrated in a single firm: [[Communications protocol|software protocols]], [[Programming language|languages]] and to some extent [[Social networking service|social networks]] and [[currencies]]. A DAO can theoretically be designed so that no one involved in the price-setting mechanism has an incentive to fix prices over market rates. More generally, they can be made invulnerable to corruption in ways unimaginable in human-controlled system, although great care would certainly need to be taken not to introduce other vulnerabilities instead.<ref name=vitalik-buterin1 />
* Identity Corp, a corporation whose sole purpose is to create cryptographically secure identity documents for individuals that they could sign messages with, and are linked to individuals’ physical identities.<ref name=vitalik-buterin2>Buterin, Vitalik. [http://bitcoinmagazine.com/7235/bootstrapping-a-decentralized-autonomous-corporation-part-3-identity-corp/ "Bootstrapping a Decentralized Autonomous Corporation, Part 3: Identity Corp"]. ''Bitcoin Magazine™''. Coin Publishing Ltd. Retrieved 23 November 2013.</ref>

==== Illegal entities ====

Because of a combination of the DAO's incorruptible nature and the explosive growth in [[Rulemaking|regulations]], services that violate government laws and regulations are unavoidable. But their decentralized nature makes it extremely difficult to prevent them from taking over illegal markets. As Satoshi Nakamoto said, "Governments are good at cutting off the heads of a centrally controlled networks like Napster, but pure P2P networks like Gnutella and Tor seem to be holding their own".<ref>[http://motherboard.vice.com/blog/quotes-from-satoshi-understanding-bitcoin-through-the-lens-of-its-enigmatic-creator "What Satoshi Said: Understanding Bitcoin Through the Lens of Its Enigmatic Creator"].</ref>
* Decentralized file-sharing networks for copyright infringement
* A captcha-cracker, that requires CPU. People pay for the Captchas to be cracked and the DAO provides some kind of API for people to offer their CPU and hosting of the software, if they do so, they get bitcoins. Putting this up online, with some marketing, the software should survive on its own as long as there are captchas that needs to be cracked.

==== Digital currency based entities ====

Finally, there are those cases where a decentralized digital currency can simply maintain itself more efficiently and outcompete the centralized alternatives. Digital currency projects are the most common examples of DAOs.
* The DAO - A soon to be deployed Ethereum smart contract that will contract with a Service Provider with the stated objective to Decentralize the Sharing Economy <ref>Jentzsch, Christoph [https://download.slock.it/public/DAO/WhitePaper.pdf "DECENTRALIZED AUTONOMOUS ORGANIZATION TO MANAGE A TRUST"]. Retrieved 26 March 2016.</ref>
* BitShares - a DAC industry with the purpose of providing infrastructure and software for other DACs. Currently available DACs within BitShares ecosystem:
** BitSharesX - a family of DACs that implement the business model of a bank and exchange.
* Colored Coins are working on defining themselves as a DAO
* DASH's Decentralized Governance by the Blockchain (DGBB)
* Mitosys - a DAC replacement for Bit-Message
* Social network - Monetizable Diaspora
* StorJ, a simple drop-box style file service with pay per use via bitcoin (and perhaps with naming provided via namecoin and/or tor hidden services).<ref name=jeff-garzik1>Garzik, Jeff. [http://garzikrants.blogspot.ch/2013/01/storj-and-bitcoin-autonomous-agents.html "StorJ, and Bitcoin autonomous agents"]. ''Random blatherings by Jeff''. Blogger. Retrieved 22 November 2013.</ref> StorJ isn't smart enough to judge bad proposals on its own — instead it forms agreements that make it unprofitable to cheat.
* [[Bitcoin protocol|Bitcoin]] itself and all Bitcoin forks that have been properly decentralized
* [http://garzikrants.blogspot.com/2014/01/blackbox-bitcoin-enabled-decentralized.html blackbox] is a Bitcoin-enabled, decentralized cloud that uses TradeNet
* [https://github.com/wetube/wetube-web Wetube]

=== Examples in literature ===

* In Daniel Suarez's [[techno-thriller]], ''[[Daemon (book series)|Daemon]]'', a collection of sophisticated computer programs have been left sitting passively on machines scattered around the Internet until one of them reads the programmer's obituary, which sends triggers to other systems which activate a number of other distributed processes, awakening the DAO.

== See also ==

* [[Bitcoin protocol]]
* [[Ethereum]]
* [[Decentralized computing]]
* [[Incentive-centered design]]
* [[Merkle tree]]
* [[Monero (cryptocurrency)|Monero]]
* [[Serious game]]

== References ==
{{Reflist|2}}

== External links ==
{{External links|section|date=December 2015}}
{{refbegin|2}}
* [http://aeon.co/magazine/technology/are-we-ready-for-companies-that-run-themselves/ RoboCorp - Get ready for companies that run themselves. But will the autonomous economy set us all free, or just make the rich richer?], David Z. Morris, ''[[Aeon (digital magazine)]]''
* [http://www.npr.org/blogs/parallels/2015/02/01/382648685/in-sweden-remote-control-airport-is-a-reality In Sweden, Remote-Control Airport Is A Reality], Ari Shapiro, ''[[National Public Radio (United States)|National Public Radio]]''
* [http://bitcoin.org/bitcoin.pdf Bitcoin: A Peer-to-Peer Electronic Cash System] bitcoin.org
* [http://bitcoinmagazine.com/7050/bootstrapping-a-decentralized-autonomous-corporation-part-i/ Bootstrapping a DAC Part 1] Bitcoin Magazine
* [http://bitsharestalk.org/index.php?topic=297.0 Topic on bitsharestalk] bitsharestalk.org
* [http://ethereum.org/ethereum.html Ethereum]: A Next-Generation Generalized Smart Contract and Decentralized Application Platform
* [http://wiki.ethereum.org/index.php/Dagger Dagger] is a proof of work algorithm, intended to provide a memory-hard proof of work based on moderately connected directed acyclic graphs. wiki.ethereum.org
* [http://wiki.ethereum.org/index.php/Patricia_Tree Patricia Tree] wiki.ethereum.org
* [https://blog.ethereum.org/2014/05/06/daos-dacs-das-and-more-an-incomplete-terminology-guide/ DAOs, DACs, DAs and More: An Incomplete Terminology Guide] blog.ethereum.org
* [http://garzikrants.blogspot.ca/2013/01/storj-and-bitcoin-autonomous-agents.html StorJ, and Bitcoin autonomous agents] garzikrants.blogspot
* [http://letstalkbitcoin.com/bitcoin-and-the-three-laws-of-robotics/ Bitcoin and the Three Laws of Robotics] letstalkbitcoin.com
* [http://letstalkbitcoin.com/dac-revisited/ DAC Revisited] letstalkbitcoin.com
* [http://letstalkbitcoin.com/dacs-that-spawn-dacs/ DACs That Spawn DACs?] letstalkbitcoin.com
* [http://letstalkbitcoin.com/is-bitcoin-overpaying-for-false-security/ The Hidden Costs of Bitcoin] letstalkbitcoin.com
* [http://tvtropes.org/pmwiki/pmwiki.php/Literature/Daemon TV Tropes Analysis of Daemon] tvtropes.org
* [http://wavism.net/group3/distributed-autonomous-virtual-state-davs/ Distributed Autonomous Virtual State] wavism.net
* [http://www.amazon.com/Great-Chain-Numbers-Contracts-Management-ebook/dp/B00IRUBMXO Great Chain of Numbers: A Guide to Smart Contracts, Smart Property and Trustless Asset Management] amazon.com
* [http://www.cs.huji.ac.il/~avivz/pubs/13/btc_scalability_full.pdf Accelerating Bitcoin's Transaction Processing] Fast Money Grows on Trees, Not Chains, cs.huji.ac.il
* [http://www.youtube.com/watch?v=Pu4PAMFPo5Y Mike Hearn's talk on autonomous agents, Turing Festival 2013] YouTube
* [https://docs.google.com/document/d/1AnkP_cVZTCMLIzw4DvsW6M8Q2JC0lIzrTLuoWu2z1BE/edit#heading=h.v3px1rgmf10o Colored Coins]
* [https://en.bitcoin.it/wiki/Agents Bitcoin-using autonomous agents] Bitcoin wiki
* [https://en.bitcoin.it/wiki/Contracts Contracts] Bitcoin wiki
* [https://en.bitcoin.it/wiki/List_of_Decentralized_Autonomous_Corporations List of Decentralized Autonomous Corporations] Bitcoin wiki
* [https://en.bitcoin.it/wiki/Scalability#Simplified_payment_verification Simplified payment verification] Bitcoin wiki
* [https://en.bitcoin.it/wiki/Smart_Property Smart Property] Bitcoin wiki
* [https://en.wikibooks.org/wiki/Seed_Factories/WWF Distributed Production Network] wikibooks.org
* [https://github.com/mastercoin-MSC/spec The Master Protocol - Mastercoin Complete Specification] github.com
{{refend}}

{{DEFAULTSORT:Distributed Computing}}
[[Category:Anarcho-capitalism]]
[[Category:Application layer protocols]]
[[Category:Applications of cryptography]]
[[Category:Computer law]]
[[Category:Computer networking]]
[[Category:Crypto-anarchism]]
[[Category:Cryptography]]
[[Category:Distributed computing]]
[[Category:Distributed data storage]]
[[Category:E-commerce]]
[[Category:Network protocols]]
[[Category:Payment systems]]
[[Category:Peer-to-peer computing]]
[[Category:Production economics]]
[[Category:Cryptocurrencies]]

FAST TCP

2016-02-10T16:14:03Z

Intgr: removed Category:Transmission Control Protocol; added Category:TCP congestion control using HotCat

'''FAST TCP''' (also written '''FastTCP''') is a [[TCP congestion avoidance algorithm]] especially targeted at long-distance, high latency links, developed at the Netlab, [[California Institute of Technology]] and now being commercialized by FastSoft. FastSoft was acquired by [[Akamai Technologies]] in 2012.<ref>{{cite web
| last = Young
| first = Jeff
| title = Akamai Acquires FastSoft
| agency = PR Newswire
| date = 2012-09-13
| url = http://www.prnewswire.com/news-releases/akamai-acquires-fastsoft-169678966.html
| accessdate = 2012-09-13 }}</ref>

FastTCP is compatible with existing TCP algorithms, requiring modification only to the [[computer]] which is sending [[data]].

==Name==
The name '''FAST''' is a [[recursive acronym]] for '''F'''AST '''A'''QM '''S'''calable '''T'''CP, where '''AQM''' stands for '''A'''ctive '''Q'''ueue '''M'''anagement, and '''TCP''' stands for '''T'''ransmission '''C'''ontrol '''P'''rotocol.

==Principles of operation==
The role of congestion control is to moderate the rate at which data is transmitted, according to the capacity of the [[telecommunications network|network]] and the rate at which other users are transmitting. Like [[TCP Vegas]], FAST TCP<ref>{{cite journal
| last = Nick
| first = Barone
| author2 = Jin, Cheng; Low, Steven H. and Hegde, Sanjay
| year = 2006
| title = FAST TCP: motivation, architecture, algorithms, performance
| journal = IEEE/ACM Trans. on Networking
| volume = 14
| issue = 6
| pages = 1246–1259
| url = http://netlab.caltech.edu/pub/papers/FAST-ToN-final-060209.pdf
| doi = 10.1109/TNET.2006.886335
}}</ref><ref>{{cite journal
| last = Jin
| first = Cheng
| year = 2005
| title = FAST TCP: from theory to experiments
| journal = IEEE Network
| volume = 19
| issue = 1
| pages = 4–11
| url = http://netlab.caltech.edu/pub/papers/fast-network05.pdf
| doi = 10.1109/MNET.2005.1383434
| last2 = Wei
| first2 = D.
| last3 = Low
| first3 = S.H.
| last4 = Bunn
| first4 = J.
| last5 = Choe
| first5 = H.D.
| last6 = Doyle
| first6 = J.C.
| last7 = Newman
| first7 = H.
| last8 = Ravot
| first8 = S.
| last9 = Singh
| first9 = S.
| last10 = Paganini
| first10 = F.
| last11 = Buhrmaster
| first11 = G.
| last12 = Cottrell
| first12 = L.
| last13 = Martin
| first13 = O.
| last14 = Wu-Chun Feng
}}</ref> uses [[queueing delay]] instead of [[packet loss|loss probability]] as a congestion signal.

Most current congestion control algorithms detect congestion and slow down when they discover that packets are being dropped, so that the average sending rate depends on the loss probability. This has two drawbacks. First, low loss probabilities are required to sustain high data rates; in the case of TCP Reno, very low loss probabilities are required, but even new congestion avoidance algorithms such as [[H-TCP]], [[BIC TCP]] and [[HSTCP]] require loss rates lower than those provided by most wireless [[wide area network]]s. Moreover, packet loss only provides a single bit of information about the congestion level, whereas delay is a continuous quantity and in principle provides more information about the network.

A FAST TCP flow seeks to maintain a constant number of packets in queues throughout the network. The number of packets in queues is estimated by measuring the difference between the observed [[round-trip delay time|round trip time]] (RTT) and the ''base RTT'', defined as the round trip time when there is no queueing. The base RTT is estimated as the minimum observed RTT for the connection. If too few packets are queued, the sending rate is increased, while if too many are queued, the rate is decreased. In this respect, it is a direct descendant of TCP Vegas.

The difference between TCP Vegas and FAST TCP lies in the way in which the rate is adjusted when the number of packets stored is too small or large. TCP Vegas makes fixed size adjustments to the rate, independent of how far the current rate is from the target rate. FAST TCP makes larger steps when the system is further from equilibrium and smaller steps near equilibrium. This improves the speed of convergence and the stability.

==Strengths and weaknesses==
Delay-based algorithms can, in principle, maintain a constant window size, avoiding the oscillations inherent in loss-based algorithms. However, they also detect congestion earlier than loss-based algorithms, since delay corresponds to partially filled [[Buffer (telecommunication)|buffers]], while loss results from totally filled buffers. This can be either a strength or a weakness. If the only protocol used in a network is delay-based, then the inefficiency of loss can be avoided; however, if loss-based and delay-based protocols share the network,<ref>{{cite web
| last = Tang
| first = Ao
| author2 = Wang, Jiantao; Low, Steven H. and Chiang, Mung
|date= March 2005
| title = Network Equilibrium of heterogeneous congestion control protocols
| work = IEEE INFOCOM
| location = Miami, FL
| url = http://www.sisl.caltech.edu/pubs/controlprotocol.pdf
}}
</ref> then delay-based algorithms tend to be less aggressive. This can be overcome by suitable choice of parameters, leading to complex interactions studied by Tang et al.

Delay measurements are also subject to jitter as a result of [[operating system]] scheduling, or [[Computer bus|bus]] contention.

Whether the strengths or weaknesses prevail is not clear, and depends in large part on the particular scenario.

==Intellectual property==
Unlike most TCP congestion avoidance algorithms, FAST TCP is protected by several patents.<ref>{{cite web
| last = Jin
| first = Cheng
| author2 = Low, Steven H.; Wei, Xiaoliang
| title = Method and apparatus for network congestion control
| publisher = [[United States Patent & Trademark Office]]
| date = 2005-01-27
| url = http://appft1.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&p=1&u=%2Fnetahtml%2FPTO%2Fsearch-bool.html&r=2&f=G&l=50&co1=AND&d=PG01&s1=jin.IN.&s2=low.IN.&OS=IN/jin+AND+IN/low&RS=IN/jin+AND+IN/low
| accessdate = 2006-11-05 }}</ref><ref>{{cite web
| last = Jin
| first = Cheng
|author2=Low, Steven H. |author3=Wei, David X. |author4=Wydrowski, Bartek |author5=Tang, Ao |author6= Choe, Hyojeong
| title = Method and apparatus for network congestion control using queue control and one-way delay measurements
| publisher = [[United States Patent & Trademark Office]]
| date = 2006-03-09
| url = http://appft1.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&p=1&u=%2Fnetahtml%2FPTO%2Fsearch-bool.html&r=1&f=G&l=50&co1=AND&d=PG01&s1=jin.IN.&s2=low.IN.&OS=IN/jin+AND+IN/low&RS=IN/jin+AND+IN/low
| accessdate = 2006-11-05 }}</ref> Instead of seeking standardization by the [[IETF]], the inventors of FAST, notably [[Steven H. Low]] and Cheng Jin, are seeking to commercialize it through the company FastSoft. Currently FastSoft sells a 1-Unit rack appliance which can be deployed at the sender-side with no other software or hardware modifications needed on either end.

==See also==
* [[TCP congestion avoidance algorithm]]
* [[Transmission Control Protocol#Development]]

==References==
{{reflist}}

==External links==
*[http://netlab.caltech.edu/FAST/ FAST] Home Page.
*[http://ultralight.caltech.edu/web-site/sc05/html/index.html Supercomputing 2005 Bandwidth Challenge]
*[http://www.fastsoft.com FastSoft home page]

{{DEFAULTSORT:Fast Tcp}}
[[Category:Internet protocols]]
[[Category:Internet Standards]]
[[Category:TCP congestion control]]

Jim Keller

2016-02-10T13:26:34Z

Intgr: /* Career */ WP:OVERLINK SiByte redirects to Broadcom, which is already linked

{{Use dmy dates|date=November 2015}}
{{Infobox person
| name = Jim Keller
| image = 
| alt =
| caption =
| birth_name = 
| birth_date = 
| birth_place =
| death_date = 
| death_place =
| nationality =
| other_names =
| occupation = Vice President of Autopilot Hardware Engineering at [[Tesla Motors]]<ref name=electrek-tesla />
| years_active =
| known_for = {{Plainlist|
* AMD K7
* AMD K8 (lead architect)
* Apple A4, A5
* x86-64 (coauthor)
* HyperTransport (coauthor)
}}
| notable_works =
}}

'''Jim Keller''' is a [[microprocessor]] [[engineer]] most well known for his work at [[AMD]] and [[Apple Inc.|Apple]]. He was the lead architect of [[AMD K8]] microarchitecture<ref name=anandtech>{{cite news |url=http://www.anandtech.com/show/6129/apple-a4a5-designer-k8-lead-architect-jim-keller-returns-to-amd |title=Apple A4/A5 Designer & K8 Lead Architect, Jim Keller, Returns to AMD |author=[[Anand Lal Shimpi]] |date=1 August 2012 |work=[[AnandTech]] }}</ref><ref name=xbitlabs>{{cite news |url=http://www.xbitlabs.com/news/cpu/display/20120801190422_Return_of_the_King_AMD_K7_and_K8_Designer_Jim_Keller_Back_at_AMD.html |title=Return of the King: AMD K7 and K8 Designer Jim Keller Back at AMD |author=Anton Shilov |date=1 August 2012 |work=X-bit Labs }}</ref><ref name=computing>{{cite news |url=http://www.computing.co.uk/ctg/news/2344223/amd-to-design-new-micro-architecture-for-2015-launch-under-chip-guru-jim-keller |title=AMD to design new micro-architecture for 2015 launch under chip guru Jim Keller |author=Graeme Burton |date=12 May 2014 |work=computing.co.uk }}</ref> (including the original [[Athlon 64]])<ref name=anandtech /><ref name=thenextweb>{{cite news |url=http://thenextweb.com/insider/2012/08/01/apples-cpu-architect-jim-keller-departs-to-head-up-chipmaker-amds-processor-group/ |title=Apple's CPU Architect Jim Keller Jumps To AMD |author=Robin Wauters |date=1 August 2012 |work=[[The Next Web]] }}</ref><ref name=cultofmac>{{cite news |url=http://www.cultofmac.com/182296/amd-hires-ax-series-architect-jim-keller-away-from-apple-to-report-to-mark-papermaster/ |title=AMD Hires Ax Series Architect Jim Keller Away From Apple To Report To Mark Papermaster |author=John Brownlee |date=1 August 2012 |work=Cult of Mac}}</ref> and was involved in designing the [[Athlon]] (K7)<ref name=computing /> and [[Apple A4]]/[[Apple A5|A5]] processors.<ref name=anandtech /><ref name=venturebeat>{{cite news |url=http://venturebeat.com/2012/08/01/apple-cpu-jim-keller-amd/ |title=Apple CPU lead Jim Keller heads back to AMD as chief architect |author=Devindra Hardawar |date=1 August 2012 |work=[[VentureBeat]] }}</ref><ref name=theverge>{{cite news |url=http://www.theverge.com/2012/8/1/3212406/jim-keller-joins-amd-vp-chief-architect |title=Former Apple chip designer Jim Keller joins AMD as chief architect and VP |author=Adi Robertson |date=1 August 2012 |publisher=Vox Media |work=[[The Verge]] }}</ref><ref name=allthingsd>{{cite news |url=http://allthingsd.com/20120801/amd-hires-apples-head-chip-designer/ |title=AMD Hires Apple's Head Chip Designer |author=Arik Hesseldahl |date=1 August 2012 |work=[[AllThingsD]] }}</ref> He was also the coauthor of the specifications for the [[x86-64]] instruction set<ref name=venturebeat /><ref name=itworld>{{cite news |url=http://www.itworld.com/article/2693371/is-amd-finally-ready-to-give-intel-a-real-fight.html |title=AMD roadmap: Is AMD finally ready to give Intel a real fight? |author=Andy Patrizio |date=16 May 2014 |work=ITworld}}</ref> and [[HyperTransport]] interconnect.<ref name=anandtech/><ref name=itworld /><ref name=semiaccurate>{{cite news |url=http://semiaccurate.com/2012/08/01/apples-cpu-architect-jim-keller-moves-back-to-amd/ |title=Apple's CPU architect Jim Keller moves back to AMD |author=Charlie Demerjian |date=1 August 2012 |work=[[SemiAccurate]] }}</ref> From 2012 to 2015, he returned to AMD to work on the [[AMD K12]]<ref name=decryptedtech>{{cite news |url=http://www.decryptedtech.com/news/amd-brings-k7-k8-creator-jim-keller-back-into-the-fold |title=AMD Brings K7/K8 Creator, Jim Keller, Back Into the Fold |author=Sean Kalinich |date=27 June 2014 |work=decryptedtech.com }}</ref> and [[AMD Zen|Zen]] microarchitectures,<ref name=kitguru>{{cite news |url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/ |title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be |author=Anton Shilov |date=11 September 2014 |work=kitguru.net }}</ref><ref name=wccftech>{{cite news |url=http://wccftech.com/amd-confirms-development-of-high-performance-x86-core-with-completely-new-architecture/ |title=AMD Confirms Development of High-Performance x86 Core With Completely New Architecture |author=Hassan Mujtaba |date=5 May 2014 |work=WCCFtech }}</ref> particularly on the low-power/embedded versions.<ref name=cultofmac /><ref name=allthingsd />

== Career ==
Jim Keller was working at [[Digital Equipment Corporation|DEC]] until 1998, where he was involved in designing the [[Alpha 21164]] and [[Alpha 21264|21264]] processors.<ref name=anandtech /><ref name=xbitlabs /> In 1998 he moved to AMD, where he worked to launch the AMD [[Athlon]] (K7) processor and was the lead architect of the [[AMD K8]] microarchitecture,<ref name=9to5mac>{{cite news |url=http://9to5mac.com/2012/08/01/apple-cpu-guru-jim-keller-who-came-with-pa-semi-deal-departs-back-to-amd-to-lead-group-under-mark-papermaster/ |title=Apple CPU guru Jim Keller, who came with PA Semi deal, departs back to AMD to lead group under Mark Papermaster |author=Seth Weintraub |date=1 August 2012 |work=9to5Mac }}</ref> which also included designing the x86-64 instruction set and HyperTransport interconnect mainly used for [[multiprocessor]] communications.<ref name=anandtech />

In 1999, he left AMD to work at SiByte to design [[MIPS instruction set|MIPS]]-based processors for 1 Gbit/s network interfaces and other devices.<ref name=xbitlabs /><ref name=semiaccurate /><ref>{{cite web |url=http://www.techspot.com/news/49611-apple-chip-designer-jim-keller-heads-back-to-amd.html |title=Apple chip designer Jim Keller heads back to AMD |author=Jose Vilches |date=1 August 2012 |work=[[TechSpot]]}}</ref> In November 2000, SiByte was acquired by [[Broadcom]],<ref>{{cite news |url=http://www.wsj.com/articles/SB973519053768422247 |title=Broadcom Agrees to Acquire SiByte for $2 Billion in Stock |author=Molly Williams |date=7 November 2000 |work=[[Wall Street Journal]]}}</ref> where he continued as chief architect<ref name=theverge /> until 2004.<ref name=anandtech />

In 2004 he moved to serve as the Vice President of Engineering at [[P.A. Semi]],<ref name=anandtech /><ref name=itworld /> a company specializing in low-power mobile processors.<ref name=xbitlabs /> P.A. Semi was acquired by Apple in 2008, and Keller followed,<ref name=thenextweb /><ref name=9to5mac /> becoming part of a team to design the Apple A4 and A5 [[system-on-a-chip]] mobile processors. These processors were used in several Apple products, including [[iPhone 4]], [[iPhone 4S|4S]], [[iPad]] and [[iPad 2]].

In August 2012, Jim Keller returned to AMD, where his primary task was to design a new generation [[microarchitecture]]<ref name=computing /><ref name=itworld /><ref name=wccftech /> called [[Zen (microarchitecture)|Zen]].<ref name=kitguru /> After years of being unable to compete with [[Intel]] in the high-end [[CPU]] market, the new generation of Zen processors is hoped to restore AMD's position in the high-end [[x86-64]] processor market.<ref name=anandtech /><ref name=decryptedtech /> On 18 September 2015, Keller departed from AMD to pursue other opportunities, ending his three-year employment at AMD.<ref>{{cite news |last1=Mann |first1=Parm |title=Legendary CPU architect Jim Keller leaves AMD |url=http://hexus.net/tech/news/cpu/86585-legendary-cpu-architect-jim-keller-leaves-amd/ |accessdate=18 September 2015}}</ref>

In January 2016, Keller joined [[Tesla Motors]] as Vice President of Autopilot Hardware Engineering.<ref name=electrek-tesla>{{cite news |url=http://electrek.co/2016/01/28/tesla-jim-keller-apple-processor-architect-2/ |author=Seth Weintraub |date=28 January 2016 |title=The chip guru who built Apple’s Ax microprocessors joins Tesla to lead the Autopilot Hardware Engineering team |work=Electrek }}</ref>

== References ==
{{Reflist|30em}}

{{DEFAULTSORT:Keller, Jim}}
[[Category:Living people]]
[[Category:Advanced Micro Devices people]]
[[Category:American engineers]]
[[Category:Computer hardware engineers]]
[[Category:Apple Inc. ex-employees]]

{{engineer-stub}}

Dezentralisierte Autonome Organisation

2016-02-09T09:30:21Z

Intgr: +Citation needed, in response to recent arbitrary-looking changes by IP editor

{{refimprove|date=February 2015}}
A '''decentralized autonomous organization''' (DAO), '''fully automated business entity''' (FAB), or '''distributed autonomous corporation/company''' (DAC) is a decentralized network of narrow-AI [[autonomous agent]]s which perform an output-maximizing production function and which divides its labor into computationally intractable tasks (which it incentivizes humans to do) and tasks which it performs itself.<ref name=dave-talk>Babbitt, Dave. "Crypto-Economic Design: A Proposed Agent-Based Modeling Effort." SwarmFest 2014: 18th Annual Meeting on Agent-Based Modeling & Simulation, University of Notre Dame, McKenna Hall Auditorium, Notre Dame, IN USA, June 29 - July 1, 2014. Ed. Greg Madey & Ryan McCune. Tuesday 3:00 PM Address. Retrieved from http://www3.nd.edu/~swarm06/SwarmFest2014/Crypto-economicDesignBabbit.pdf</ref><ref name=dave-thesis>{{ cite thesis | chapter=4.4 | author=Dave Babbitt | docket= | year=2014 | degree=Master's | publisher=Northwestern University | title=Agent-Based Modeling of Peer-to-Peer Economic Systems | oclc= | url= | accessdate= | location=Evanston, IL }}</ref> It can be thought of as a corporation run without any human involvement under the control of an incorruptible set of business rules. These rules are typically implemented as publicly auditable open-source software distributed across the computers of their stakeholders. A human becomes a stakeholder by buying stock in the company or being paid in that stock to provide services for the company. This stock may entitle its owner to a share of the profits of the DAO, participation in its growth, and/or a say in how it is run.<ref name=david-johnston1>[https://github.com/DavidJohnstonCEO/DecentralizedApplications#the-emerging-wave-of-decentralized-applications "The Emerging Wave of Decentralized Applications"]. GitHub. Retrieved 2 July 2014.</ref>

== Terminology ==

=== Autonomous agents ===
In an autonomous agent, there is no necessary specific human involvement outside of some degree of the human effort necessary to build the hardware that the agent runs on. Outside of that, there is no need for any humans to exist that are aware of the agent’s existence. One example of an autonomous agent that already exists today would be a computer virus; the virus survives by replicating itself from machine to machine without deliberate human action.<ref name=vitalik-buterin3>{{cite web|author1=Vitalik Buterin|url=https://blog.ethereum.org/2014/05/06/daos-dacs-das-and-more-an-incomplete-terminology-guide/|website=etherum blog|accessdate=13 August 2014|date=May 6, 2014|title=DAOs, DACs, DAs and More: An Incomplete Terminology Guide}}</ref>

=== Decentralized applications (Dapps) ===
A [[smart contract]] is the simplest form of decentralized automation. It is a mechanism involving [[digital assets]] and two or more parties, where some or all of the parties put assets in and assets are automatically redistributed among those parties according to a formula based on certain data that is not known at the time the contract is initiated. A decentralized application is similar to a smart contract, but different in two key ways. First of all, a decentralized application has an unbounded number of participants on all sides of the market. Second, a decentralized application need not be necessarily financial. [[BitTorrent]] qualifies as a decentralized application, as do [[Popcorn Time]], [[Tor (anonymity network)|Tor]], [[Maidsafe]] and [[Crypti]] (note that Maidsafe and Crypti are also platforms for other decentralized applications).<ref name=vitalik-buterin3 />

=== Decentralized organizations (DOs) ===
A human organization can be defined as a combination of two things: a set of [[property]], and a [[Communications protocol|protocol]] for a [[Set (abstract data type)|set]] of individuals (which may or may not be divided into certain classes with different conditions for entering or leaving the set) to interact with each other, including rules for under what circumstances the individuals may use certain parts of the property.

The idea of a decentralized organization takes the same concept of an organization, and decentralizes it. Instead of a hierarchical structure managed by a set of humans interacting in person and controlling property via the [[legal system]], a decentralized organization involves a set of humans interacting with each other according to a protocol specified in code, and enforced on the [[Block chain (transaction database)|blockchain]].<ref name=vitalik-buterin3 /> The earliest prototype software to link up such a protocol to a blockchain was the Eris 0.1 prototype in June 2014.<ref>{{Cite web|title = Eris - The Dawn of Distributed Autonomous Organizations and The Future of Governance - h+ Media|url = http://hplusmagazine.com/2014/06/17/eris-the-dawn-of-distributed-autonomous-organizations-and-the-future-of-governance/|website = h+ Media|accessdate = 2015-11-02}}</ref>

=== Decentralized autonomous organizations (DAOs) ===
[[File:Quadrant Chart for Classifying DAOs.png|thumb|400px|Vitalik Buterin's Quadrant Chart for Classifying DAOs]]
The main difference between a DO and a DAO is that a DAO has internal capital; that is, a DAO contains some kind of internal property that is valuable in some way, and it has the ability to use that property as a mechanism for rewarding certain activities. [[BitTorrent]] has no internal property, and [[Maidsafe]]-like systems have reputation but that reputation is not a saleable asset. [[Bitcoin]] and [[Namecoin]], on the other hand, do. However, plain old DOs also have internal capital, as do autonomous agents.

DOs and DAOs are both vulnerable to collusion attacks, where a significant percentage of a certain type of members collude to specifically direct its activity. However, in a DO collusion attacks are treated as a bug, whereas in a DAO they are a feature (such as [[majority vote]] in a [[democracy]]).{{Citation needed|date=February 2016}}

An AI is completely autonomous, whereas a DAO still requires heavy involvement from humans specifically interacting according to a protocol defined by the DAO in order to operate.<ref name=vitalik-buterin3 />

==== Decentralized autonomous corporations/companies ====
DACs are basically a subclass of DAOs that pays [[dividend]]s on purchaseable and tradeable [[Share (finance)|shares]] which potentially entitle their holders to continual receipts based on the DAC’s success, to the point where the profit mechanism and the consensus mechanism are not the same thing.<ref name=vitalik-buterin3 /> According to Stan Larimer, President of Invictus Innovations, Inc. (a developer of DACs), an open source DAC with its state information kept public has these characteristics:
* They are '''corporations''' – they are free and independent persons (but don’t have [[legal personality]]).
* They are '''autonomous''' – once up to speed, they no longer need (or heed) their creators.
* They are '''distributed''' – there are no central points of control or failure that can be attacked.
* They are '''transparent''' – their books and business rules are auditable by all.
* They are '''confidential''' – customer information is securely (and incorruptibly) protected.
* They are '''trustworthy''' – because no interaction with them depends on trust.
* They are '''fiduciaries''' – acting solely in their customers’ and shareholders’ interests.
* They are '''self-regulating''' – they robotically obey their own rules.
* They are '''incorruptible''' – no one can exercise seductive or coercive influence over them.
* They are '''sovereign''' – over their digital resources (but don't have [[Capacity (law)|legal capacity]]).<ref name=stan-larimer1>Larimer, Stan. [http://letstalkbitcoin.com/bitcoin-and-the-three-laws-of-robotics/#.UpKv78Ssi-2 "Bitcoin and the Three Laws of Robotics"]. ''Let's Talk Bitcoin''. Retrieved 2 July 2014.</ref>

An example of a currently running DAC is the [[Nu Network]] (based on the open source [[Peershares]] template), which manages the world's first stable digital currency [[NuBits]].{{citation needed|date=November 2015}}

===== Criticism of terminology =====
Some of those interested in new models for building successful and massively scalable applications reject the term, arguing that the classification reintroduces legacy hierarchy-based structures with their regulatory and compliance issues, unnecessarily burdening those involved in their development. For example, in their white paper ''The Emerging Wave of Decentralized Applications'', David Johnston, et al., argue that the term "Distributed Autonomous Corporations" shouldn't be used:<ref name=david-johnston1 />

<blockquote class="templatequote">
It is worth while to note that the authors of this paper agree with many of the concepts proposed by the Invictus authors and the spirit and ethics they [uphold] we embrace wholeheartedly. The point on which we disagree is one of property terminology, “Distributed” and “Autonomous” are great terms, we don’t believe “Corporation” in particular is a desirable term for these entities. One of our primary reservations with using the term is, “Corporation” carries a lot of historical and legal baggage that won’t necessarily best serve the community of developers and entrepreneurs seeking to describe and build these new projects. If you Google the definition of “Corporation” the result is: “a company or group of people authorized to act as a single entity (legally a person) and recognized as such in law.”
</blockquote>

== Economic theory ==

In this economic theory, the role of the [[Business|firm]] is played by the DAO, and the role of the [[Entrepreneurial economics|entrepreneur]] is played by the programmers who develop the DAO.

=== Firm ===

In its typical implementation as publicly auditable rules distributed across the computers of the stakeholders, the DAO can be thought of in a [[Neoclassical economics|neoclassical]] sense as a [[production function]] or [[Production–possibility frontier|production possibilities set]], a black box that transforms inputs into outputs. The DAO can be modeled as a single actor, facing a series of mathematical calculations, implicit in the non-self-verifying data, determined by the characteristics of the production function. The reason that the DAO can exist is because market coordination without it fails due to lack of necessary intersubjective points of orientation, that is, lack of so-called [[Focal point (game theory)|Schelling points]]. The emergence of behavior-coordinating Schelling points is a characteristic of the way that the DAO is coded.<ref name=h-malmgren1>Malmgren, H. B. (1961). "Information, Expectations and the Theory of the Firm". ''Quarterly Journal of Economics'' '''75''': 399-421.</ref>

=== Entrepreneur ===

The entrepreneurship of the DAO's development process can be thought of in a [[Joseph Schumpeter|Schumpeterian]] sense as an exceptional occurrence of massive importance. The programmers who develop and launch the DAO are persons who by introducing "new combinations" shake the economy out of its previous equilibrium, starting a process Schumpeter termed [[creative destruction]].<ref name=marcus-becker1>Becker, Marcus C.; Thorbjørn Knudsen (2003). "The Entrepreneur at a Crucial Juncture in Schumpeter’s Work: Schumpeter’s 1928 Handbook Entry Entrepreneur". ''Advances in Austrian Economics'' '''6''': 199–234.</ref> This speaks to the tenuous relationship between the developers and the DAO they own or contract with, because Schumpeterian entrepreneurship is ''[[sui generis]]'' (independent of its environment).<ref name=nicolai-foss1>Foss NJ, Klein PG. ''Organizing Entrepreneurial Judgment: A New Approach to the Firm''. Cambridge University Press. (2012). ISBN 9780521874427</ref><ref>Foss NJ, Klein PG. Authors Forum:''Organizing Entrepreneurial Judgment: A New Approach to the Firm''. 2012 Austrian Scholars Conference, recorded 8 March 2012 at the Ludwig von Mises Institute in Auburn, Alabama. [https://www.youtube.com/watch?v=a0rJtEBjTA4]</ref>

== Legal issues ==

DAOs currently have no way to indemnify users since they lack [[legal personality]] and may have either no cash-flow or no assets. Accordingly, recovery in the event that a given DAO fails could turn out to be extremely difficult in practice. Consequently, if for example, a DAO does have funds, they may be able to indemnify specific users (namely exchanges) through corporate insurance (a [[Bond (finance)|bond]]).<ref name=swanson1>{{cite web|last1=Swanson|first1=Tim|title=Mitigating the Legal Risks of Issuing Securities on a Cryptoledger|url=http://cointelegraph.com/news/112034/mitigating-the-legal-risks-of-issuing-securities-on-a-cryptoledger|website=Cointelegraph|publisher=Cointelegraph|accessdate=11 July 2014}}</ref>
According to Austin Brister, a Houston-based attorney:
<blockquote class="templatequote">Consumer protection laws can be far-reaching and quite unforgiving. Ordinary businesses do just fine in navigating these laws, even if they don't realize it, because they can adjust their interactions with consumers in "real-time" in order to be reasonable, well-centered, and act in good faith in dealing with consumers. However, the problem with smart contracts, decentralized autonomous organizations, and the like, is that they are hard-wired to act in one way, whether it makes sense or not.

Unforeseeable circumstances practically always present themselves to businesses of all types, and by definition, these circumstances cannot be foreseen or planned for. These systems need to adequately plan for this possibility, and be prepared to be properly insured or adequately bonded in the event things go wrong, and customers are hurt. Similarly, consumers should be aware that they are not dealing with living breathing people, but rather a machine subject only to 0's and 1's.<ref name="swanson1"/>
</blockquote>

== Key architectural principles ==

* '''The [[Black swan theory|Black Swan]] principle''': Because of the impossibility of calculating the risks of consequential rare events and predicting their occurrence, an implementation must be based on ''nonpredictive'' decision-making under uncertainty, with more upside than downside from random events.
* '''The Chessmaster principle''': In general, an implementation must treat people like pawns in a [[chess]] game, patiently moving them into places that often seem harmless or pointless, and getting them to do all the heavy computational lifting. The best implementations will have layers of misdirection and backup plans in case some [[Hacker (computer security)|hacker]] attempts to defraud them, for instance, causing the attacker to do some work for them in the attempt.
* '''[[Finagle's Law]]''': In general, an implementation of a DAO must assume that if there are two or more ways to do something, and one of those ways can result in a catastrophe for the DAO, then someone will choose it. The best implementations rely on low trust protocols and [[behavior-shaping constraint]]s to protect themselves. (Being merely narrow AI, they cannot make nuanced trust judgments and are potentially easy to scam.)

== Layers in the DAO protocol suite ==

The DAO protocol suite uses [[Encapsulation (networking)|encapsulation]] to provide abstraction of protocols and services. Encapsulation is usually aligned with the division of the protocol suite into layers of general functionality. Viewing layers as providing or consuming a service is a method of [[Abstraction (computer science)|abstraction]] to isolate Services Layer protocols from the details of generating addresses, for example, while the Memory Layer avoids having to know the details of each and every market interaction and its protocol.{{citation needed|date=February 2015}}

[[File:Layers in the DAC protocol suite.svg|thumb|This is a diagram of the layers in the protocol suite for a Decentralized Autonomous Organization (DAO).]]

=== Internetworking layer ===

This layer provides a market-wide system of interconnected [[computer network]]s (the [[internet]]). This layer supports the peer-to-peer communications infrastructure that allows the DAO to be distributed and the other layers to interact.{{citation needed|date=February 2015}}

=== Economic layer ===

Technologies like [[Bitcoin]] have enabled this layer, which has the responsibility of maintaining a balance in some [[Cryptocurrency|cryptographic money]], and sending and receiving transactions. It handles non-self-verifying time data so that a transaction cannot spend money before that money was received and cannot spend money that has already been spent. Technologies like [[Mastercoin]] or [[Ripple (monetary system)|Ripple]] provide the [[Distributed computing|distributed]], [[peer-to-peer]] [[payment system]]. This layer depends on the Internetworking layer.{{citation needed|date=February 2015}}

This layer is composed of Type I and Type II decentralized applications, the payment systems being based on the cryptographic money systems with their existing blockchains, having independent protocols and tokens of their own.<ref name=david-johnston1 />

=== Memory layer ===

This layer maintains persistent [[State (computer science)|state information]] about the DAO. Generally, a [[Bitcoin protocol|blockchain]] is used to keep state information public. State information is kept private by using [[secure multiparty computation]] with the inputs split up using an algorithm called [[Shamir's Secret Sharing]]. This allows the DAO to decentrally self-validate some of its own computation, correctly sign transactions, and generate addresses. This layer depends on the Internetworking layer.{{citation needed|date=February 2015}}

=== Data gathering layer ===

This layer handles non-self-verifying data about the real world:
# '''Demand'''. Data about what people want.
# '''Supply'''. Data about what resources are available to obtain what people want.

This layer provides some kind of resource-democracy mechanism to vote on the correct value of some fact, and ensure that humans are incentivized to provide accurate estimates by depriving everyone whose report does not match the “mainstream view” of the monetary reward. This layer depends on the economic layer and the memory layer.{{citation needed|date=February 2015}}

=== Self-modification layer ===

This layer handles allowing humans to modify the DAO so as to future-proof it, e.g. changing APIs and source code. This layer allows DACs to improve themselves by purchasing the services of humans via bilateral hostage contracts, for instance.<ref name=oleg-andreev1>Andreev, Oleg. [http://blog.oleganza.com/post/58240549599/contracts-without-trust-or-third-parties "Contracts without trust or third parties"]. ''Personal Blog''. Retrieved 2 July 2014.</ref> This layer also allows the DAO to set an upper bound on the losses caused by any malicious collusion.<ref>DeFigueiredo, Dimitri do B. [http://dimitrietal.com/trustdavis.pdf "TrustDavis: A Non-Exploitable Online Reputation System"]. Department of Computer Science, University of California at Davis. Retrieved 2 July 2014.</ref> [[A/B testing]] can be used to determine if the delivered work is really better than the old one or not, and only releasing the payment if the results of the test are positive. Alternatively, a quorum of [[Dispute resolution organization|dispute mediators]] can be specified, and they decide if the contract was met or not. This layer depends on the Economic layer and the Memory layer.

=== Output layer ===

This layer interacts with the world using multiparty-signed API requests in a decentralized way. This may include APIs that allow for renting server capacity and then remotely controlling that server, for example, or the ability to post human-readable contracts to [[freelancer]] forums or the [[Amazon Mechanical Turk|Mechanical Turk]]. DACs can expose their services to humans (or other DACs) by selecting a name and then registering it with [[Namecoin]]. Using DNS hierarchies and Namecoin together allows interested parties to monitor for new agents coming online: the act of registering a name under a particular part of the tree automatically advertises its existence. This layer depends on the Economic layer, the Memory layer, and the Data Gathering layer.

This layer is composed of Type III Decentralized Applications, having their own independent protocols and tokens.<ref name=david-johnston1 />

=== Services layer ===

This layer runs the artificial intelligence algorithm that the DAO relies on to detect patterns in real-world data and model it without human intervention. This allows the DAO to create sell-able value fast enough to keep up with its own resource demands in the marketplace of humans. This layer depends on the Economic layer, the Memory layer and the Data Gathering layer.{{citation needed|date=February 2015}}

== Hiring employees ==

Making a fine-grained evaluation of an individual human employee is likely impossible. The best solution is likely to simply use monetary incentives to direct people’s actions on a coarse level, and then let the community self-organize to make the fine-grained adjustments. The extent to which a DAO targets a community for investment and participation, rather than discrete individuals, is the choice of its original developers.<ref>{{cite AV media
| year=2014
| title=Engineering Economic Security
| medium=YouTube
| url=https://www.youtube.com/watch?v=4CFlA8TdWmk&feature=youtu.be
| accessdate=August 11, 2014
| location=Silicon Valley Ethereum Meetup
| publisher=EtherCasts
}}</ref> On the one hand, targeting a community can allow your human support to work together to solve problems in large groups. On the other hand, keeping everyone separate prevents collusion, and in that way reduces the likelihood of a hostile takeover.<ref name=vitalik-buterin1>Buterin, Vitalik. [http://bitcoinmagazine.com/7119/bootstrapping-an-autonomous-decentralized-corporation-part-2-interacting-with-the-world/ "Bootstrapping An Autonomous Decentralized Corporation, Part 2: Interacting With the World"]. ''Bitcoin Magazine™''. Coin Publishing Ltd. Retrieved 22 November 2013.</ref>

== Hostile takeovers ==

A hostile takeover of a DAO handling money means that the attacker gains the ability to drain the DAO’s entire wallet. Countering hostile takeovers requires certain economic measures to establish consensus:
* '''[[Proof of work]]''' is used to deter denial of service attacks by requiring some work from the service requester that is moderately hard (but feasible) on the requester side but easy to check for the service provider. This is commonly referred to as "mining".<ref name=david-johnston1 />
* '''Proof of stake''' is used to deter other service abuses such as a [[Sybil attack]].

Another counter-measure might simply be to allow the decentralized corporation to have shareholders, so that shareholders get some kind of special voting privileges, along with the right to a share of the profits, in exchange for investing. (Shareholders benefit if the price goes up, so shareholders are encouraged to do things that increase the price.) This would incentivize the shareholders to protect their investment.

=== Sybil attacks ===
{{see also | Sybil attack}}
A hostile takeover could be accomplished by a successful Sybil attack, say through a [[botnet]], overwhelming the resource-democracy mechanism by controlling over half of the servers in the network.

Requiring each participating node to show proof that it controls some moderately large amount of crypto-currency would prevent this kind of attack. Then implementing a hostile takeover would require more resources than all of the legitimate nodes committed together. The moderately large amount of crypto-currency could even be moved to a multisignature address partially controlled by the network as a [[surety bond]], both discouraging nodes from cheating and giving their owners a great incentive to act and even get together to keep the corporation alive.

== Examples ==

=== Applications ===

There are three major categories of industries where DACs will be able to survive on their own merits and provide genuine value to society: ''natural monopolies'', ''illegal entities'', and ''entities of extremely low profitability''.

{{example farm|section|date=July 2014}}

==== Natural monopolies ====

A [[natural monopoly]] is a monopoly in an industry in which it is most efficient (involving the lowest long-run average cost) for production to be concentrated in a single firm: [[Communications protocol|software protocols]], [[Programming language|languages]] and to some extent [[Social networking service|social networks]] and [[currencies]]. A DAO can theoretically be designed so that no one involved in the price-setting mechanism has an incentive to fix prices over market rates. More generally, they can be made invulnerable to corruption in ways unimaginable in human-controlled system, although great care would certainly need to be taken not to introduce other vulnerabilities instead.<ref name=vitalik-buterin1 />
* Identity Corp, a corporation whose sole purpose is to create cryptographically secure identity documents for individuals that they could sign messages with, and are linked to individuals’ physical identities.<ref name=vitalik-buterin2>Buterin, Vitalik. [http://bitcoinmagazine.com/7235/bootstrapping-a-decentralized-autonomous-corporation-part-3-identity-corp/ "Bootstrapping a Decentralized Autonomous Corporation, Part 3: Identity Corp"]. ''Bitcoin Magazine™''. Coin Publishing Ltd. Retrieved 23 November 2013.</ref>

==== Illegal entities ====

Because of a combination of the DAO's incorruptible nature and the explosive growth in [[Rulemaking|regulations]], services that violate government laws and regulations are unavoidable. But their decentralized nature makes it extremely difficult to prevent them from taking over illegal markets. As Satoshi Nakamoto said, "Governments are good at cutting off the heads of a centrally controlled networks like Napster, but pure P2P networks like Gnutella and Tor seem to be holding their own".<ref>[https://bitcointalk.org/index.php?topic=26878.15%3Bwap2 "The root of the problem!"].</ref>
* Decentralized file-sharing networks for copyright infringement
* A captcha-cracker, that requires CPU. People pay for the Captchas to be cracked and the DAO provides some kind of API for people to offer their CPU and hosting of the software, if they do so, they get bitcoins. Putting this up online, with some marketing, the software should survive on its own as long as there are captchas that needs to be cracked.

==== Not-For-Profit Entities ====

Finally, there are those cases where a decentralized network can simply maintain itself more efficiently and provides better services than any centralized alternative.
* BitShares - a DAC industry with the purpose of providing infrastructure and software for other DACs. Currently available DACs within BitShares ecosystem:
** BitSharesX - a family of DACs that implement the business model of a bank and exchange.
* Colored Coins are working on defining themselves as a DAO
* Crop insurance
* Mitosys - a DAC replacement for Bit-Message
* Social network - Monetizable Diaspora
* StorJ, a simple drop-box style file service with pay per use via bitcoin (and perhaps with naming provided via namecoin and/or tor hidden services).<ref name=jeff-garzik1>Garzik, Jeff. [http://garzikrants.blogspot.ch/2013/01/storj-and-bitcoin-autonomous-agents.html "StorJ, and Bitcoin autonomous agents"]. ''Random blatherings by Jeff''. Blogger. Retrieved 22 November 2013.</ref> StorJ isn't smart enough to judge bad proposals on its own — instead it forms agreements that make it unprofitable to cheat.
* The peer-to-peer network used by [[Blizzard]] to distribute updates to its massively multiplayer online game [[World of Warcraft]]
* Weather network
* [[Bitcoin protocol|Bitcoin]] itself and all of Bitcoin forks/Altcurrencies
* [http://garzikrants.blogspot.com/2014/01/blackbox-bitcoin-enabled-decentralized.html blackbox] is a Bitcoin-enabled, decentralized cloud that uses TradeNet
* [https://github.com/wetube/wetube-web Wetube]

=== Examples in literature ===

* In Daniel Suarez's [[techno-thriller]], ''[[Daemon (book series)|Daemon]]'', a collection of sophisticated computer programs have been left sitting passive on machines scattered around the Internet until one of them reads the programmer's obituary, which sends triggers to other systems which activate a number of other distributed processes, awakening the DAO.

== See also ==

* [[Bitcoin protocol]]
* [[Decentralized computing]]
* [[Incentive-centered design]]
* [[Merkle tree]]
* [[Monero (cryptocurrency)|Monero]]
* [[Serious game]]

== References ==
{{Reflist|2}}

== External links ==
{{External links|section|date=December 2015}}
{{refbegin|2}}
* [http://aeon.co/magazine/technology/are-we-ready-for-companies-that-run-themselves/ RoboCorp - Get ready for companies that run themselves. But will the autonomous economy set us all free, or just make the rich richer?], David Z. Morris, ''[[Aeon (digital magazine)]]''
* [http://www.npr.org/blogs/parallels/2015/02/01/382648685/in-sweden-remote-control-airport-is-a-reality In Sweden, Remote-Control Airport Is A Reality], Ari Shapiro, ''[[National Public Radio (United States)|National Public Radio]]''
* [http://bitcoin.org/bitcoin.pdf Bitcoin: A Peer-to-Peer Electronic Cash System] bitcoin.org
* [http://bitcoinmagazine.com/7050/bootstrapping-a-decentralized-autonomous-corporation-part-i/ Bootstrapping a DAC Part 1] Bitcoin Magazine
* [http://bitsharestalk.org/index.php?topic=297.0 Topic on bitsharestalk] bitsharestalk.org
* [http://ethereum.org/ethereum.html Ethereum]: A Next-Generation Generalized Smart Contract and Decentralized Application Platform
* [http://wiki.ethereum.org/index.php/Dagger Dagger] is a proof of work algorithm, intended to provide a memory-hard proof of work based on moderately connected directed acyclic graphs. wiki.ethereum.org
* [http://wiki.ethereum.org/index.php/Patricia_Tree Patricia Tree] wiki.ethereum.org
* [https://blog.ethereum.org/2014/05/06/daos-dacs-das-and-more-an-incomplete-terminology-guide/ DAOs, DACs, DAs and More: An Incomplete Terminology Guide] blog.ethereum.org
* [http://garzikrants.blogspot.ca/2013/01/storj-and-bitcoin-autonomous-agents.html StorJ, and Bitcoin autonomous agents] garzikrants.blogspot
* [http://letstalkbitcoin.com/bitcoin-and-the-three-laws-of-robotics/ Bitcoin and the Three Laws of Robotics] letstalkbitcoin.com
* [http://letstalkbitcoin.com/dac-revisited/ DAC Revisited] letstalkbitcoin.com
* [http://letstalkbitcoin.com/dacs-that-spawn-dacs/ DACs That Spawn DACs?] letstalkbitcoin.com
* [http://letstalkbitcoin.com/is-bitcoin-overpaying-for-false-security/ The Hidden Costs of Bitcoin] letstalkbitcoin.com
* [http://tvtropes.org/pmwiki/pmwiki.php/Literature/Daemon TV Tropes Analysis of Daemon] tvtropes.org
* [http://wavism.net/group3/distributed-autonomous-virtual-state-davs/ Distributed Autonomous Virtual State] wavism.net
* [http://www.amazon.com/Great-Chain-Numbers-Contracts-Management-ebook/dp/B00IRUBMXO Great Chain of Numbers: A Guide to Smart Contracts, Smart Property and Trustless Asset Management] amazon.com
* [http://www.cs.huji.ac.il/~avivz/pubs/13/btc_scalability_full.pdf Accelerating Bitcoin's Transaction Processing] Fast Money Grows on Trees, Not Chains, cs.huji.ac.il
* [http://www.youtube.com/watch?v=Pu4PAMFPo5Y Mike Hearn's talk on autonomous agents, Turing Festival 2013] YouTube
* [https://docs.google.com/document/d/1AnkP_cVZTCMLIzw4DvsW6M8Q2JC0lIzrTLuoWu2z1BE/edit#heading=h.v3px1rgmf10o Colored Coins]
* [https://en.bitcoin.it/wiki/Agents Bitcoin-using autonomous agents] Bitcoin wiki
* [https://en.bitcoin.it/wiki/Contracts Contracts] Bitcoin wiki
* [https://en.bitcoin.it/wiki/List_of_Decentralized_Autonomous_Corporations List of Decentralized Autonomous Corporations] Bitcoin wiki
* [https://en.bitcoin.it/wiki/Scalability#Simplified_payment_verification Simplified payment verification] Bitcoin wiki
* [https://en.bitcoin.it/wiki/Smart_Property Smart Property] Bitcoin wiki
* [https://en.wikibooks.org/wiki/Seed_Factories/WWF Distributed Production Network] wikibooks.org
* [https://github.com/mastercoin-MSC/spec The Master Protocol - Mastercoin Complete Specification] github.com
{{refend}}

{{DEFAULTSORT:Distributed Computing}}
[[Category:Anarcho-capitalism]]
[[Category:Application layer protocols]]
[[Category:Applications of cryptography]]
[[Category:Computer law]]
[[Category:Computer networking]]
[[Category:Crypto-anarchism]]
[[Category:Cryptography]]
[[Category:Distributed computing]]
[[Category:Distributed data storage]]
[[Category:E-commerce]]
[[Category:Network protocols]]
[[Category:Payment systems]]
[[Category:Peer-to-peer computing]]
[[Category:Production economics]]
[[Category:Cryptocurrencies]]

Jim Keller

2016-01-29T16:43:34Z

Intgr: Update occupation in infobox

{{Use dmy dates|date=November 2015}}
{{Infobox person
| name = Jim Keller
| image = 
| alt =
| caption =
| birth_name = 
| birth_date = 
| birth_place =
| death_date = 
| death_place =
| nationality =
| other_names =
| occupation = Vice President of Autopilot Hardware Engineering at [[Tesla Motors]]<ref name=electrek-tesla />
| years_active =
| known_for = {{Plainlist|
* AMD K7
* AMD K8 (lead architect)
* Apple A4, A5
* x86-64 (coauthor)
* HyperTransport (coauthor)
}}
| notable_works =
}}

'''Jim Keller''' is a [[microprocessor]] [[engineer]] most well known for his work at [[AMD]] and [[Apple Inc.|Apple]]. He was the lead architect of [[AMD K8]] microarchitecture<ref name=anandtech>{{cite news |url=http://www.anandtech.com/show/6129/apple-a4a5-designer-k8-lead-architect-jim-keller-returns-to-amd |title=Apple A4/A5 Designer & K8 Lead Architect, Jim Keller, Returns to AMD |author=[[Anand Lal Shimpi]] |date=1 August 2012 |work=[[AnandTech]] }}</ref><ref name=xbitlabs>{{cite news |url=http://www.xbitlabs.com/news/cpu/display/20120801190422_Return_of_the_King_AMD_K7_and_K8_Designer_Jim_Keller_Back_at_AMD.html |title=Return of the King: AMD K7 and K8 Designer Jim Keller Back at AMD |author=Anton Shilov |date=1 August 2012 |work=X-bit Labs }}</ref><ref name=computing>{{cite news |url=http://www.computing.co.uk/ctg/news/2344223/amd-to-design-new-micro-architecture-for-2015-launch-under-chip-guru-jim-keller |title=AMD to design new micro-architecture for 2015 launch under chip guru Jim Keller |author=Graeme Burton |date=12 May 2014 |work=computing.co.uk }}</ref> (including the original [[Athlon 64]])<ref name=anandtech /><ref name=thenextweb>{{cite news |url=http://thenextweb.com/insider/2012/08/01/apples-cpu-architect-jim-keller-departs-to-head-up-chipmaker-amds-processor-group/ |title=Apple's CPU Architect Jim Keller Jumps To AMD |author=Robin Wauters |date=1 August 2012 |work=[[The Next Web]] }}</ref><ref name=cultofmac>{{cite news |url=http://www.cultofmac.com/182296/amd-hires-ax-series-architect-jim-keller-away-from-apple-to-report-to-mark-papermaster/ |title=AMD Hires Ax Series Architect Jim Keller Away From Apple To Report To Mark Papermaster |author=John Brownlee |date=1 August 2012 |work=Cult of Mac}}</ref> and was involved in designing the [[Athlon]] (K7)<ref name=computing /> and [[Apple A4]]/[[Apple A5|A5]] processors.<ref name=anandtech /><ref name=venturebeat>{{cite news |url=http://venturebeat.com/2012/08/01/apple-cpu-jim-keller-amd/ |title=Apple CPU lead Jim Keller heads back to AMD as chief architect |author=Devindra Hardawar |date=1 August 2012 |work=[[VentureBeat]] }}</ref><ref name=theverge>{{cite news |url=http://www.theverge.com/2012/8/1/3212406/jim-keller-joins-amd-vp-chief-architect |title=Former Apple chip designer Jim Keller joins AMD as chief architect and VP |author=Adi Robertson |date=1 August 2012 |publisher=Vox Media |work=[[The Verge]] }}</ref><ref name=allthingsd>{{cite news |url=http://allthingsd.com/20120801/amd-hires-apples-head-chip-designer/ |title=AMD Hires Apple's Head Chip Designer |author=Arik Hesseldahl |date=1 August 2012 |work=[[AllThingsD]] }}</ref> He was also the coauthor of the specifications for the [[x86-64]] instruction set<ref name=venturebeat /><ref name=itworld>{{cite news |url=http://www.itworld.com/article/2693371/is-amd-finally-ready-to-give-intel-a-real-fight.html |title=AMD roadmap: Is AMD finally ready to give Intel a real fight? |author=Andy Patrizio |date=16 May 2014 |work=ITworld}}</ref> and [[HyperTransport]] interconnect.<ref name=anandtech/><ref name=itworld /><ref name=semiaccurate>{{cite news |url=http://semiaccurate.com/2012/08/01/apples-cpu-architect-jim-keller-moves-back-to-amd/ |title=Apple's CPU architect Jim Keller moves back to AMD |author=Charlie Demerjian |date=1 August 2012 |work=[[SemiAccurate]] }}</ref> From 2012 to 2015, he returned to AMD to work on the [[AMD K12]]<ref name=decryptedtech>{{cite news |url=http://www.decryptedtech.com/news/amd-brings-k7-k8-creator-jim-keller-back-into-the-fold |title=AMD Brings K7/K8 Creator, Jim Keller, Back Into the Fold |author=Sean Kalinich |date=27 June 2014 |work=decryptedtech.com }}</ref> and [[AMD Zen|Zen]] microarchitectures,<ref name=kitguru>{{cite news |url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/ |title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be |author=Anton Shilov |date=11 September 2014 |work=kitguru.net }}</ref><ref name=wccftech>{{cite news |url=http://wccftech.com/amd-confirms-development-of-high-performance-x86-core-with-completely-new-architecture/ |title=AMD Confirms Development of High-Performance x86 Core With Completely New Architecture |author=Hassan Mujtaba |date=5 May 2014 |work=WCCFtech }}</ref> particularly on the low-power/embedded versions.<ref name=cultofmac /><ref name=allthingsd />

== Career ==
Jim Keller was working at [[Digital Equipment Corporation|DEC]] until 1998, where he was involved in designing the [[Alpha 21164]] and [[Alpha 21264|21264]] processors.<ref name=anandtech /><ref name=xbitlabs /> In 1998 he moved to AMD, where he worked to launch the AMD [[Athlon]] (K7) processor and was the lead architect of the [[AMD K8]] microarchitecture,<ref name=9to5mac>{{cite news |url=http://9to5mac.com/2012/08/01/apple-cpu-guru-jim-keller-who-came-with-pa-semi-deal-departs-back-to-amd-to-lead-group-under-mark-papermaster/ |title=Apple CPU guru Jim Keller, who came with PA Semi deal, departs back to AMD to lead group under Mark Papermaster |author=Seth Weintraub |date=1 August 2012 |work=9to5Mac }}</ref> which also included designing the x86-64 instruction set and HyperTransport interconnect mainly used for [[multiprocessor]] communications.<ref name=anandtech />

In 1999, he left AMD to work at [[SiByte]] to design [[MIPS instruction set|MIPS]]-based processors for 1 Gbit/s network interfaces and other devices.<ref name=xbitlabs /><ref name=semiaccurate /><ref>{{cite web |url=http://www.techspot.com/news/49611-apple-chip-designer-jim-keller-heads-back-to-amd.html |title=Apple chip designer Jim Keller heads back to AMD |author=Jose Vilches |date=1 August 2012 |work=[[TechSpot]]}}</ref> In November 2000, SiByte was acquired by [[Broadcom]],<ref>{{cite news |url=http://www.wsj.com/articles/SB973519053768422247 |title=Broadcom Agrees to Acquire SiByte for $2 Billion in Stock |author=Molly Williams |date=7 November 2000 |work=[[Wall Street Journal]]}}</ref> where he continued as chief architect<ref name=theverge /> until 2004.<ref name=anandtech />

In 2004 he moved to serve as the Vice President of Engineering at [[P.A. Semi]],<ref name=anandtech /><ref name=itworld /> a company specializing in low-power mobile processors.<ref name=xbitlabs /> P.A. Semi was acquired by Apple in 2008, and Keller followed,<ref name=thenextweb /><ref name=9to5mac /> becoming part of a team to design the Apple A4 and A5 [[system-on-a-chip]] mobile processors. These processors were used in several Apple products, including [[iPhone 4]], [[iPhone 4S|4S]], [[iPad]] and [[iPad 2]].

In August 2012, Jim Keller returned to AMD, where his primary task was to design a new generation [[microarchitecture]]<ref name=computing /><ref name=itworld /><ref name=wccftech /> called [[Zen (microarchitecture)|Zen]].<ref name=kitguru /> After years of being unable to compete with [[Intel]] in the high-end [[CPU]] market, the new generation of Zen processors is hoped to restore AMD's position in the high-end [[x86-64]] processor market.<ref name=anandtech /><ref name=decryptedtech /> On 18 September 2015, Keller departed from AMD to pursue other opportunities, ending his three-year employment at AMD.<ref>{{cite news |last1=Mann |first1=Parm |title=Legendary CPU architect Jim Keller leaves AMD |url=http://hexus.net/tech/news/cpu/86585-legendary-cpu-architect-jim-keller-leaves-amd/ |accessdate=18 September 2015}}</ref>

In January 2016, Keller joined [[Tesla Motors]] as as Vice President of Autopilot Hardware Engineering.<ref name=electrek-tesla>{{cite news |url=http://electrek.co/2016/01/28/tesla-jim-keller-apple-processor-architect-2/ |author=Seth Weintraub |date=28 January 2016 |title=The chip guru who built Apple’s Ax microprocessors joins Tesla to lead the Autopilot Hardware Engineering team |work=Electrek }}</ref>

== References ==
{{Reflist|30em}}

{{DEFAULTSORT:Keller, Jim}}
[[Category:Living people]]
[[Category:Advanced Micro Devices people]]
[[Category:American engineers]]
[[Category:Computer hardware engineers]]
[[Category:Apple Inc. ex-employees]]

{{engineer-stub}}

Jim Keller

2016-01-29T16:42:09Z

Intgr: Fill out ref fields & specify month/year in the article, minor tweaks

{{Use dmy dates|date=November 2015}}
{{Infobox person
| name = Jim Keller
| image = 
| alt =
| caption =
| birth_name = 
| birth_date = 
| birth_place =
| death_date = 
| death_place =
| nationality =
| other_names =
| occupation = Former Chief Architect of Microprocessor Cores and Corporate Vice President, Advanced Micro Devices<ref>{{cite web |url=http://www.bloomberg.com/research/stocks/people/person.asp?personId=215060089&ticker=AMD&previousCapId=168864&previousTitle=ADVANCED%20MICRO%20DEVICES |title=Jim Keller: Executive Profile & Biography |work=[[Bloomberg Business]] |accessdate=14 May 2015 }}</ref><ref name=bit-tech>{{cite web |url=http://www.bit-tech.net/news/hardware/2012/08/02/amd-jim-keller/1 |title=AMD re-hires Athlon 64 K8 designer Jim Keller |author=Gareth Halfacree |date=2 August 2012 |work=bit-tech }}</ref>
| years_active =
| known_for = {{Plainlist|
* AMD K7
* AMD K8 (lead architect)
* Apple A4, A5
* x86-64 (coauthor)
* HyperTransport (coauthor)
}}
| notable_works =
}}

'''Jim Keller''' is a [[microprocessor]] [[engineer]] most well known for his work at [[AMD]] and [[Apple Inc.|Apple]]. He was the lead architect of [[AMD K8]] microarchitecture<ref name=anandtech>{{cite news |url=http://www.anandtech.com/show/6129/apple-a4a5-designer-k8-lead-architect-jim-keller-returns-to-amd |title=Apple A4/A5 Designer & K8 Lead Architect, Jim Keller, Returns to AMD |author=[[Anand Lal Shimpi]] |date=1 August 2012 |work=[[AnandTech]] }}</ref><ref name=xbitlabs>{{cite news |url=http://www.xbitlabs.com/news/cpu/display/20120801190422_Return_of_the_King_AMD_K7_and_K8_Designer_Jim_Keller_Back_at_AMD.html |title=Return of the King: AMD K7 and K8 Designer Jim Keller Back at AMD |author=Anton Shilov |date=1 August 2012 |work=X-bit Labs }}</ref><ref name=computing>{{cite news |url=http://www.computing.co.uk/ctg/news/2344223/amd-to-design-new-micro-architecture-for-2015-launch-under-chip-guru-jim-keller |title=AMD to design new micro-architecture for 2015 launch under chip guru Jim Keller |author=Graeme Burton |date=12 May 2014 |work=computing.co.uk }}</ref> (including the original [[Athlon 64]])<ref name=anandtech /><ref name=thenextweb>{{cite news |url=http://thenextweb.com/insider/2012/08/01/apples-cpu-architect-jim-keller-departs-to-head-up-chipmaker-amds-processor-group/ |title=Apple's CPU Architect Jim Keller Jumps To AMD |author=Robin Wauters |date=1 August 2012 |work=[[The Next Web]] }}</ref><ref name=cultofmac>{{cite news |url=http://www.cultofmac.com/182296/amd-hires-ax-series-architect-jim-keller-away-from-apple-to-report-to-mark-papermaster/ |title=AMD Hires Ax Series Architect Jim Keller Away From Apple To Report To Mark Papermaster |author=John Brownlee |date=1 August 2012 |work=Cult of Mac}}</ref> and was involved in designing the [[Athlon]] (K7)<ref name=computing /> and [[Apple A4]]/[[Apple A5|A5]] processors.<ref name=anandtech /><ref name=venturebeat>{{cite news |url=http://venturebeat.com/2012/08/01/apple-cpu-jim-keller-amd/ |title=Apple CPU lead Jim Keller heads back to AMD as chief architect |author=Devindra Hardawar |date=1 August 2012 |work=[[VentureBeat]] }}</ref><ref name=theverge>{{cite news |url=http://www.theverge.com/2012/8/1/3212406/jim-keller-joins-amd-vp-chief-architect |title=Former Apple chip designer Jim Keller joins AMD as chief architect and VP |author=Adi Robertson |date=1 August 2012 |publisher=Vox Media |work=[[The Verge]] }}</ref><ref name=allthingsd>{{cite news |url=http://allthingsd.com/20120801/amd-hires-apples-head-chip-designer/ |title=AMD Hires Apple's Head Chip Designer |author=Arik Hesseldahl |date=1 August 2012 |work=[[AllThingsD]] }}</ref> He was also the coauthor of the specifications for the [[x86-64]] instruction set<ref name=venturebeat /><ref name=itworld>{{cite news |url=http://www.itworld.com/article/2693371/is-amd-finally-ready-to-give-intel-a-real-fight.html |title=AMD roadmap: Is AMD finally ready to give Intel a real fight? |author=Andy Patrizio |date=16 May 2014 |work=ITworld}}</ref> and [[HyperTransport]] interconnect.<ref name=anandtech/><ref name=itworld /><ref name=semiaccurate>{{cite news |url=http://semiaccurate.com/2012/08/01/apples-cpu-architect-jim-keller-moves-back-to-amd/ |title=Apple's CPU architect Jim Keller moves back to AMD |author=Charlie Demerjian |date=1 August 2012 |work=[[SemiAccurate]] }}</ref> From 2012 to 2015, he returned to AMD to work on the [[AMD K12]]<ref name=decryptedtech>{{cite news |url=http://www.decryptedtech.com/news/amd-brings-k7-k8-creator-jim-keller-back-into-the-fold |title=AMD Brings K7/K8 Creator, Jim Keller, Back Into the Fold |author=Sean Kalinich |date=27 June 2014 |work=decryptedtech.com }}</ref> and [[AMD Zen|Zen]] microarchitectures,<ref name=kitguru>{{cite news |url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/ |title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be |author=Anton Shilov |date=11 September 2014 |work=kitguru.net }}</ref><ref name=wccftech>{{cite news |url=http://wccftech.com/amd-confirms-development-of-high-performance-x86-core-with-completely-new-architecture/ |title=AMD Confirms Development of High-Performance x86 Core With Completely New Architecture |author=Hassan Mujtaba |date=5 May 2014 |work=WCCFtech }}</ref> particularly on the low-power/embedded versions.<ref name=cultofmac /><ref name=allthingsd />

== Career ==
Jim Keller was working at [[Digital Equipment Corporation|DEC]] until 1998, where he was involved in designing the [[Alpha 21164]] and [[Alpha 21264|21264]] processors.<ref name=anandtech /><ref name=xbitlabs /> In 1998 he moved to AMD, where he worked to launch the AMD [[Athlon]] (K7) processor and was the lead architect of the [[AMD K8]] microarchitecture,<ref name=9to5mac>{{cite news |url=http://9to5mac.com/2012/08/01/apple-cpu-guru-jim-keller-who-came-with-pa-semi-deal-departs-back-to-amd-to-lead-group-under-mark-papermaster/ |title=Apple CPU guru Jim Keller, who came with PA Semi deal, departs back to AMD to lead group under Mark Papermaster |author=Seth Weintraub |date=1 August 2012 |work=9to5Mac }}</ref> which also included designing the x86-64 instruction set and HyperTransport interconnect mainly used for [[multiprocessor]] communications.<ref name=anandtech />

In 1999, he left AMD to work at [[SiByte]] to design [[MIPS instruction set|MIPS]]-based processors for 1 Gbit/s network interfaces and other devices.<ref name=xbitlabs /><ref name=semiaccurate /><ref>{{cite web |url=http://www.techspot.com/news/49611-apple-chip-designer-jim-keller-heads-back-to-amd.html |title=Apple chip designer Jim Keller heads back to AMD |author=Jose Vilches |date=1 August 2012 |work=[[TechSpot]]}}</ref> In November 2000, SiByte was acquired by [[Broadcom]],<ref>{{cite news |url=http://www.wsj.com/articles/SB973519053768422247 |title=Broadcom Agrees to Acquire SiByte for $2 Billion in Stock |author=Molly Williams |date=7 November 2000 |work=[[Wall Street Journal]]}}</ref> where he continued as chief architect<ref name=theverge /> until 2004.<ref name=anandtech />

In 2004 he moved to serve as the Vice President of Engineering at [[P.A. Semi]],<ref name=anandtech /><ref name=itworld /> a company specializing in low-power mobile processors.<ref name=xbitlabs /> P.A. Semi was acquired by Apple in 2008, and Keller followed,<ref name=thenextweb /><ref name=9to5mac /> becoming part of a team to design the Apple A4 and A5 [[system-on-a-chip]] mobile processors. These processors were used in several Apple products, including [[iPhone 4]], [[iPhone 4S|4S]], [[iPad]] and [[iPad 2]].

In August 2012, Jim Keller returned to AMD, where his primary task was to design a new generation [[microarchitecture]]<ref name=computing /><ref name=itworld /><ref name=wccftech /> called [[Zen (microarchitecture)|Zen]].<ref name=kitguru /> After years of being unable to compete with [[Intel]] in the high-end [[CPU]] market, the new generation of Zen processors is hoped to restore AMD's position in the high-end [[x86-64]] processor market.<ref name=anandtech /><ref name=decryptedtech /> On 18 September 2015, Keller departed from AMD to pursue other opportunities, ending his three-year employment at AMD.<ref>{{cite news |last1=Mann |first1=Parm |title=Legendary CPU architect Jim Keller leaves AMD |url=http://hexus.net/tech/news/cpu/86585-legendary-cpu-architect-jim-keller-leaves-amd/ |accessdate=18 September 2015}}</ref>

In January 2016, Keller joined [[Tesla Motors]] as as Vice President of Autopilot Hardware Engineering.<ref>{{cite news |url=http://electrek.co/2016/01/28/tesla-jim-keller-apple-processor-architect-2/ |author=Seth Weintraub |date=28 January 2016 |title=The chip guru who built Apple’s Ax microprocessors joins Tesla to lead the Autopilot Hardware Engineering team |work=Electrek }}</ref>

== References ==
{{Reflist|30em}}

{{DEFAULTSORT:Keller, Jim}}
[[Category:Living people]]
[[Category:Advanced Micro Devices people]]
[[Category:American engineers]]
[[Category:Computer hardware engineers]]
[[Category:Apple Inc. ex-employees]]

{{engineer-stub}}

Dezentralisierte Autonome Organisation

2016-01-19T12:39:40Z

Intgr: Revert spamlink, WP:EL. Undid revision 700581234 by 91.64.6.201 (talk)

{{refimprove|date=February 2015}}
A '''decentralized autonomous organization''' (DAO), '''fully automated business entity''' (FAB), or '''distributed autonomous corporation/company''' (DAC) is a decentralized network of narrow-AI [[autonomous agent]]s which perform an output-maximizing production function and which divides its labor into computationally intractable tasks (which it incentivizes humans to do) and tasks which it performs itself.<ref name=dave-talk>Babbitt, Dave. "Crypto-Economic Design: A Proposed Agent-Based Modeling Effort." SwarmFest 2014: 18th Annual Meeting on Agent-Based Modeling & Simulation, University of Notre Dame, McKenna Hall Auditorium, Notre Dame, IN USA, June 29 - July 1, 2014. Ed. Greg Madey & Ryan McCune. Tuesday 3:00 PM Address. Retrieved from http://www3.nd.edu/~swarm06/SwarmFest2014/Crypto-economicDesignBabbit.pdf</ref><ref name=dave-thesis>{{ cite thesis | chapter=4.4 | author=Dave Babbitt | docket= | year=2014 | degree=Master's | publisher=Northwestern University | title=Agent-Based Modeling of Peer-to-Peer Economic Systems | oclc= | url= | accessdate= | location=Evanston, IL }}</ref> It can be thought of as a corporation run without any human involvement under the control of an incorruptible set of business rules. These rules are typically implemented as publicly auditable open-source software distributed across the computers of their stakeholders. A human becomes a stakeholder by buying stock in the company or being paid in that stock to provide services for the company. This stock may entitle its owner to a share of the profits of the DAO, participation in its growth, and/or a say in how it is run.<ref name=david-johnston1>[https://github.com/DavidJohnstonCEO/DecentralizedApplications#the-emerging-wave-of-decentralized-applications "The Emerging Wave of Decentralized Applications"]. GitHub. Retrieved 2 July 2014.</ref>

== Terminology ==

=== Autonomous agents ===
In an autonomous agent, there is no necessary specific human involvement outside of some degree of the human effort necessary to build the hardware that the agent runs on. Outside of that, there is no need for any humans to exist that are aware of the agent’s existence. One example of an autonomous agent that already exists today would be a computer virus; the virus survives by replicating itself from machine to machine without deliberate human action.<ref name=vitalik-buterin3>{{cite web|author1=Vitalik Buterin|url=https://blog.ethereum.org/2014/05/06/daos-dacs-das-and-more-an-incomplete-terminology-guide/|website=etherum blog|accessdate=13 August 2014|date=May 6, 2014|title=DAOs, DACs, DAs and More: An Incomplete Terminology Guide}}</ref>

=== Decentralized applications (Dapps) ===
A [[smart contract]] is the simplest form of decentralized automation. It is a mechanism involving [[digital assets]] and two or more parties, where some or all of the parties put assets in and assets are automatically redistributed among those parties according to a formula based on certain data that is not known at the time the contract is initiated. A decentralized application is similar to a smart contract, but different in two key ways. First of all, a decentralized application has an unbounded number of participants on all sides of the market. Second, a decentralized application need not be necessarily financial. [[BitTorrent]] qualifies as a decentralized application, as do [[Popcorn Time]], [[Tor (anonymity network)|Tor]], [[Maidsafe]] and [[Crypti]] (note that Maidsafe and Crypti are also platforms for other decentralized applications).<ref name=vitalik-buterin3 />

=== Decentralized organizations (DOs) ===
A human organization can be defined as a combination of two things: a set of [[property]], and a [[Communications protocol|protocol]] for a [[Set (abstract data type)|set]] of individuals (which may or may not be divided into certain classes with different conditions for entering or leaving the set) to interact with each other, including rules for under what circumstances the individuals may use certain parts of the property.

The idea of a decentralized organization takes the same concept of an organization, and decentralizes it. Instead of a hierarchical structure managed by a set of humans interacting in person and controlling property via the [[legal system]], a decentralized organization involves a set of humans interacting with each other according to a protocol specified in code, and enforced on the [[Block chain (transaction database)|blockchain]].<ref name=vitalik-buterin3 /> The earliest prototype software to link up such a protocol to a blockchain was the Eris 0.1 prototype in June 2014.<ref>{{Cite web|title = Eris - The Dawn of Distributed Autonomous Organizations and The Future of Governance - h+ Media|url = http://hplusmagazine.com/2014/06/17/eris-the-dawn-of-distributed-autonomous-organizations-and-the-future-of-governance/|website = h+ Media|accessdate = 2015-11-02}}</ref>

=== Decentralized autonomous organizations (DAOs) ===
[[File:Quadrant Chart for Classifying DAOs.png|thumb|400px|Vitalik Buterin's Quadrant Chart for Classifying DAOs]]
The main difference between a DO and a DAO is that a DAO has internal capital; that is, a DAO contains some kind of internal property that is valuable in some way, and it has the ability to use that property as a mechanism for rewarding certain activities. [[BitTorrent]] has no internal property, and [[Maidsafe]]-like systems have reputation but that reputation is not a saleable asset. [[Bitcoin]] and [[Namecoin]], on the other hand, do. However, plain old DOs also have internal capital, as do autonomous agents.

DOs and DAOs are both vulnerable to collusion attacks, where a significant percentage of a certain type of members collude to specifically direct its activity. However, in a DAO collusion attacks are treated as a bug, whereas in a DO they are a feature (such as [[majority vote]] in a [[democracy]]).

An AI is completely autonomous, whereas a DAO still requires heavy involvement from humans specifically interacting according to a protocol defined by the DAO in order to operate.<ref name=vitalik-buterin3 />

==== Decentralized autonomous corporations/companies ====
DACs are basically a subclass of DAOs that pays [[dividend]]s on purchaseable and tradeable [[Share (finance)|shares]] which potentially entitle their holders to continual receipts based on the DAC’s success, to the point where the profit mechanism and the consensus mechanism are not the same thing.<ref name=vitalik-buterin3 /> According to Stan Larimer, President of Invictus Innovations, Inc. (a developer of DACs), an open source DAC with its state information kept public has these characteristics:
* They are '''corporations''' – they are free and independent persons (but don’t have [[legal personality]]).
* They are '''autonomous''' – once up to speed, they no longer need (or heed) their creators.
* They are '''distributed''' – there are no central points of control or failure that can be attacked.
* They are '''transparent''' – their books and business rules are auditable by all.
* They are '''confidential''' – customer information is securely (and incorruptibly) protected.
* They are '''trustworthy''' – because no interaction with them depends on trust.
* They are '''fiduciaries''' – acting solely in their customers’ and shareholders’ interests.
* They are '''self-regulating''' – they robotically obey their own rules.
* They are '''incorruptible''' – no one can exercise seductive or coercive influence over them.
* They are '''sovereign''' – over their digital resources (but don't have [[Capacity (law)|legal capacity]]).<ref name=stan-larimer1>Larimer, Stan. [http://letstalkbitcoin.com/bitcoin-and-the-three-laws-of-robotics/#.UpKv78Ssi-2 "Bitcoin and the Three Laws of Robotics"]. ''Let's Talk Bitcoin''. Retrieved 2 July 2014.</ref>

An example of a currently running DAC is the [[Nu Network]] (based on the open source [[Peershares]] template), which manages the world's first stable digital currency [[NuBits]].{{citation needed|date=November 2015}}

===== Criticism of terminology =====
Some of those interested in new models for building successful and massively scalable applications reject the term, arguing that the classification reintroduces legacy hierarchy-based structures with their regulatory and compliance issues, unnecessarily burdening those involved in their development. For example, in their white paper ''The Emerging Wave of Decentralized Applications'', David Johnston, et al., argue that the term "Distributed Autonomous Corporations" shouldn't be used:<ref name=david-johnston1 />

<blockquote class="templatequote">
It is worth while to note that the authors of this paper agree with many of the concepts proposed by the Invictus authors and the spirit and ethics they [uphold] we embrace wholeheartedly. The point on which we disagree is one of property terminology, “Distributed” and “Autonomous” are great terms, we don’t believe “Corporation” in particular is a desirable term for these entities. One of our primary reservations with using the term is, “Corporation” carries a lot of historical and legal baggage that won’t necessarily best serve the community of developers and entrepreneurs seeking to describe and build these new projects. If you Google the definition of “Corporation” the result is: “a company or group of people authorized to act as a single entity (legally a person) and recognized as such in law.”
</blockquote>

== Economic theory ==

In this economic theory, the role of the [[Business|firm]] is played by the DAO, and the role of the [[Entrepreneurial economics|entrepreneur]] is played by the programmers who develop the DAO.

=== Firm ===

In its typical implementation as publicly auditable rules distributed across the computers of the stakeholders, the DAO can be thought of in a [[Neoclassical economics|neoclassical]] sense as a [[production function]] or [[Production–possibility frontier|production possibilities set]], a black box that transforms inputs into outputs. The DAO can be modeled as a single actor, facing a series of mathematical calculations, implicit in the non-self-verifying data, determined by the characteristics of the production function. The reason that the DAO can exist is because market coordination without it fails due to lack of necessary intersubjective points of orientation, that is, lack of so-called [[Focal point (game theory)|Schelling points]]. The emergence of behavior-coordinating Schelling points is a characteristic of the way that the DAO is coded.<ref name=h-malmgren1>Malmgren, H. B. (1961). "Information, Expectations and the Theory of the Firm". ''Quarterly Journal of Economics'' '''75''': 399-421.</ref>

=== Entrepreneur ===

The entrepreneurship of the DAO's development process can be thought of in a [[Joseph Schumpeter|Schumpeterian]] sense as an exceptional occurrence of massive importance. The programmers who develop and launch the DAO are persons who by introducing "new combinations" shake the economy out of its previous equilibrium, starting a process Schumpeter termed [[creative destruction]].<ref name=marcus-becker1>Becker, Marcus C.; Thorbjørn Knudsen (2003). "The Entrepreneur at a Crucial Juncture in Schumpeter’s Work: Schumpeter’s 1928 Handbook Entry Entrepreneur". ''Advances in Austrian Economics'' '''6''': 199–234.</ref> This speaks to the tenuous relationship between the developers and the DAO they own or contract with, because Schumpeterian entrepreneurship is ''[[sui generis]]'' (independent of its environment).<ref name=nicolai-foss1>Foss NJ, Klein PG. ''Organizing Entrepreneurial Judgment: A New Approach to the Firm''. Cambridge University Press. (2012). ISBN 9780521874427</ref><ref>Foss NJ, Klein PG. Authors Forum:''Organizing Entrepreneurial Judgment: A New Approach to the Firm''. 2012 Austrian Scholars Conference, recorded 8 March 2012 at the Ludwig von Mises Institute in Auburn, Alabama. [https://www.youtube.com/watch?v=a0rJtEBjTA4]</ref>

== Legal issues ==

DAOs currently have no way to indemnify users since they lack [[legal personality]] and may have either no cash-flow or no assets. Accordingly, recovery in the event that a given DAO fails could turn out to be extremely difficult in practice. Consequently, if for example, a DAO does have funds, they may be able to indemnify specific users (namely exchanges) through corporate insurance (a [[Bond (finance)|bond]]).<ref name=swanson1>{{cite web|last1=Swanson|first1=Tim|title=Mitigating the Legal Risks of Issuing Securities on a Cryptoledger|url=http://cointelegraph.com/news/112034/mitigating-the-legal-risks-of-issuing-securities-on-a-cryptoledger|website=Cointelegraph|publisher=Cointelegraph|accessdate=11 July 2014}}</ref>
According to Austin Brister, a Houston-based attorney:
<blockquote class="templatequote">Consumer protection laws can be far-reaching and quite unforgiving. Ordinary businesses do just fine in navigating these laws, even if they don't realize it, because they can adjust their interactions with consumers in "real-time" in order to be reasonable, well-centered, and act in good faith in dealing with consumers. However, the problem with smart contracts, decentralized autonomous organizations, and the like, is that they are hard-wired to act in one way, whether it makes sense or not.

Unforeseeable circumstances practically always present themselves to businesses of all types, and by definition, these circumstances cannot be foreseen or planned for. These systems need to adequately plan for this possibility, and be prepared to be properly insured or adequately bonded in the event things go wrong, and customers are hurt. Similarly, consumers should be aware that they are not dealing with living breathing people, but rather a machine subject only to 0's and 1's.<ref name="swanson1"/>
</blockquote>

== Key architectural principles ==

* '''The [[Black swan theory|Black Swan]] principle''': Because of the impossibility of calculating the risks of consequential rare events and predicting their occurrence, an implementation must be based on ''nonpredictive'' decision-making under uncertainty, with more upside than downside from random events.
* '''The Chessmaster principle''': In general, an implementation must treat people like pawns in a [[chess]] game, patiently moving them into places that often seem harmless or pointless, and getting them to do all the heavy computational lifting. The best implementations will have layers of misdirection and backup plans in case some [[Hacker (computer security)|hacker]] attempts to defraud them, for instance, causing the attacker to do some work for them in the attempt.
* '''[[Finagle's Law]]''': In general, an implementation of a DAO must assume that if there are two or more ways to do something, and one of those ways can result in a catastrophe for the DAO, then someone will choose it. The best implementations rely on low trust protocols and [[behavior-shaping constraint]]s to protect themselves. (Being merely narrow AI, they cannot make nuanced trust judgments and are potentially easy to scam.)

== Layers in the DAO protocol suite ==

The DAO protocol suite uses [[Encapsulation (networking)|encapsulation]] to provide abstraction of protocols and services. Encapsulation is usually aligned with the division of the protocol suite into layers of general functionality. Viewing layers as providing or consuming a service is a method of [[Abstraction (computer science)|abstraction]] to isolate Services Layer protocols from the details of generating addresses, for example, while the Memory Layer avoids having to know the details of each and every market interaction and its protocol.{{citation needed|date=February 2015}}

[[File:Layers in the DAC protocol suite.svg|thumb|This is a diagram of the layers in the protocol suite for a Decentralized Autonomous Organization (DAO).]]

=== Internetworking layer ===

This layer provides a market-wide system of interconnected [[computer network]]s (the [[internet]]). This layer supports the peer-to-peer communications infrastructure that allows the DAO to be distributed and the other layers to interact.{{citation needed|date=February 2015}}

=== Economic layer ===

Technologies like [[Bitcoin]] have enabled this layer, which has the responsibility of maintaining a balance in some [[Cryptocurrency|cryptographic money]], and sending and receiving transactions. It handles non-self-verifying time data so that a transaction cannot spend money before that money was received and cannot spend money that has already been spent. Technologies like [[Mastercoin]] or [[Ripple (monetary system)|Ripple]] provide the [[Distributed computing|distributed]], [[peer-to-peer]] [[payment system]]. This layer depends on the Internetworking layer.{{citation needed|date=February 2015}}

This layer is composed of Type I and Type II decentralized applications, the payment systems being based on the cryptographic money systems with their existing blockchains, having independent protocols and tokens of their own.<ref name=david-johnston1 />

=== Memory layer ===

This layer maintains persistent [[State (computer science)|state information]] about the DAO. Generally, a [[Bitcoin protocol|blockchain]] is used to keep state information public. State information is kept private by using [[secure multiparty computation]] with the inputs split up using an algorithm called [[Shamir's Secret Sharing]]. This allows the DAO to decentrally self-validate some of its own computation, correctly sign transactions, and generate addresses. This layer depends on the Internetworking layer.{{citation needed|date=February 2015}}

=== Data gathering layer ===

This layer handles non-self-verifying data about the real world:
# '''Demand'''. Data about what people want.
# '''Supply'''. Data about what resources are available to obtain what people want.

This layer provides some kind of resource-democracy mechanism to vote on the correct value of some fact, and ensure that humans are incentivized to provide accurate estimates by depriving everyone whose report does not match the “mainstream view” of the monetary reward. This layer depends on the economic layer and the memory layer.{{citation needed|date=February 2015}}

=== Self-modification layer ===

This layer handles allowing humans to modify the DAO so as to future-proof it, e.g. changing APIs and source code. This layer allows DACs to improve themselves by purchasing the services of humans via bilateral hostage contracts, for instance.<ref name=oleg-andreev1>Andreev, Oleg. [http://blog.oleganza.com/post/58240549599/contracts-without-trust-or-third-parties "Contracts without trust or third parties"]. ''Personal Blog''. Retrieved 2 July 2014.</ref> This layer also allows the DAO to set an upper bound on the losses caused by any malicious collusion.<ref>DeFigueiredo, Dimitri do B. [http://dimitrietal.com/trustdavis.pdf "TrustDavis: A Non-Exploitable Online Reputation System"]. Department of Computer Science, University of California at Davis. Retrieved 2 July 2014.</ref> [[A/B testing]] can be used to determine if the delivered work is really better than the old one or not, and only releasing the payment if the results of the test are positive. Alternatively, a quorum of [[Dispute resolution organization|dispute mediators]] can be specified, and they decide if the contract was met or not. This layer depends on the Economic layer and the Memory layer.

=== Output layer ===

This layer interacts with the world using multiparty-signed API requests in a decentralized way. This may include APIs that allow for renting server capacity and then remotely controlling that server, for example, or the ability to post human-readable contracts to [[freelancer]] forums or the [[Amazon Mechanical Turk|Mechanical Turk]]. DACs can expose their services to humans (or other DACs) by selecting a name and then registering it with [[Namecoin]]. Using DNS hierarchies and Namecoin together allows interested parties to monitor for new agents coming online: the act of registering a name under a particular part of the tree automatically advertises its existence. This layer depends on the Economic layer, the Memory layer, and the Data Gathering layer.

This layer is composed of Type III Decentralized Applications, having their own independent protocols and tokens.<ref name=david-johnston1 />

=== Services layer ===

This layer runs the artificial intelligence algorithm that the DAO relies on to detect patterns in real-world data and model it without human intervention. This allows the DAO to create sell-able value fast enough to keep up with its own resource demands in the marketplace of humans. This layer depends on the Economic layer, the Memory layer and the Data Gathering layer.{{citation needed|date=February 2015}}

== Hiring employees ==

Making a fine-grained evaluation of an individual human employee is likely impossible. The best solution is likely to simply use monetary incentives to direct people’s actions on a coarse level, and then let the community self-organize to make the fine-grained adjustments. The extent to which a DAO targets a community for investment and participation, rather than discrete individuals, is the choice of its original developers.<ref>{{cite AV media
| year=2014
| title=Engineering Economic Security
| medium=YouTube
| url=https://www.youtube.com/watch?v=4CFlA8TdWmk&feature=youtu.be
| accessdate=August 11, 2014
| location=Silicon Valley Ethereum Meetup
| publisher=EtherCasts
}}</ref> On the one hand, targeting a community can allow your human support to work together to solve problems in large groups. On the other hand, keeping everyone separate prevents collusion, and in that way reduces the likelihood of a hostile takeover.<ref name=vitalik-buterin1>Buterin, Vitalik. [http://bitcoinmagazine.com/7119/bootstrapping-an-autonomous-decentralized-corporation-part-2-interacting-with-the-world/ "Bootstrapping An Autonomous Decentralized Corporation, Part 2: Interacting With the World"]. ''Bitcoin Magazine™''. Coin Publishing Ltd. Retrieved 22 November 2013.</ref>

== Hostile takeovers ==

A hostile takeover of a DAO handling money means that the attacker gains the ability to drain the DAO’s entire wallet. Countering hostile takeovers requires certain economic measures to establish consensus:
* '''[[Proof of work]]''' is used to deter denial of service attacks by requiring some work from the service requester that is moderately hard (but feasible) on the requester side but easy to check for the service provider. This is commonly referred to as "mining".<ref name=david-johnston1 />
* '''Proof of stake''' is used to deter other service abuses such as a [[Sybil attack]].

Another counter-measure might simply be to allow the decentralized corporation to have shareholders, so that shareholders get some kind of special voting privileges, along with the right to a share of the profits, in exchange for investing. (Shareholders benefit if the price goes up, so shareholders are encouraged to do things that increase the price.) This would incentivize the shareholders to protect their investment.

=== Sybil attacks ===
{{see also | Sybil attack}}
A hostile takeover could be accomplished by a successful Sybil attack, say through a [[botnet]], overwhelming the resource-democracy mechanism by controlling over half of the servers in the network.

Requiring each participating node to show proof that it controls some moderately large amount of crypto-currency would prevent this kind of attack. Then implementing a hostile takeover would require more resources than all of the legitimate nodes committed together. The moderately large amount of crypto-currency could even be moved to a multisignature address partially controlled by the network as a [[surety bond]], both discouraging nodes from cheating and giving their owners a great incentive to act and even get together to keep the corporation alive.

== Examples ==

=== Applications ===

There are three major categories of industries where DACs will be able to survive on their own merits and provide genuine value to society: ''natural monopolies'', ''illegal entities'', and ''entities of extremely low profitability''.

{{example farm|section|date=July 2014}}

==== Natural monopolies ====

A [[natural monopoly]] is a monopoly in an industry in which it is most efficient (involving the lowest long-run average cost) for production to be concentrated in a single firm: [[Communications protocol|software protocols]], [[Programming language|languages]] and to some extent [[Social networking service|social networks]] and [[currencies]]. A DAO can theoretically be designed so that no one involved in the price-setting mechanism has an incentive to fix prices over market rates. More generally, they can be made invulnerable to corruption in ways unimaginable in human-controlled system, although great care would certainly need to be taken not to introduce other vulnerabilities instead.<ref name=vitalik-buterin1 />
* Identity Corp, a corporation whose sole purpose is to create cryptographically secure identity documents for individuals that they could sign messages with, and are linked to individuals’ physical identities.<ref name=vitalik-buterin2>Buterin, Vitalik. [http://bitcoinmagazine.com/7235/bootstrapping-a-decentralized-autonomous-corporation-part-3-identity-corp/ "Bootstrapping a Decentralized Autonomous Corporation, Part 3: Identity Corp"]. ''Bitcoin Magazine™''. Coin Publishing Ltd. Retrieved 23 November 2013.</ref>

==== Illegal entities ====

Because of a combination of the DAO's incorruptible nature and the explosive growth in [[Rulemaking|regulations]], services that violate government laws and regulations are unavoidable. But their decentralized nature makes it extremely difficult to prevent them from taking over illegal markets. As Satoshi Nakamoto said, "Governments are good at cutting off the heads of a centrally controlled networks like Napster, but pure P2P networks like Gnutella and Tor seem to be holding their own".<ref>[https://bitcointalk.org/index.php?topic=26878.15%3Bwap2 "The root of the problem!"].</ref>
* Decentralized file-sharing networks for copyright infringement
* A captcha-cracker, that requires CPU. People pay for the Captchas to be cracked and the DAO provides some kind of API for people to offer their CPU and hosting of the software, if they do so, they get bitcoins. Putting this up online, with some marketing, the software should survive on its own as long as there are captchas that needs to be cracked.

==== Not-For-Profit Entities ====

Finally, there are those cases where a decentralized network can simply maintain itself more efficiently and provides better services than any centralized alternative.
* BitShares - a DAC industry with the purpose of providing infrastructure and software for other DACs. Currently available DACs within BitShares ecosystem:
** BitSharesX - a family of DACs that implement the business model of a bank and exchange.
* Colored Coins are working on defining themselves as a DAO
* Crop insurance
* Mitosys - a DAC replacement for Bit-Message
* Social network - Monetizable Diaspora
* StorJ, a simple drop-box style file service with pay per use via bitcoin (and perhaps with naming provided via namecoin and/or tor hidden services).<ref name=jeff-garzik1>Garzik, Jeff. [http://garzikrants.blogspot.ch/2013/01/storj-and-bitcoin-autonomous-agents.html "StorJ, and Bitcoin autonomous agents"]. ''Random blatherings by Jeff''. Blogger. Retrieved 22 November 2013.</ref> StorJ isn't smart enough to judge bad proposals on its own — instead it forms agreements that make it unprofitable to cheat.
* The peer-to-peer network used by [[Blizzard]] to distribute updates to its massively multiplayer online game [[World of Warcraft]]
* Weather network
* [[Bitcoin protocol|Bitcoin]] itself and all of Bitcoin forks/Altcurrencies
* [http://garzikrants.blogspot.com/2014/01/blackbox-bitcoin-enabled-decentralized.html blackbox] is a Bitcoin-enabled, decentralized cloud that uses TradeNet
* [https://github.com/wetube/wetube-web Wetube]

=== Examples in literature ===

* In Daniel Suarez's [[techno-thriller]], ''[[Daemon (book series)|Daemon]]'', a collection of sophisticated computer programs have been left sitting passive on machines scattered around the Internet until one of them reads the programmer's obituary, which sends triggers to other systems which activate a number of other distributed processes, awakening the DAO.

== See also ==

* [[Bitcoin protocol]]
* [[Decentralized computing]]
* [[Incentive-centered design]]
* [[Merkle tree]]
* [[Monero (cryptocurrency)|Monero]]
* [[Serious game]]

== References ==
{{Reflist|2}}

== External links ==
{{External links|section|date=December 2015}}
{{refbegin|2}}
* [http://aeon.co/magazine/technology/are-we-ready-for-companies-that-run-themselves/ RoboCorp - Get ready for companies that run themselves. But will the autonomous economy set us all free, or just make the rich richer?], David Z. Morris, ''[[Aeon (digital magazine)]]''
* [http://www.npr.org/blogs/parallels/2015/02/01/382648685/in-sweden-remote-control-airport-is-a-reality In Sweden, Remote-Control Airport Is A Reality], Ari Shapiro, ''[[National Public Radio (United States)|National Public Radio]]''
* [http://bitcoin.org/bitcoin.pdf Bitcoin: A Peer-to-Peer Electronic Cash System] bitcoin.org
* [http://bitcoinmagazine.com/7050/bootstrapping-a-decentralized-autonomous-corporation-part-i/ Bootstrapping a DAC Part 1] Bitcoin Magazine
* [http://bitsharestalk.org/index.php?topic=297.0 Topic on bitsharestalk] bitsharestalk.org
* [http://ethereum.org/ethereum.html Ethereum]: A Next-Generation Generalized Smart Contract and Decentralized Application Platform
* [http://wiki.ethereum.org/index.php/Dagger Dagger] is a proof of work algorithm, intended to provide a memory-hard proof of work based on moderately connected directed acyclic graphs. wiki.ethereum.org
* [http://wiki.ethereum.org/index.php/Patricia_Tree Patricia Tree] wiki.ethereum.org
* [https://blog.ethereum.org/2014/05/06/daos-dacs-das-and-more-an-incomplete-terminology-guide/ DAOs, DACs, DAs and More: An Incomplete Terminology Guide] blog.ethereum.org
* [http://garzikrants.blogspot.ca/2013/01/storj-and-bitcoin-autonomous-agents.html StorJ, and Bitcoin autonomous agents] garzikrants.blogspot
* [http://letstalkbitcoin.com/bitcoin-and-the-three-laws-of-robotics/ Bitcoin and the Three Laws of Robotics] letstalkbitcoin.com
* [http://letstalkbitcoin.com/dac-revisited/ DAC Revisited] letstalkbitcoin.com
* [http://letstalkbitcoin.com/dacs-that-spawn-dacs/ DACs That Spawn DACs?] letstalkbitcoin.com
* [http://letstalkbitcoin.com/is-bitcoin-overpaying-for-false-security/ The Hidden Costs of Bitcoin] letstalkbitcoin.com
* [http://tvtropes.org/pmwiki/pmwiki.php/Literature/Daemon TV Tropes Analysis of Daemon] tvtropes.org
* [http://wavism.net/group3/distributed-autonomous-virtual-state-davs/ Distributed Autonomous Virtual State] wavism.net
* [http://www.amazon.com/Great-Chain-Numbers-Contracts-Management-ebook/dp/B00IRUBMXO Great Chain of Numbers: A Guide to Smart Contracts, Smart Property and Trustless Asset Management] amazon.com
* [http://www.cs.huji.ac.il/~avivz/pubs/13/btc_scalability_full.pdf Accelerating Bitcoin's Transaction Processing] Fast Money Grows on Trees, Not Chains, cs.huji.ac.il
* [http://www.youtube.com/watch?v=Pu4PAMFPo5Y Mike Hearn's talk on autonomous agents, Turing Festival 2013] YouTube
* [https://docs.google.com/document/d/1AnkP_cVZTCMLIzw4DvsW6M8Q2JC0lIzrTLuoWu2z1BE/edit#heading=h.v3px1rgmf10o Colored Coins]
* [https://en.bitcoin.it/wiki/Agents Bitcoin-using autonomous agents] Bitcoin wiki
* [https://en.bitcoin.it/wiki/Contracts Contracts] Bitcoin wiki
* [https://en.bitcoin.it/wiki/List_of_Decentralized_Autonomous_Corporations List of Decentralized Autonomous Corporations] Bitcoin wiki
* [https://en.bitcoin.it/wiki/Scalability#Simplified_payment_verification Simplified payment verification] Bitcoin wiki
* [https://en.bitcoin.it/wiki/Smart_Property Smart Property] Bitcoin wiki
* [https://en.wikibooks.org/wiki/Seed_Factories/WWF Distributed Production Network] wikibooks.org
* [https://github.com/mastercoin-MSC/spec The Master Protocol - Mastercoin Complete Specification] github.com
{{refend}}

{{DEFAULTSORT:Distributed Computing}}
[[Category:Anarcho-capitalism]]
[[Category:Application layer protocols]]
[[Category:Applications of cryptography]]
[[Category:Computer law]]
[[Category:Computer networking]]
[[Category:Crypto-anarchism]]
[[Category:Cryptography]]
[[Category:Distributed computing]]
[[Category:Distributed data storage]]
[[Category:E-commerce]]
[[Category:Network protocols]]
[[Category:Payment systems]]
[[Category:Peer-to-peer computing]]
[[Category:Production economics]]
[[Category:Cryptocurrencies]]

Call to Action (Marketing)

2016-01-18T08:49:11Z

Intgr: rv nonsense. Undid revision 699979777 by 82.70.219.54 (talk)

{{About-distinguish|the marketing term|Call to Action}}
{{multiple issues|
{{Refimprove|date=January 2012}}
{{third-party|date=January 2012}}
}}

{{marketing}}

In marketing, a '''call to action''' (CTA) is an instruction to the audience to provoke an immediate response, usually using an [[imperative verb]] such as "call now", "find out more" or "visit a store today".<ref>{{cite web|url=http://homebusiness.about.com/od/homebusinessglossar1/g/Call-To-Action-Definition.htm|title=Call To Action|author=Mindy Lilyquist|work=About.com Money|accessdate=12 January 2016}}</ref>

A CTA can be a simple non-demanding request like "choose a colour" or "watch this video", or a much more demanding request. An obvious CTA would be requesting the audience to purchase a product or provide personal details and contact information.

Clever marketing strategies often combine a series of small CTAs. These smaller CTAs create a pattern of behaviour that makes it easy for the audience to follow-through with just one last CTA, completing a more demanding request, had it been asked without context. An example could be the purchase of a designer torch. The website might request you choose a style, then a colour, a size and even a personalised engraving. When you get to see your personalised one-of-a-kind product, you are more likely to feel inclined to buy it as it rotates in full 3D rendered colour on your computer monitor or tablet.

==On websites==
In web design, a CTA is a [[web banner|banner]], button, or some type of graphic or text on a website meant to prompt a user to [[Click analytics|click]] it and continue down a [[conversion funnel]]. It is an essential part of [[inbound marketing]] as well as [[permission marketing]] in that it actively strives to convert a user into a lead and later into a customer. The main goal of a CTA is a click, or a scan in the case of a [[qr code]], and its success can be measured via a conversion rate formula that calculates the number of clicks over the times the CTA was seen. Another way to test the effectiveness of a CTA is using [[A/B testing]] where several graphics are presented to users and the graphic with highest success rate becomes the default.

[[File:Cta.PNG|thumb|Example of a website CTA]]

== References ==

{{Reflist}}

[[Category:Marketing]]
[[Category:Market research]]
[[Category:Internet marketing terminology]]
[[Category:Marketing terminology]]
[[Category:Internet marketing]]
[[Category:Internet terminology]]
[[Category:Types of marketing]]

Dezentralisierte Autonome Organisation

2015-12-15T17:33:05Z

Intgr: Tag with too many links, Delete some spam links including Eris Industries

{{refimprove|date=February 2015}}
A '''decentralized autonomous organization''' (DAO), '''fully automated business entity''' (FAB), or '''distributed autonomous corporation/company''' (DAC) is a decentralized network of narrow-AI [[autonomous agent]]s which perform an output-maximizing production function and which divides its labor into computationally intractable tasks (which it incentivizes humans to do) and tasks which it performs itself.<ref name=dave-talk>Babbitt, Dave. "Crypto-Economic Design: A Proposed Agent-Based Modeling Effort." SwarmFest 2014: 18th Annual Meeting on Agent-Based Modeling & Simulation, University of Notre Dame, McKenna Hall Auditorium, Notre Dame, IN USA, June 29 - July 1, 2014. Ed. Greg Madey & Ryan McCune. Tuesday 3:00 PM Address. Retrieved from http://www3.nd.edu/~swarm06/SwarmFest2014/Crypto-economicDesignBabbit.pdf</ref><ref name=dave-thesis>{{ cite thesis | chapter=4.4 | author=Dave Babbitt | docket= | year=2014 | degree=Master's | publisher=Northwestern University | title=Agent-Based Modeling of Peer-to-Peer Economic Systems | oclc= | url= | accessdate= | location=Evanston, IL }}</ref> It can be thought of as a corporation run without any human involvement under the control of an incorruptible set of business rules. These rules are typically implemented as publicly auditable open-source software distributed across the computers of their stakeholders. A human becomes a stakeholder by buying stock in the company or being paid in that stock to provide services for the company. This stock may entitle its owner to a share of the profits of the DAO, participation in its growth, and/or a say in how it is run.<ref name=david-johnston1>[https://github.com/DavidJohnstonCEO/DecentralizedApplications#the-emerging-wave-of-decentralized-applications "The Emerging Wave of Decentralized Applications"]. GitHub. Retrieved 2 July 2014.</ref>

== Terminology ==

=== Autonomous agents ===
In an autonomous agent, there is no necessary specific human involvement outside of some degree of the human effort necessary to build the hardware that the agent runs on. Outside of that, there is no need for any humans to exist that are aware of the agent’s existence. One example of an autonomous agent that already exists today would be a computer virus; the virus survives by replicating itself from machine to machine without deliberate human action.<ref name=vitalik-buterin3>{{cite web|author1=Vitalik Buterin|url=https://blog.ethereum.org/2014/05/06/daos-dacs-das-and-more-an-incomplete-terminology-guide/|website=etherum blog|accessdate=13 August 2014|date=May 6, 2014|title=DAOs, DACs, DAs and More: An Incomplete Terminology Guide}}</ref>

=== Decentralized applications (Dapps) ===
A [[smart contract]] is the simplest form of decentralized automation. It is a mechanism involving [[digital assets]] and two or more parties, where some or all of the parties put assets in and assets are automatically redistributed among those parties according to a formula based on certain data that is not known at the time the contract is initiated. A decentralized application is similar to a smart contract, but different in two key ways. First of all, a decentralized application has an unbounded number of participants on all sides of the market. Second, a decentralized application need not be necessarily financial. [[BitTorrent]] qualifies as a decentralized application, as do [[Popcorn Time]], [[Tor (anonymity network)|Tor]], [[Maidsafe]] and [[Crypti]] (note that Maidsafe and Crypti are also platforms for other decentralized applications).<ref name=vitalik-buterin3 />

=== Decentralized organizations (DOs) ===
A human organization can be defined as a combination of two things: a set of [[property]], and a [[Communications protocol|protocol]] for a [[Set (abstract data type)|set]] of individuals (which may or may not be divided into certain classes with different conditions for entering or leaving the set) to interact with each other, including rules for under what circumstances the individuals may use certain parts of the property.

The idea of a decentralized organization takes the same concept of an organization, and decentralizes it. Instead of a hierarchical structure managed by a set of humans interacting in person and controlling property via the [[legal system]], a decentralized organization involves a set of humans interacting with each other according to a protocol specified in code, and enforced on the [[Block chain (transaction database)|blockchain]].<ref name=vitalik-buterin3 /> The earliest prototype software to link up such a protocol to a blockchain was the Eris 0.1 prototype in June of 2014.<ref>{{Cite web|title = Eris - The Dawn of Distributed Autonomous Organizations and The Future of Governance - h+ Media|url = http://hplusmagazine.com/2014/06/17/eris-the-dawn-of-distributed-autonomous-organizations-and-the-future-of-governance/|website = h+ Media|accessdate = 2015-11-02}}</ref>

=== Decentralized autonomous organizations (DAOs) ===
[[File:Quadrant Chart for Classifying DAOs.png|thumb|400px|Vitalik Buterin's Quadrant Chart for Classifying DAOs]]
The main difference between a DO and a DAO is that a DAO has internal capital; that is, a DAO contains some kind of internal property that is valuable in some way, and it has the ability to use that property as a mechanism for rewarding certain activities. [[BitTorrent]] has no internal property, and [[Maidsafe]]-like systems have reputation but that reputation is not a saleable asset. [[Bitcoin]] and [[Namecoin]], on the other hand, do. However, plain old DOs also have internal capital, as do autonomous agents.

DOs and DAOs are both vulnerable to collusion attacks, where a significant percentage of a certain type of members collude to specifically direct its activity. However, in a DAO collusion attacks are treated as a bug, whereas in a DO they are a feature (such as [[majority vote]] in a [[democracy]]).

An AI is completely autonomous, whereas a DAO still requires heavy involvement from humans specifically interacting according to a protocol defined by the DAO in order to operate.<ref name=vitalik-buterin3 />

==== Decentralized autonomous corporations/companies ====
DACs are basically a subclass of DAOs that pays [[dividend]]s on purchaseable and tradeable [[Share (finance)|shares]] which potentially entitle their holders to continual receipts based on the DAC’s success, to the point where the profit mechanism and the consensus mechanism are not the same thing.<ref name=vitalik-buterin3 /> According to Stan Larimer, President of Invictus Innovations, Inc. (a developer of DACs), an open source DAC with its state information kept public has these characteristics:
* They are '''corporations''' – they are free and independent persons (but don’t have [[legal personality]]).
* They are '''autonomous''' – once up to speed, they no longer need (or heed) their creators.
* They are '''distributed''' – there are no central points of control or failure that can be attacked.
* They are '''transparent''' – their books and business rules are auditable by all.
* They are '''confidential''' – customer information is securely (and incorruptibly) protected.
* They are '''trustworthy''' – because no interaction with them depends on trust.
* They are '''fiduciaries''' – acting solely in their customers’ and shareholders’ interests.
* They are '''self-regulating''' – they robotically obey their own rules.
* They are '''incorruptible''' – no one can exercise seductive or coercive influence over them.
* They are '''sovereign''' – over their digital resources (but don't have [[Capacity (law)|legal capacity]]).<ref name=stan-larimer1>Larimer, Stan. [http://letstalkbitcoin.com/bitcoin-and-the-three-laws-of-robotics/#.UpKv78Ssi-2 "Bitcoin and the Three Laws of Robotics"]. ''Let's Talk Bitcoin''. Retrieved 2 July 2014.</ref>

An example of a currently running DAC is the [[Nu Network]] (based of the open source [[Peershares]] template), which manages the world's first stable digital currency [[NuBits]].{{citation needed|date=November 2015}}

===== Criticism of terminology =====
Some of those interested in new models for building successful and massively scalable applications reject the term, arguing that the classification reintroduces legacy hierarchy-based structures with their regulatory and compliance issues, unnecessarily burdening those involved in their development. For example, in their white paper ''The Emerging Wave of Decentralized Applications'', David Johnston, et al., argue that the term "Distributed Autonomous Corporations" shouldn't be used:<ref name=david-johnston1 />

<blockquote class="templatequote">
It is worth while to note that the authors of this paper agree with many of the concepts proposed by the Invictus authors and the spirit and ethics they [uphold] we embrace wholeheartedly. The point on which we disagree is one of property terminology, “Distributed” and “Autonomous” are great terms, we don’t believe “Corporation” in particular is a desirable term for these entities. One of our primary reservations with using the term is, “Corporation” carries a lot of historical and legal baggage that won’t necessarily best serve the community of developers and entrepreneurs seeking to describe and build these new projects. If you Google the definition of “Corporation” the result is: “a company or group of people authorized to act as a single entity (legally a person) and recognized as such in law.”
</blockquote>

== Economic theory ==

In this economic theory, the role of the [[Business|firm]] is played by the DAO, and the role of the [[Entrepreneurial economics|entrepreneur]] is played by the programmers who develop the DAO.

=== Firm ===

In its typical implementation as publicly auditable rules distributed across the computers of the stakeholders, the DAO can be thought of in a [[Neoclassical economics|neoclassical]] sense as a [[production function]] or [[Production–possibility frontier|production possibilities set]], a black box that transforms inputs into outputs. The DAO can be modeled as a single actor, facing a series of mathematical calculations, implicit in the non-self-verifying data, determined by the characteristics of the production function. The reason that the DAO can exist is because market coordination without it fails due to lack of necessary intersubjective points of orientation, that is, lack of so-called [[Focal point (game theory)|Schelling points]]. The emergence of behavior-coordinating Schelling points is a characteristic of the way that the DAO is coded.<ref name=h-malmgren1>Malmgren, H. B. (1961). "Information, Expectations and the Theory of the Firm". ''Quarterly Journal of Economics'' '''75''': 399-421.</ref>

=== Entrepreneur ===

The entrepreneurship of the DAO's development process can be thought of in a [[Joseph Schumpeter|Schumpeterian]] sense as an exceptional occurrence of massive importance. The programmers who develop and launch the DAO are persons who by introducing "new combinations" shake the economy out of its previous equilibrium, starting a process Schumpeter termed [[creative destruction]].<ref name=marcus-becker1>Becker, Marcus C.; Thorbjørn Knudsen (2003). "The Entrepreneur at a Crucial Juncture in Schumpeter’s Work: Schumpeter’s 1928 Handbook Entry Entrepreneur". ''Advances in Austrian Economics'' '''6''': 199–234.</ref> This speaks to the tenuous relationship between the developers and the DAO they own or contract with, because Schumpeterian entrepreneurship is ''[[sui generis]]'' (independent of its environment).<ref name=nicolai-foss1>Foss NJ, Klein PG. ''Organizing Entrepreneurial Judgment: A New Approach to the Firm''. Cambridge University Press. (2012). ISBN 9780521874427</ref><ref>Foss NJ, Klein PG. Authors Forum:''Organizing Entrepreneurial Judgment: A New Approach to the Firm''. 2012 Austrian Scholars Conference, recorded 8 March 2012 at the Ludwig von Mises Institute in Auburn, Alabama. [https://www.youtube.com/watch?v=a0rJtEBjTA4]</ref>

== Legal issues ==

DAOs currently have no way to indemnify users since they lack [[legal personality]] and may have either no cash-flow or no assets. Accordingly, recovery in the event that a given DAO fails could turn out to be extremely difficult in practice. Consequently if for example, a DAO does have funds, they may be able to indemnify specific users (namely exchanges) through corporate insurance (a [[Bond (finance)|bond]]).<ref name=swanson1>{{cite web|last1=Swanson|first1=Tim|title=Mitigating the Legal Risks of Issuing Securities on a Cryptoledger|url=http://cointelegraph.com/news/112034/mitigating-the-legal-risks-of-issuing-securities-on-a-cryptoledger|website=Cointelegraph|publisher=Cointelegraph|accessdate=11 July 2014}}</ref>
According to Austin Brister, a Houston-based attorney:
<blockquote class="templatequote">Consumer protection laws can be far-reaching and quite unforgiving. Ordinary businesses do just fine in navigating these laws, even if they don't realize it, because they can adjust their interactions with consumers in "real-time" in order to be reasonable, well-centered, and act in good faith in dealing with consumers. However, the problem with smart contracts, decentralized autonomous organizations, and the like, is that they are hard-wired to act in one way, whether it makes sense or not.

Unforeseeable circumstances practically always present themselves to businesses of all types, and by definition, these circumstances cannot be foreseen or planned for. These systems need to adequately plan for this possibility, and be prepared to be properly insured or adequately bonded in the event things go wrong, and customers are hurt. Similarly, consumers should be aware that they are not dealing with living breathing people, but rather a machine subject only to 0's and 1's.<ref name="swanson1"/>
</blockquote>

== Key architectural principles ==

* '''The [[Black swan theory|Black Swan]] principle''': Because of the impossibility of calculating the risks of consequential rare events and predicting their occurrence, an implementation must be based on ''nonpredictive'' decision-making under uncertainty, with more upside than downside from random events.
* '''The Chessmaster principle''': In general, an implementation must treat people like pawns in a [[chess]] game, patiently moving them into places that often seem harmless or pointless, and getting them to do all the heavy computational lifting. The best implementations will have layers of misdirection and backup plans in case some [[Hacker (computer security)|hacker]] attempts to defraud them, for instance, causing the attacker to do some work for them in the attempt.
* '''[[Finagle's Law]]''': In general, an implementation of a DAO must assume that if there are two or more ways to do something, and one of those ways can result in a catastrophe for the DAO, then someone will choose it. The best implementations rely on low trust protocols and [[behavior-shaping constraint]]s to protect themselves. (Being merely narrow AI, they cannot make nuanced trust judgments and are potentially easy to scam.)

== Layers in the DAO protocol suite ==

The DAO protocol suite uses [[Encapsulation (networking)|encapsulation]] to provide abstraction of protocols and services. Encapsulation is usually aligned with the division of the protocol suite into layers of general functionality. Viewing layers as providing or consuming a service is a method of [[Abstraction (computer science)|abstraction]] to isolate Services Layer protocols from the details of generating addresses, for example, while the Memory Layer avoids having to know the details of each and every market interaction and its protocol.{{citation needed|date=February 2015}}

[[File:Layers in the DAC protocol suite.svg|thumb|This is a diagram of the layers in the protocol suite for a Decentralized Autonomous Organization (DAO).]]

=== Internetworking layer ===

This layer provides a market-wide system of interconnected [[computer network]]s (the [[internet]]). This layer supports the peer-to-peer communications infrastructure that allows the DAO to be distributed and the other layers to interact.{{citation needed|date=February 2015}}

=== Economic layer ===

Technologies like [[Bitcoin]] have enabled this layer, which has the responsibility of maintaining a balance in some [[Cryptocurrency|cryptographic money]], and sending and receiving transactions. It handles non-self-verifying time data so that a transaction cannot spend money before that money was received and cannot spend money that has already been spent. Technologies like [[Mastercoin]] or [[Ripple (monetary system)|Ripple]] provide the [[Distributed computing|distributed]], [[peer-to-peer]] [[payment system]]. This layer depends on the Internetworking layer.{{citation needed|date=February 2015}}

This layer is composed of Type I and Type II decentralized applications, the payment systems being based on the cryptographic money systems with their existing blockchains, having independent protocols and tokens of their own.<ref name=david-johnston1 />

=== Memory layer ===

This layer maintains persistent [[State (computer science)|state information]] about the DAO. Generally, a [[Bitcoin protocol|blockchain]] is used to keep state information public. State information is kept private by using [[secure multiparty computation]] with the inputs split up using an algorithm called [[Shamir's Secret Sharing]]. This allows the DAO to decentrally self-validate some of its own computation, correctly sign transactions, and generate addresses. This layer depends on the Internetworking layer.{{citation needed|date=February 2015}}

=== Data gathering layer ===

This layer handles non-self-verifying data about the real world:
# '''Demand'''. Data about what people want.
# '''Supply'''. Data about what resources are available to obtain what people want.

This layer provides some kind of resource-democracy mechanism to vote on the correct value of some fact, and ensure that humans are incentivized to provide accurate estimates by depriving everyone whose report does not match the “mainstream view” of the monetary reward. This layer depends on the economic layer and the memory layer.{{citation needed|date=February 2015}}

=== Self-modification layer ===

This layer handles allowing humans to modify the DAO so as to future-proof it, e.g. changing APIs and source code. This layer allows DACs to improve themselves by purchasing the services of humans via bilateral hostage contracts, for instance.<ref name=oleg-andreev1>Andreev, Oleg. [http://blog.oleganza.com/post/58240549599/contracts-without-trust-or-third-parties "Contracts without trust or third parties"]. ''Personal Blog''. Retrieved 2 July 2014.</ref> This layer also allows the DAO to set an upper bound on the losses caused by any malicious collusion.<ref>DeFigueiredo, Dimitri do B. [http://dimitrietal.com/trustdavis.pdf "TrustDavis: A Non-Exploitable Online Reputation System"]. Department of Computer Science, University of California at Davis. Retrieved 2 July 2014.</ref> [[A/B testing]] can be used to determine if the delivered work is really better than the old one or not, and only releasing the payment if the results of the test are positive. Alternatively, a quorum of [[Dispute resolution organization|dispute mediators]] can be specified, and they decide if the contract was met or not. This layer depends on the Economic layer and the Memory layer.

=== Output layer ===

This layer interacts with the world using multiparty-signed API requests in a decentralized way. This may include APIs that allow for renting server capacity and then remotely controlling that server, for example, or the ability to post human-readable contracts to [[freelancer]] forums or the [[Amazon Mechanical Turk|Mechanical Turk]]. DACs can expose their services to humans (or other DACs) by selecting a name and then registering it with [[Namecoin]]. Using DNS hierarchies and Namecoin together allows interested parties to monitor for new agents coming online: the act of registering a name under a particular part of the tree automatically advertises its existence. This layer depends on the Economic layer, the Memory layer, and the Data Gathering layer.

This layer is composed of Type III Decentralized Applications, having their own independent protocols and tokens.<ref name=david-johnston1 />

=== Services layer ===

This layer runs the artificial intelligence algorithm that the DAO relies on to detect patterns in real-world data and model it without human intervention. This allows the DAO to create sell-able value fast enough to keep up with its own resource demands in the marketplace of humans. This layer depends on the Economic layer, the Memory layer and the Data Gathering layer.{{citation needed|date=February 2015}}

== Hiring employees ==

Making a fine-grained evaluation of an individual human employee is likely impossible. The best solution is likely to simply use monetary incentives to direct people’s actions on a coarse level, and then let the community self-organize to make the fine-grained adjustments. The extent to which a DAO targets a community for investment and participation, rather than discrete individuals, is the choice of its original developers.<ref>{{cite AV media
| year=2014
| title=Engineering Economic Security
| medium=YouTube
| url=https://www.youtube.com/watch?v=4CFlA8TdWmk&feature=youtu.be
| accessdate=August 11, 2014
| location=Silicon Valley Ethereum Meetup
| publisher=EtherCasts
}}</ref> On the one hand, targeting a community can allow your human support to work together to solve problems in large groups. On the other hand, keeping everyone separate prevents collusion, and in that way reduces the likelihood of a hostile takeover.<ref name=vitalik-buterin1>Buterin, Vitalik. [http://bitcoinmagazine.com/7119/bootstrapping-an-autonomous-decentralized-corporation-part-2-interacting-with-the-world/ "Bootstrapping An Autonomous Decentralized Corporation, Part 2: Interacting With the World"]. ''Bitcoin Magazine™''. Coin Publishing Ltd. Retrieved 22 November 2013.</ref>

== Hostile takeovers ==

A hostile takeover of a DAO handling money means that the attacker gains the ability to drain the DAO’s entire wallet. Countering hostile takeovers requires certain economic measures to establish consensus:
* '''[[Proof of work]]''' is used to deter denial of service attacks by requiring some work from the service requester that is moderately hard (but feasible) on the requester side but easy to check for the service provider. This is commonly referred to as "mining".<ref name=david-johnston1 />
* '''Proof of stake''' is used to deter other service abuses such as a [[Sybil attack]].

Another counter-measure might simply be to allow the decentralized corporation to have shareholders, so that shareholders get some kind of special voting privileges, along with the right to a share of the profits, in exchange for investing. (Shareholders benefit if the price goes up, so shareholders are encouraged to do things that increase the price.) This would incentivize the shareholders to protect their investment.

=== Sybil attacks ===
{{see also | Sybil attack}}
A hostile takeover could be accomplished by a successful Sybil attack, say through a [[botnet]], overwhelming the resource-democracy mechanism by controlling over half of the servers in the network.

Requiring each participating node to show proof that it controls some moderately large amount of crypto-currency would prevent this kind of attack. Then implementing a hostile takeover would require more resources than all of the legitimate nodes committed together. The moderately large amount of crypto-currency could even be moved to a multisignature address partially controlled by the network as a [[surety bond]], both discouraging nodes from cheating and giving their owners a great incentive to act and even get together to keep the corporation alive.

== Examples ==

=== Applications ===

There are three major categories of industries where DACs will be able to survive on their own merits and provide genuine value to society: ''natural monopolies'', ''illegal entities'', and ''entities of extremely low profitability''.

{{example farm|section|date=July 2014}}

==== Natural monopolies ====

A [[natural monopoly]] is a monopoly in an industry in which it is most efficient (involving the lowest long-run average cost) for production to be concentrated in a single firm: [[Communications protocol|software protocols]], [[Programming language|languages]] and to some extent [[Social networking service|social networks]] and [[currencies]]. A DAO can theoretically be designed so that no one involved in the price-setting mechanism has an incentive to fix prices over market rates. More generally, they can be made invulnerable to corruption in ways unimaginable in human-controlled system, although great care would certainly need to be taken not to introduce other vulnerabilities instead.<ref name=vitalik-buterin1 />
* Identity Corp, a corporation whose sole purpose is to create cryptographically secure identity documents for individuals that they could sign messages with, and are linked to individuals’ physical identities.<ref name=vitalik-buterin2>Buterin, Vitalik. [http://bitcoinmagazine.com/7235/bootstrapping-a-decentralized-autonomous-corporation-part-3-identity-corp/ "Bootstrapping a Decentralized Autonomous Corporation, Part 3: Identity Corp"]. ''Bitcoin Magazine™''. Coin Publishing Ltd. Retrieved 23 November 2013.</ref>

==== Illegal entities ====

Because of a combination of the DAO's incorruptible nature and the explosive growth in [[Rulemaking|regulations]], services that violate government laws and regulations are unavoidable. But their decentralized nature makes it extremely difficult to prevent them from taking over illegal markets. As Satoshi Nakamoto said, "Governments are good at cutting off the heads of a centrally controlled networks like Napster, but pure P2P networks like Gnutella and Tor seem to be holding their own".<ref>[https://bitcointalk.org/index.php?topic=26878.15%3Bwap2 "The root of the problem!"].</ref>
* Decentralized file-sharing networks for copyright infringement
* A captcha-cracker, that requires CPU. People pay for the Captchas to be cracked and the DAO provides some kind of API for people to offer their CPU and hosting of the software, if they do so, they get bitcoins. Putting this up online, with some marketing, the software should survive on its own as long as there are captchas that needs to be cracked.

==== Not-For-Profit Entities ====

Finally, there are those cases where a decentralized network can simply maintain itself more efficiently and provides better services than any centralized alternative.
* BitShares - a DAC industry with the purpose of providing infrastructure and software for other DACs. Currently available DACs within BitShares ecosystem:
** BitSharesX - a family of DACs that implement the business model of a bank and exchange.
* Colored Coins are working on defining themselves as a DAO
* Crop insurance
* Mitosys - a DAC replacement for Bit-Message
* Social network - Monetizable Diaspora
* StorJ, a simple drop-box style file service with pay per use via bitcoin (and perhaps with naming provided via namecoin and/or tor hidden services).<ref name=jeff-garzik1>Garzik, Jeff. [http://garzikrants.blogspot.ch/2013/01/storj-and-bitcoin-autonomous-agents.html "StorJ, and Bitcoin autonomous agents"]. ''Random blatherings by Jeff''. Blogger. Retrieved 22 November 2013.</ref> StorJ isn't smart enough to judge bad proposals on its own — instead it forms agreements that make it unprofitable to cheat.
* The peer-to-peer network used by [[Blizzard]] to distribute updates to its massively multiplayer online game [[World of Warcraft]]
* Weather network
* [[Bitcoin protocol|Bitcoin]] itself and all of Bitcoin forks/Altcurrencies
* [http://garzikrants.blogspot.com/2014/01/blackbox-bitcoin-enabled-decentralized.html blackbox] is a Bitcoin-enabled, decentralized cloud that uses TradeNet
* [https://github.com/wetube/wetube-web Wetube]

=== Examples in literature ===

* In Daniel Suarez's [[techno-thriller]], ''[[Daemon (book series)|Daemon]]'', a collection of sophisticated computer programs have been left sitting passive on machines scattered around the Internet until one of them reads the programmer's obituary, which sends triggers to other systems which activate a number of other distributed processes, awakening the DAO.

== See also ==

* [[Bitcoin protocol]]
* [[Decentralized computing]]
* [[Incentive-centered design]]
* [[Merkle tree]]
* [[Monero (cryptocurrency)|Monero]]
* [[Serious game]]

== References ==
{{Reflist|2}}

== External links ==
{{Too many links|section|date=December 2015}}
{{refbegin|2}}
* [http://aeon.co/magazine/technology/are-we-ready-for-companies-that-run-themselves/ RoboCorp - Get ready for companies that run themselves. But will the autonomous economy set us all free, or just make the rich richer?], David Z. Morris, ''[[Aeon (digital magazine)]]''
* [http://www.npr.org/blogs/parallels/2015/02/01/382648685/in-sweden-remote-control-airport-is-a-reality In Sweden, Remote-Control Airport Is A Reality], Ari Shapiro, ''[[National Public Radio (United States)|National Public Radio]]''
* [http://bitcoin.org/bitcoin.pdf Bitcoin: A Peer-to-Peer Electronic Cash System] bitcoin.org
* [http://bitcoinmagazine.com/7050/bootstrapping-a-decentralized-autonomous-corporation-part-i/ Bootstrapping a DAC Part 1] Bitcoin Magazine
* [http://bitsharestalk.org/index.php?topic=297.0 Topic on bitsharestalk] bitsharestalk.org
* [http://ethereum.org/ethereum.html Ethereum]: A Next-Generation Generalized Smart Contract and Decentralized Application Platform
* [http://wiki.ethereum.org/index.php/Dagger Dagger] is a proof of work algorithm, intended to provide a memory-hard proof of work based on moderately connected directed acyclic graphs. wiki.ethereum.org
* [http://wiki.ethereum.org/index.php/Patricia_Tree Patricia Tree] wiki.ethereum.org
* [https://blog.ethereum.org/2014/05/06/daos-dacs-das-and-more-an-incomplete-terminology-guide/ DAOs, DACs, DAs and More: An Incomplete Terminology Guide] blog.ethereum.org
* [http://garzikrants.blogspot.ca/2013/01/storj-and-bitcoin-autonomous-agents.html StorJ, and Bitcoin autonomous agents] garzikrants.blogspot
* [http://letstalkbitcoin.com/bitcoin-and-the-three-laws-of-robotics/ Bitcoin and the Three Laws of Robotics] letstalkbitcoin.com
* [http://letstalkbitcoin.com/dac-revisited/ DAC Revisited] letstalkbitcoin.com
* [http://letstalkbitcoin.com/dacs-that-spawn-dacs/ DACs That Spawn DACs?] letstalkbitcoin.com
* [http://letstalkbitcoin.com/is-bitcoin-overpaying-for-false-security/ The Hidden Costs of Bitcoin] letstalkbitcoin.com
* [http://tvtropes.org/pmwiki/pmwiki.php/Literature/Daemon TV Tropes Analysis of Daemon] tvtropes.org
* [http://wavism.net/group3/distributed-autonomous-virtual-state-davs/ Distributed Autonomous Virtual State] wavism.net
* [http://www.amazon.com/Great-Chain-Numbers-Contracts-Management-ebook/dp/B00IRUBMXO Great Chain of Numbers: A Guide to Smart Contracts, Smart Property and Trustless Asset Management] amazon.com
* [http://www.cs.huji.ac.il/~avivz/pubs/13/btc_scalability_full.pdf Accelerating Bitcoin's Transaction Processing] Fast Money Grows on Trees, Not Chains, cs.huji.ac.il
* [http://www.youtube.com/watch?v=Pu4PAMFPo5Y Mike Hearn's talk on autonomous agents, Turing Festival 2013] YouTube
* [https://docs.google.com/document/d/1AnkP_cVZTCMLIzw4DvsW6M8Q2JC0lIzrTLuoWu2z1BE/edit#heading=h.v3px1rgmf10o Colored Coins]
* [https://en.bitcoin.it/wiki/Agents Bitcoin-using autonomous agents] Bitcoin wiki
* [https://en.bitcoin.it/wiki/Contracts Contracts] Bitcoin wiki
* [https://en.bitcoin.it/wiki/List_of_Decentralized_Autonomous_Corporations List of Decentralized Autonomous Corporations] Bitcoin wiki
* [https://en.bitcoin.it/wiki/Scalability#Simplified_payment_verification Simplified payment verification] Bitcoin wiki
* [https://en.bitcoin.it/wiki/Smart_Property Smart Property] Bitcoin wiki
* [https://en.wikibooks.org/wiki/Seed_Factories/WWF Distributed Production Network] wikibooks.org
* [https://github.com/mastercoin-MSC/spec The Master Protocol - Mastercoin Complete Specification] github.com
{{refend}}

{{DEFAULTSORT:Distributed Computing}}
[[Category:Anarcho-capitalism]]
[[Category:Application layer protocols]]
[[Category:Applications of cryptography]]
[[Category:Computer law]]
[[Category:Computer networking]]
[[Category:Crypto-anarchism]]
[[Category:Cryptography]]
[[Category:Distributed computing]]
[[Category:Distributed data storage]]
[[Category:E-commerce]]
[[Category:Network protocols]]
[[Category:Payment systems]]
[[Category:Peer-to-peer computing]]
[[Category:Production economics]]
[[Category:Cryptocurrencies]]

Zen (Mikroarchitektur)

2015-12-03T13:55:41Z

Intgr: Puncation around maint tags

{{Infobox CPU
| name = Zen
| image =
| image_size = 138px
| caption =
| produced-start = 2016+
| produced-end =
| designfirm = [[AMD]]
| manuf1 = [[Advanced Micro Devices|AMD]]
| size-from = 14 nm ([[FinFET]])<ref name="WCCF Zen">{{cite web|last=Moammer |first=Khalid |url=http://wccftech.com/breaking-amds-gen-x86-high-performance-core-code-named-zen-debut-k12/ |title=AMD's Next Gen x86 High Performance Core is Zen |publisher=WCCF Tech | date=September 9, 2014 |accessdate=January 15, 2015}}</ref>
| predecessor = [[Excavator (microarchitecture)|Excavator Family 15h (4th-gen)]]
| successor =
| arch = [[X86-64#AMD64|AMD64]] ([[x86-64]])
| sock1 = [[Socket AM4]]<ref name="Ryan Smith">{{cite web |url=http://www.anandtech.com/show/9231/amds-20162017-x86-roadmap-zen-is-in|title=AMD’s 2016-2017 x86 Roadmap: Zen Is In, Skybridge Is Out |author=Ryan Smith |date={{date|2015-05-06}} |publisher=[[AnandTech]] }}</ref>
| application = Desktop, Laptop, Server
| core1 =
| TDP =
}}

'''Zen''' is an upcoming [[CPU]] microarchitecture created by [[AMD]],<ref name="AMD hints at high-performance Zen">{{cite news|url=http://www.bit-tech.net/news/hardware/2014/09/11/amd-zen/1 | publisher=bit-tech | title=AMD hints at high-performance Zen x86 architecture | date=11 September 2014 | accessdate=15 December 2014}}</ref> expected for release in October 2016.<ref name="zenoct2016">{{cite news|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-set-to-release-first-zen-based-microprocessors-in-late-2016-document | website=KitGuru.net | title=AMD set to release first ‘Zen’-based microprocessors in late 2016 – document | date=12 June 2015 | accessdate=30 August 2015}}</ref>

==Architecture==
According to [[AMD]], Zen's main focus will be on increasing per-core performance rather than core count or multi-threading performance.<ref name="techspot">{{cite web|url=http://www.techspot.com/news/60626-tech-reading-amd-zen-comeback.html|title=Weekend tech reading: AMD 'Zen' and their return to high-end CPUs, tracking Windows pirates - TechSpot|publisher=techspot.com|accessdate=2015-05-12}}</ref><ref name="techreport">{{cite web|url=http://techreport.com/review/28228/amd-zen-chips-headed-to-desktops-servers-in-2016|title=AMD: Zen chips headed to desktops, servers in 2016 - The Tech Report - Page 1|publisher=techreport.com|accessdate=2015-05-12}}</ref><ref name="kitguru">{{cite news|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/ | work=KitGuru | title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be | date=11 September 2014 |author=Anton Shilov | accessdate=1 February 2015}}</ref> Reports from AMD indicate that Zen will abandon modular [[Bulldozer (microarchitecture)#CMT|CMT]] (Clustered Multithread) for a [[Simultaneous multithreading|SMT]] (Simultaneous Multithreading) microarchitecture,<ref name="WCCF Zen" /><ref>{{cite web|title=AMD 2015 comeback attempt: reforming high-performance processor, abandon modular architecture.|url=http://www.expreview.com/33161.html|publisher=Extreme Performance Review|accessdate=10 May 2015}}</ref> which is the same model that Intel uses, as well as what AMD has used in past architectures.{{Which?|date=November 2015}} Adapting their chips from the less-popular CMT to SMT<ref name="Ryan Smith"/> is expected to offer much higher number threading efficiency, but also possibly increase the die size of a Zen module.<ref name="kitguru" />

Reportedly, the Zen architecture will be built on a more efficient [[14 nanometer]] process, rather than the 32 nm and 28 nm processes of previous [[AMD FX]] CPUs and [[AMD Accelerated Processing Unit|AMD APUs]], respectively.<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading"/> The "Summit Ridge" Zen family will also feature a unified AM4 socket with its GPU-equipped "Raven Ridge" APU counterparts,<ref name="pcgamer">{{cite web|url=http://www.pcgamer.com/amds-next-gen-zen-cpu-due-in-2016/|title=AMD's next-gen Zen CPU due in 2016 - PC Gamer|publisher=pcgamer.com|accessdate=2015-05-12}}</ref> and feature [[DDR4 SDRAM|DDR4]] support and a 95W [[Thermal design power|TDP]].<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading">{{cite news|url=http://news.softpedia.com/news/14nm-AMD-Zen-CPU-Will-Have-DDR4-and-Simultaneous-Multithreading-471401.shtml | publisher=Softpedia | title=14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading | date=28 January 2015 | accessdate=31 January 2015}}</ref> Zen does not support DDR3;{{Citation needed|date=November 2015}} only 7th generation AMD APUs (also fitting the AMD AM4 unified socket) support DDR3 and DDR4. While newer roadmaps don't confirm the TDP for desktop products, they suggest a range for low-power mobile products with up to two Zen cores from 5 to 15W and 15 to 35W for performance-oriented mobile products with up to four Zen cores.<ref name="Shattered Media article">{{cite news| url=http://www.shattered.media/amds-next-gen-cpu-zen/ | publisher=Shattered.Media | title=AMD's next gen CPU Zen |date=May 2015}}</ref>

Zen will support [[RDSEED]].<ref name="AMD Starts Linux Enablement">{{cite news|url=http://www.phoronix.com/scan.php?page=news_item&px=AMD-Zen-CPU-Znver1 | publisher=Phoronix | title=AMD Starts Linux Enablement On Next-Gen "Zen" Architecture | date=17 March 2015 | accessdate=17 March 2015}}</ref>{{explain|date=October 2015}}

Zen core will have four integer units, two address generation units and four floating point units, and the decoder can decode four instructions per clock cycle.
L1 cache size is 32 kiB and L2 cache size 512 kiB per core. Two of the floating point units are adders, two are multipliers.<ref name="dresdenboy">{{cite web|title=AMD's Zen core (family 17h) to have ten pipelines per core|url=http://dresdenboy.blogspot.fi/2015/10/amds-zen-core-family-17h-to-have-ten.html}}</ref>{{Unreliable source?|certain=y|date=October 2015}}

{{quote box|align=right|width=35em|quote="It is the first time in a very long time that we engineers have been given the total freedom to build a processor from scratch and do the best we can do. It is a multi-year project with a really large team. It's like a marathon effort with some sprints in the middle. The team is working very hard, but they can see the finish line. I guarantee that it will deliver a huge improvement in performance and (low) power consumption over the previous generation."|source=—Suzanne Plummer, Zen team leader, on September 19th, 2015.<ref>http://www.mystatesman.com/news/business/amid-challenges-chipmnaker-amd-sees-a-way-forward/nngdf/</ref>}}

==History==
AMD began planning the Zen microarchitecture shortly after re-hiring [[Jim Keller (engineer)|Jim Keller]] in early 2012.<ref>{{cite av media|url=https://www.youtube.com/watch?v=SOTFE7sJY-Q|title=Jim Keller On AMD's Next-Gen High Performance x86 Zen Core & K12 ARM Core|date=7 May 2014|work=YouTube}}</ref>

The team in charge of the Zen microarchitecture was led by Keller until he left in September 2015 after a 3-year tenure.<ref name="anandtech">{{cite web|url=http://anandtech.com/show/9643/jim-keller-leaves-amd|title=Jim Keller Leaves AMD|publisher=anandtech.com|accessdate=2015-10-14}}</ref>

Zen was originally planned for 2017 following the ARM64-based [[AMD K12|K12]] sister core, but on AMD's 2015 Financial Analyst Day it was revealed that K12 was delayed in favour of the Zen design, to allow it to enter the market within the 2016 timeframe,<ref name="Ryan Smith" /> with the release of first Zen-based processors expected for October 2016.<ref name="zenoct2016"/>

As of November 2015, AMD reported that its Zen microprocessors had been tested and "met all expectations" with "no significant bottlenecks found".<ref>http://www.overclock3d.net/articles/cpu_mainboard/amd_tests_zen_cpus_met_all_expectation_with_no_significant_bottlenecks_found/1</ref><ref>http://www.extremetech.com/computing/217664-globalfoundries-announces-14nm-validation-with-amd-silicon</ref>

==See also==
{{Portal|Computing}}

* [[Bulldozer (microarchitecture)]]
* [[Steamroller (microarchitecture)]]
* [[AMD K12]]

==References==
{{Reflist|40em}}

{{AMD processors|state=collapsed}}

[[Category:Advanced Micro Devices x86 microprocessors]]
[[Category:Advanced Micro Devices microarchitectures]]
[[Category:Upcoming integrated circuits]]

{{Comp-hardware-stub}}

Zen (Mikroarchitektur)

2015-11-30T10:07:47Z

Intgr: The source doesn't say anything about "3D transistors" or "bulk silicon"

{{Infobox CPU
| name = Zen
| image =
| image_size = 138px
| caption =
| produced-start = 2016+
| produced-end =
| designfirm = [[AMD]]
| manuf1 = [[Advanced Micro Devices|AMD]]
| size-from = 14 nm ([[FinFET]])<ref name="WCCF Zen">{{cite web|last=Moammer |first=Khalid |url=http://wccftech.com/breaking-amds-gen-x86-high-performance-core-code-named-zen-debut-k12/ |title=AMD's Next Gen x86 High Performance Core is Zen |publisher=WCCF Tech | date=September 9, 2014 |accessdate=January 15, 2015}}</ref>
| predecessor = [[Excavator (microarchitecture)|Excavator Family 15h (4th-gen)]]
| successor =
| arch = [[X86-64#AMD64|AMD64]] ([[x86-64]])
| sock1 = [[Socket AM4]]<ref name="Ryan Smith">{{cite web |url=http://www.anandtech.com/show/9231/amds-20162017-x86-roadmap-zen-is-in|title=AMD’s 2016-2017 x86 Roadmap: Zen Is In, Skybridge Is Out |author=Ryan Smith |date={{date|2015-05-06}} |publisher=[[AnandTech]] }}</ref>
| application = Desktop, Laptop, Server
| core1 =
| TDP =
}}

'''Zen''' is an upcoming [[CPU]] microarchitecture created by [[AMD]],<ref name="AMD hints at high-performance Zen">{{cite news|url=http://www.bit-tech.net/news/hardware/2014/09/11/amd-zen/1 | publisher=bit-tech | title=AMD hints at high-performance Zen x86 architecture | date=11 September 2014 | accessdate=15 December 2014}}</ref> expected for release in October 2016.<ref name="zenoct2016">{{cite news|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-set-to-release-first-zen-based-microprocessors-in-late-2016-document | website=KitGuru.net | title=AMD set to release first ‘Zen’-based microprocessors in late 2016 – document | date=12 June 2015 | accessdate=30 August 2015}}</ref>

==Architecture==
According to [[AMD]], Zen's main focus will be on increasing per-core performance rather than core count or multi-threading performance.<ref name="techspot">{{cite web|url=http://www.techspot.com/news/60626-tech-reading-amd-zen-comeback.html|title=Weekend tech reading: AMD 'Zen' and their return to high-end CPUs, tracking Windows pirates - TechSpot|publisher=techspot.com|accessdate=2015-05-12}}</ref><ref name="techreport">{{cite web|url=http://techreport.com/review/28228/amd-zen-chips-headed-to-desktops-servers-in-2016|title=AMD: Zen chips headed to desktops, servers in 2016 - The Tech Report - Page 1|publisher=techreport.com|accessdate=2015-05-12}}</ref><ref name="kitguru">{{cite news|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/ | work=KitGuru | title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be | date=11 September 2014 |author=Anton Shilov | accessdate=1 February 2015}}</ref> Reports from AMD indicate that Zen will abandon modular [[Bulldozer (microarchitecture)#CMT|CMT]] (Clustered Multithread) for a [[Simultaneous multithreading|SMT]] (Simultaneous Multithreading) microarchitecture,<ref name="WCCF Zen" /><ref>{{cite web|title=AMD 2015 comeback attempt: reforming high-performance processor, abandon modular architecture.|url=http://www.expreview.com/33161.html|publisher=Extreme Performance Review|accessdate=10 May 2015}}</ref> which is the same model that Intel uses, as well as what AMD has used in past architectures. Adapting their chips from the less-popular CMT to SMT<ref name="Ryan Smith"/> is expected to offer much higher number threading efficiency, but also possibly increase the die size of a Zen module.<ref name="kitguru" />

Reportedly, the Zen architecture will be built on a more efficient [[14 nanometer]] process, rather than the 32 nm and 28 nm processes of previous [[AMD FX]] CPUs and [[AMD Accelerated Processing Unit|AMD APUs]], respectively.<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading"/> The "Summit Ridge" Zen family will also feature a unified AM4 socket with its GPU-equipped "Raven Ridge" APU counterparts,<ref name="pcgamer">{{cite web|url=http://www.pcgamer.com/amds-next-gen-zen-cpu-due-in-2016/|title=AMD's next-gen Zen CPU due in 2016 - PC Gamer|publisher=pcgamer.com|accessdate=2015-05-12}}</ref> and feature [[DDR4 SDRAM|DDR4]] support and a 95W [[Thermal design power|TDP]].<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading">{{cite news|url=http://news.softpedia.com/news/14nm-AMD-Zen-CPU-Will-Have-DDR4-and-Simultaneous-Multithreading-471401.shtml | publisher=Softpedia | title=14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading | date=28 January 2015 | accessdate=31 January 2015}}</ref> Zen does not support DDR3;{{Citation needed|date=November 2015}} only 7th generation AMD APUs (also fitting the AMD AM4 unified socket) support DDR3 and DDR4. While newer roadmaps don't confirm the TDP for desktop products, they suggest a range for low-power mobile products with up to two Zen cores from 5 to 15W and 15 to 35W for performance-oriented mobile products with up to four Zen cores.<ref name="Shattered Media article">{{cite news| url=http://www.shattered.media/amds-next-gen-cpu-zen/ | publisher=Shattered.Media | title=AMD's next gen CPU Zen |date=May 2015}}</ref>

Zen will support [[RDSEED]].<ref name="AMD Starts Linux Enablement">{{cite news|url=http://www.phoronix.com/scan.php?page=news_item&px=AMD-Zen-CPU-Znver1 | publisher=Phoronix | title=AMD Starts Linux Enablement On Next-Gen "Zen" Architecture | date=17 March 2015 | accessdate=17 March 2015}}</ref>{{explain|date=October 2015}}

Zen core will have four integer units, two address generation units and four floating point units, and the decoder can decode four instructions per clock cycle.
L1 cache size is 32 kiB and L2 cache size 512 kiB per core. Two of the floating point units are adders, two are multipliers.<ref name="dresdenboy">{{cite web|title=AMD's Zen core (family 17h) to have ten pipelines per core|url=http://dresdenboy.blogspot.fi/2015/10/amds-zen-core-family-17h-to-have-ten.html}}</ref>{{Unreliable source?|certain=y|date=October 2015}}

{{quote box|align=right|width=35em|quote="It is the first time in a very long time that we engineers have been given the total freedom to build a processor from scratch and do the best we can do. It is a multi-year project with a really large team. It's like a marathon effort with some sprints in the middle. The team is working very hard, but they can see the finish line. I guarantee that it will deliver a huge improvement in performance and (low) power consumption over the previous generation."|source=—Suzanne Plummer, Zen team leader, on September 19th, 2015.<ref>http://www.mystatesman.com/news/business/amid-challenges-chipmnaker-amd-sees-a-way-forward/nngdf/</ref>}}

==History==
AMD began planning the Zen microarchitecture shortly after re-hiring [[Jim Keller (engineer)|Jim Keller]] in early 2012.<ref>{{cite av media|url=https://www.youtube.com/watch?v=SOTFE7sJY-Q|title=Jim Keller On AMD's Next-Gen High Performance x86 Zen Core & K12 ARM Core|date=7 May 2014|work=YouTube}}</ref>

The team in charge of the Zen microarchitecture was led by Keller until he left in September 2015 after a 3-year tenure.<ref name="anandtech">{{cite web|url=http://anandtech.com/show/9643/jim-keller-leaves-amd|title=Jim Keller Leaves AMD|publisher=anandtech.com|accessdate=2015-10-14}}</ref>

Zen was originally planned for 2017 following the ARM64-based [[AMD K12|K12]] sister core, but on AMD's 2015 Financial Analyst Day it was revealed that K12 was delayed in favour of the Zen design, to allow it to enter the market within the 2016 timeframe,<ref name="Ryan Smith" /> with the release of first Zen-based processors expected for October 2016.<ref name="zenoct2016"/>

As of November 2015, AMD reported that its Zen microprocessors had been tested and "met all expectations" with "no significant bottlenecks found".<ref>http://www.overclock3d.net/articles/cpu_mainboard/amd_tests_zen_cpus_met_all_expectation_with_no_significant_bottlenecks_found/1</ref><ref>http://www.extremetech.com/computing/217664-globalfoundries-announces-14nm-validation-with-amd-silicon</ref>

==See also==
{{Portal|Computing}}

* [[Bulldozer (microarchitecture)]]
* [[Steamroller (microarchitecture)]]
* [[AMD K12]]

==References==
{{Reflist|40em}}

{{AMD processors|state=collapsed}}

[[Category:Advanced Micro Devices x86 microprocessors]]
[[Category:Advanced Micro Devices microarchitectures]]
[[Category:Upcoming integrated circuits]]

{{Comp-hardware-stub}}

Zen (Mikroarchitektur)

2015-11-30T10:05:27Z

Intgr: The sources don't say anything about delays or "being on time"

{{Infobox CPU
| name = Zen
| image =
| image_size = 138px
| caption =
| produced-start = 2016+
| produced-end =
| designfirm = [[AMD]]
| manuf1 = [[Advanced Micro Devices|AMD]]
| size-from = 14 nm ([[Multigate device#FinFET|Bulk Silicon]])3D transistors(FinFET)<ref name="WCCF Zen">{{cite web|last=Moammer |first=Khalid |url=http://wccftech.com/breaking-amds-gen-x86-high-performance-core-code-named-zen-debut-k12/ |title=AMD's Next Gen x86 High Performance Core is Zen |publisher=WCCF Tech | date=September 9, 2014 |accessdate=January 15, 2015}}</ref>
| predecessor = [[Excavator (microarchitecture)|Excavator Family 15h (4th-gen)]]
| successor =
| arch = [[X86-64#AMD64|AMD64]] ([[x86-64]])
| sock1 = [[Socket AM4]]<ref name="Ryan Smith">{{cite web |url=http://www.anandtech.com/show/9231/amds-20162017-x86-roadmap-zen-is-in|title=AMD’s 2016-2017 x86 Roadmap: Zen Is In, Skybridge Is Out |author=Ryan Smith |date={{date|2015-05-06}} |publisher=[[AnandTech]] }}</ref>
| application = Desktop, Laptop, Server
| core1 =
| TDP =
}}

'''Zen''' is an upcoming [[CPU]] microarchitecture created by [[AMD]],<ref name="AMD hints at high-performance Zen">{{cite news|url=http://www.bit-tech.net/news/hardware/2014/09/11/amd-zen/1 | publisher=bit-tech | title=AMD hints at high-performance Zen x86 architecture | date=11 September 2014 | accessdate=15 December 2014}}</ref> expected for release in October 2016.<ref name="zenoct2016">{{cite news|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-set-to-release-first-zen-based-microprocessors-in-late-2016-document | website=KitGuru.net | title=AMD set to release first ‘Zen’-based microprocessors in late 2016 – document | date=12 June 2015 | accessdate=30 August 2015}}</ref>

==Architecture==
According to [[AMD]], Zen's main focus will be on increasing per-core performance rather than core count or multi-threading performance.<ref name="techspot">{{cite web|url=http://www.techspot.com/news/60626-tech-reading-amd-zen-comeback.html|title=Weekend tech reading: AMD 'Zen' and their return to high-end CPUs, tracking Windows pirates - TechSpot|publisher=techspot.com|accessdate=2015-05-12}}</ref><ref name="techreport">{{cite web|url=http://techreport.com/review/28228/amd-zen-chips-headed-to-desktops-servers-in-2016|title=AMD: Zen chips headed to desktops, servers in 2016 - The Tech Report - Page 1|publisher=techreport.com|accessdate=2015-05-12}}</ref><ref name="kitguru">{{cite news|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/ | work=KitGuru | title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be | date=11 September 2014 |author=Anton Shilov | accessdate=1 February 2015}}</ref> Reports from AMD indicate that Zen will abandon modular [[Bulldozer (microarchitecture)#CMT|CMT]] (Clustered Multithread) for a [[Simultaneous multithreading|SMT]] (Simultaneous Multithreading) microarchitecture,<ref name="WCCF Zen" /><ref>{{cite web|title=AMD 2015 comeback attempt: reforming high-performance processor, abandon modular architecture.|url=http://www.expreview.com/33161.html|publisher=Extreme Performance Review|accessdate=10 May 2015}}</ref> which is the same model that Intel uses, as well as what AMD has used in past architectures. Adapting their chips from the less-popular CMT to SMT<ref name="Ryan Smith"/> is expected to offer much higher number threading efficiency, but also possibly increase the die size of a Zen module.<ref name="kitguru" />

Reportedly, the Zen architecture will be built on a more efficient [[14 nanometer]] process, rather than the 32 nm and 28 nm processes of previous [[AMD FX]] CPUs and [[AMD Accelerated Processing Unit|AMD APUs]], respectively.<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading"/> The "Summit Ridge" Zen family will also feature a unified AM4 socket with its GPU-equipped "Raven Ridge" APU counterparts,<ref name="pcgamer">{{cite web|url=http://www.pcgamer.com/amds-next-gen-zen-cpu-due-in-2016/|title=AMD's next-gen Zen CPU due in 2016 - PC Gamer|publisher=pcgamer.com|accessdate=2015-05-12}}</ref> and feature [[DDR4 SDRAM|DDR4]] support and a 95W [[Thermal design power|TDP]].<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading">{{cite news|url=http://news.softpedia.com/news/14nm-AMD-Zen-CPU-Will-Have-DDR4-and-Simultaneous-Multithreading-471401.shtml | publisher=Softpedia | title=14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading | date=28 January 2015 | accessdate=31 January 2015}}</ref> Zen does not support DDR3;{{Citation needed|date=November 2015}} only 7th generation AMD APUs (also fitting the AMD AM4 unified socket) support DDR3 and DDR4. While newer roadmaps don't confirm the TDP for desktop products, they suggest a range for low-power mobile products with up to two Zen cores from 5 to 15W and 15 to 35W for performance-oriented mobile products with up to four Zen cores.<ref name="Shattered Media article">{{cite news| url=http://www.shattered.media/amds-next-gen-cpu-zen/ | publisher=Shattered.Media | title=AMD's next gen CPU Zen |date=May 2015}}</ref>

Zen will support [[RDSEED]].<ref name="AMD Starts Linux Enablement">{{cite news|url=http://www.phoronix.com/scan.php?page=news_item&px=AMD-Zen-CPU-Znver1 | publisher=Phoronix | title=AMD Starts Linux Enablement On Next-Gen "Zen" Architecture | date=17 March 2015 | accessdate=17 March 2015}}</ref>{{explain|date=October 2015}}

Zen core will have four integer units, two address generation units and four floating point units, and the decoder can decode four instructions per clock cycle.
L1 cache size is 32 kiB and L2 cache size 512 kiB per core. Two of the floating point units are adders, two are multipliers.<ref name="dresdenboy">{{cite web|title=AMD's Zen core (family 17h) to have ten pipelines per core|url=http://dresdenboy.blogspot.fi/2015/10/amds-zen-core-family-17h-to-have-ten.html}}</ref>{{Unreliable source?|certain=y|date=October 2015}}

{{quote box|align=right|width=35em|quote="It is the first time in a very long time that we engineers have been given the total freedom to build a processor from scratch and do the best we can do. It is a multi-year project with a really large team. It's like a marathon effort with some sprints in the middle. The team is working very hard, but they can see the finish line. I guarantee that it will deliver a huge improvement in performance and (low) power consumption over the previous generation."|source=—Suzanne Plummer, Zen team leader, on September 19th, 2015.<ref>http://www.mystatesman.com/news/business/amid-challenges-chipmnaker-amd-sees-a-way-forward/nngdf/</ref>}}

==History==
AMD began planning the Zen microarchitecture shortly after re-hiring [[Jim Keller (engineer)|Jim Keller]] in early 2012.<ref>{{cite av media|url=https://www.youtube.com/watch?v=SOTFE7sJY-Q|title=Jim Keller On AMD's Next-Gen High Performance x86 Zen Core & K12 ARM Core|date=7 May 2014|work=YouTube}}</ref>

The team in charge of the Zen microarchitecture was led by Keller until he left in September 2015 after a 3-year tenure.<ref name="anandtech">{{cite web|url=http://anandtech.com/show/9643/jim-keller-leaves-amd|title=Jim Keller Leaves AMD|publisher=anandtech.com|accessdate=2015-10-14}}</ref>

Zen was originally planned for 2017 following the ARM64-based [[AMD K12|K12]] sister core, but on AMD's 2015 Financial Analyst Day it was revealed that K12 was delayed in favour of the Zen design, to allow it to enter the market within the 2016 timeframe,<ref name="Ryan Smith" /> with the release of first Zen-based processors expected for October 2016.<ref name="zenoct2016"/>

As of November 2015, AMD reported that its Zen microprocessors had been tested and "met all expectations" with "no significant bottlenecks found".<ref>http://www.overclock3d.net/articles/cpu_mainboard/amd_tests_zen_cpus_met_all_expectation_with_no_significant_bottlenecks_found/1</ref><ref>http://www.extremetech.com/computing/217664-globalfoundries-announces-14nm-validation-with-amd-silicon</ref>

==See also==
{{Portal|Computing}}

* [[Bulldozer (microarchitecture)]]
* [[Steamroller (microarchitecture)]]
* [[AMD K12]]

==References==
{{Reflist|40em}}

{{AMD processors|state=collapsed}}

[[Category:Advanced Micro Devices x86 microprocessors]]
[[Category:Advanced Micro Devices microarchitectures]]
[[Category:Upcoming integrated circuits]]

{{Comp-hardware-stub}}

Kubernetes

2015-11-26T09:07:23Z

Intgr: Revert, external links within article text are discouraged, WP:EL. Undid revision 692503360 by Brendan.d.burns (talk)

{{Infobox software
| name = Kubernetes
| title = Kubernetes
| logo = [[File:Kubernetes_(container_engine).png|75px]]
| caption =
| developer =
| status = Active
| released = {{Start date|2014|06|07|df=yes}}<ref name="github first-commit">{{cite web|url=https://github.com/kubernetes/kubernetes/commit/2c4b3a562ce34cddc3f8218a2c4d11c7310e6d56 |title=First GitHub commit for Kubernetes |work=github.com | date=2014-06-07}}</ref>
| latest release version = 1.1.2<ref name="github releases">{{cite web|url=https://github.com/kubernetes/kubernetes/releases |title=GitHub Releases page |work=github.com | date=2015-11-25}}</ref>
| latest release date = {{release date|2015|10|27}}
| operating system = [[Cross-platform]]
| programming language = [[Go (programming language)|Go]]
| genre = [[Computer cluster#Cluster management|Cluster management software]]
| posix compliant =
| license = [[Apache License]] 2.0
| website = {{URL|kubernetes.io}}
}}

'''Kubernetes''' is an [[open source]] [[Container (virtualization)|container]] [[Computer cluster#Cluster management|cluster manager]] by [[Google]]. It aims to provide a "platform for automating deployment, scaling, and operations of application containers across clusters of hosts".<ref>{{cite web|title=What is Kubernetes|url=http://kubernetes.io/v1.0/docs/whatisk8s.html|website=Kubernetes|accessdate=28 August 2015}}</ref>

== History ==
Kubernetes (from κυβερνήτης: Greek for "helmsman" or "pilot") was first announced by Google in 2014.<ref>{{cite web|title=Google Open Sources Its Secret Weapon in Cloud Computing|url=http://www.wired.com/2014/06/google-kubernetes/|website=Wired|accessdate=24 September 2015}}</ref> Its development and design are heavily influenced by Google's Borg system,<ref>{{cite journal|author1=Abhishek Verma|author2=Luis Pedrosa|author3=Madhukar R. Korupolu|author4=David Oppenheimer|author5=Eric Tune|author6=John Wilkes|title=Large-scale cluster management at Google with Borg|journal=Proceedings of the European Conference on Computer Systems (EuroSys)|date=April 21–24, 2015|url=https://research.google.com/pubs/pub43438.html}}</ref> and many of the top contributors to the project previously worked on Borg. Kubernetes v1.0 was released on July 21, 2015.<ref>{{cite web|title=As Kubernetes Hits 1.0, Google Donates Technology To Newly Formed Cloud Native Computing Foundation|url=http://techcrunch.com/2015/07/21/as-kubernetes-hits-1-0-google-donates-technology-to-newly-formed-cloud-native-computing-foundation-with-ibm-intel-twitter-and-others/|website=TechCrunch|accessdate=24 September 2015}}</ref> Along with the Kubernetes v1.0 release, Google partnered with the [[Linux Foundation]] to form the [[Cloud Native Computing Foundation]] (CNCF)<ref>{{cite web|url=https://cncf.io/|title=Cloud Native Computing Foundation}}</ref> and offered Kubernetes as a seed technology.

== Design ==
Kubernetes defines a set of building blocks ("primitives") which collectively provide mechanisms for deploying, maintaining, and scaling applications. The components which make up Kubernetes are designed to be [[Loose coupling|loosely coupled]] and extensible so that it can meet a wide variety of different workloads. The extensibility is provided in large part by the Kubernetes API, which is used by internal components as well as extensions and containers running on Kubernetes.<ref name="do-intro">{{cite web|title=An Introduction to Kubernetes|url=https://www.digitalocean.com/community/tutorials/an-introduction-to-kubernetes|website=DigitalOcean|accessdate=24 September 2015}}</ref>

=== Pods ===
The basic scheduling unit in Kubernetes is a "pod". A pod consists of one or more containers that are guaranteed to be colocated on the host machine and can share resources.<ref name="do-intro" /> Each pod in Kubernetes is assigned a unique (within the cluster) [[IP address]], which allows applications to use ports without the risk of conflict.<ref name="kubernetes-101-networking">{{cite web |url=http://www.dasblinkenlichten.com/kubernetes-101-networking/ |title=Kubernetes 101 – Networking |last=Langemak |first=Jon |work=Das Blinken Lichten |date=2015-02-11 |accessdate=2015-11-02 }}</ref> A pod can define a volume, such as a local disk directory or a network disk, and expose it to the containers in the pod.<ref name="kubernetes-for-developers">{{cite web |last=Strachan |first=James |url=https://medium.com/fabric8-io/kubernetes-for-developers-2a9c7202fcd3#.b6u76jxar |title=Kubernetes for Developers |work=[[Medium (publishing platform)]] |date=2015-05-21 |accessdate=2015-11-02 }}</ref> Pods can be manually managed through the Kubernetes [[API]], or their management can be delegated to a controller.<ref name="do-intro" />

=== Labels and Selectors ===
Kubernetes allows clients (users or internal components) to attach key-value pairs called “labels” to any API object in the system, such as pods and nodes. Correspondingly, “label selectors” are queries against labels that resolve to matching objects.<ref name="do-intro" /> Labels and selectors are the primary grouping mechanism in Kubernetes, and are used to determine which components to apply an operation to.<ref name="containerizing-docker-on-Kubernetes">{{cite news |last=Surana |first=Ramit |url=https://www.linkedin.com/pulse/containerizing-docker-kubernetes-ramit-surana |title=Containerizing Docker on Kubernetes |work=[[LinkedIn]] |date=2015-09-16 |accessdate=2015-11-02 }}</ref> For example, if the Pods of an application have labels for “tier” (front-end, back-end, etc.) and “release_track” (canary, production, etc.), then an operation on all of the back-end canary nodes could use a selector <code>tier=back-end AND release_track=canary</code>.<ref name="redhat-docker-and-kubernetes-training-labels-examples">{{cite web |url=http://christianposta.com/slides/docker/generated/day2.html#/label-examples |title=Intro: Docker and Kubernetes training - Day 2 |publisher=[[Red Hat]] |date=2015-10-20 |accessdate=2015-11-02 }}</ref>

=== Controllers ===
A controller is a reconciliation loop that drives actual cluster state toward the desired cluster state.<ref name="coreos-replication-controller">{{cite web |url=https://coreos.com/kubernetes/docs/latest/replication-controller.html |title=Overview of a Replication Controller |work=Documentation |publisher=[[CoreOS]] |accessdate=2015-11-02 }}</ref> It does this by managing a set of pods. One kind of controller is a Replication Controller, which handles replication and scaling by running a specified number of copies of a pod across the cluster. It also handles creating replacement pods when the node a pod is running on, fails.<ref name="coreos-replication-controller" /> Other controllers that are part of the core Kubernetes system include a “DaemonSet controller” for running exactly one pod on every machine (or some subset of machines), and a “Job controller” for running pods that run to completion, e.g. as part of a batch job.<ref name="exciting-experimental-features">{{cite web |url=http://www.livewyer.com/blog/2015/10/02/kubernetes-exciting-experimental-features |title=Kubernetes: Exciting Experimental Features |last=Sanders |first=Jake |work=Livewyer |date=2015-10-02 |accessdate=2015-11-02 }}</ref> The set of pods that a controller manages is determined by label selectors that are part of the controller’s definition.<ref name="redhat-docker-and-kubernetes-training-labels-examples"/>

=== Services ===
A Kubernetes service is a set of pods that work together, such as one tier of a multi-tier application. The set of pods that constitute a service are defined by a label selector.<ref name="do-intro" />
Kubernetes provides service discovery and request routing by assigning a stable IP address and [[DNS name]] to the service, and [[Round-robin DNS|round-robin load balances]] network connections to that IP address among the pods matching the selector (even as failures cause the pods move from machine to machine).<ref name="kubernetes-101-networking" /> By default a service is exposed inside a cluster (e.g. [[Front and back ends|back end]] pods might be grouped into a service, with requests from the front-end pods load-balanced among them), but a service can also be exposed outside a cluster (e.g. for clients to reach frontend pods)<ref name="kubernetes-101-external-access">{{cite web |url=http://www.dasblinkenlichten.com/kubernetes-101-external-access-into-the-cluster/ |title=Kubernetes 101 – External Access Into The Cluster |last=Langemak |first=Jon |work=Das Blinken Lichten |date=2015-02-15 |accessdate=2015-11-02 }}</ref>

== Architecture ==
The components of Kubernetes can be divided into those that manage an individual [[Node (networking)|node]] and those that are part of the control plane.<ref name="do-intro" /><ref>{{cite web|title=Kubernetes Infrastructure|url=https://docs.openshift.org/latest/architecture/infrastructure_components/kubernetes_infrastructure.html|website=OpenShift Community Documentation|publisher=OpenShift|accessdate=24 September 2015}}</ref>

=== Kubernetes node ===
The node is a single machine (or [[virtual machine]]) being managed by Kubernetes. Every node in the cluster must run the container [[Runtime system|runtime]] (such as [[Docker (software)|Docker]]), as well as the '''Kubelet''' and the '''kube-proxy'''. The Kubelet is responsible for starting, stopping, and maintaining application containers (organized into ''pods'') as directed by the control plane.<ref name="do-intro" /><ref name="kubernetes-ground-up-kubelet">{{cite web |url=http://kamalmarhubi.com/blog/2015/08/27/what-even-is-a-kubelet/ |title=What [..] is a Kubelet? |last=Marhubi |first=Kamal |work=kamalmarhubi.com |date=2015-08-27 |accessdate=2015-11-02 }}</ref> The kube-proxy is an implementation of a [[Proxy server|network proxy]] and a [[Load balancing (computing)|load balancer]], and it supports the ''service'' abstraction along with other networking operations<ref name="do-intro" />

=== Kubernetes control plane ===
The Kubernetes control plane consists of various components, each its own process, which currently run on a single master node. The '''apiserver''' serves the kubernetes API using JSON over HTTP, which provides both the internal and external interface to Kubernetes.<ref name="do-intro" /><ref name="kubernetes-ground-up-api-server">{{cite web |url=http://kamalmarhubi.com/blog/2015/09/06/kubernetes-from-the-ground-up-the-api-server/ |title=Kubernetes from the ground up: API server |last=Marhubi |first=Kamal |work=kamalmarhubi.com |date=2015-09-26 |accessdate=2015-11-02 }}</ref> The api server writes the cluster state to [[etcd]], the persistent data store backing Kubernetes. The '''scheduler''' is the pluggable component that selects which node an unscheduled pod should run on. The '''controller manager''' is the process that the core Kubernetes controllers run in. The controllers communicate with the API server to create, update, and delete the resources they manage (pods, service endpoints, etc.)<ref name="kubernetes-ground-up-api-server" />

== References ==
{{Reflist|30em}}

== External links ==
* [http://kubernetes.io/ Official website]
* [https://github.com/kubernetes/kubernetes Source code repository]

{{Virtualization|state=collapsed}}

[[Category:Cloud infrastructure]]
[[Category:Free software for cloud computing]]
[[Category:Software using the Apache license]]
[[Category:Free software programmed in Go]]
[[Category:Virtualization-related software for Linux]]

Zen (Mikroarchitektur)

2015-11-16T08:42:16Z

Intgr: /* Architecture */ Citation needed for claim: Zen does not support DDR3

{{Infobox CPU
| name = Zen
| image =
| image_size = 138px
| caption =
| produced-start = 2016+
| produced-end =
| designfirm = [[AMD]]
| manuf1 = [[Advanced Micro Devices|AMD]]
| size-from = 14 nm ([[Multigate device#FinFET|Bulk Silicon]])<ref name="WCCF Zen">{{cite web|last=Moammer |first=Khalid |url=http://wccftech.com/breaking-amds-gen-x86-high-performance-core-code-named-zen-debut-k12/ |title=AMD's Next Gen x86 High Performance Core is Zen |publisher=WCCF Tech | date=September 9, 2014 |accessdate=January 15, 2015}}</ref>
| predecessor = [[Excavator (microarchitecture)|Excavator Family 15h (4th-gen)]]
| successor =
| arch = [[X86-64#AMD64|AMD64]] ([[x86-64]])
| sock1 = [[Socket AM4]]<ref name="Ryan Smith">{{cite web |url=http://www.anandtech.com/show/9231/amds-20162017-x86-roadmap-zen-is-in|title=AMD’s 2016-2017 x86 Roadmap: Zen Is In, Skybridge Is Out |author=Ryan Smith |date={{date|2015-05-06}} |publisher=[[AnandTech]] }}</ref>
| application = Desktop, Laptop, Server
| core1 =
| TDP =
}}

'''Zen''' is an upcoming [[CPU]] microarchitecture created by [[AMD]],<ref name="AMD hints at high-performance Zen">{{cite news|url=http://www.bit-tech.net/news/hardware/2014/09/11/amd-zen/1 | publisher=bit-tech | title=AMD hints at high-performance Zen x86 architecture | date=11 September 2014 | accessdate=15 December 2014}}</ref> expected for release in October 2016.<ref name="zenoct2016">{{cite news|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-set-to-release-first-zen-based-microprocessors-in-late-2016-document | website=KitGuru.net | title=AMD set to release first ‘Zen’-based microprocessors in late 2016 – document | date=12 June 2015 | accessdate=30 August 2015}}</ref>

==Architecture==
According to [[AMD]], Zen's main focus will be on increasing per-core performance rather than core count or multi-threading performance.<ref name="techspot">{{cite web|url=http://www.techspot.com/news/60626-tech-reading-amd-zen-comeback.html|title=Weekend tech reading: AMD 'Zen' and their return to high-end CPUs, tracking Windows pirates - TechSpot|publisher=techspot.com|accessdate=2015-05-12}}</ref><ref name="techreport">{{cite web|url=http://techreport.com/review/28228/amd-zen-chips-headed-to-desktops-servers-in-2016|title=AMD: Zen chips headed to desktops, servers in 2016 - The Tech Report - Page 1|publisher=techreport.com|accessdate=2015-05-12}}</ref><ref name="kitguru">{{cite news|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/ | work=KitGuru | title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be | date=11 September 2014 |author=Anton Shilov | accessdate=1 February 2015}}</ref> Reports from AMD indicate that Zen will abandon modular [[Bulldozer (microarchitecture)#CMT|CMT]] (Clustered Multithread) for a [[Simultaneous multithreading|SMT]] (Simultaneous Multithreading) microarchitecture,<ref name="WCCF Zen" /><ref>{{cite web|title=AMD 2015 comeback attempt: reforming high-performance processor, abandon modular architecture.|url=http://www.expreview.com/33161.html|publisher=Extreme Performance Review|accessdate=10 May 2015}}</ref> which is the same model that Intel uses, as well as what AMD has used in past architectures. Adapting their chips from the less-popular CMT to SMT<ref name="Ryan Smith"/> is expected to offer much higher number threading efficiency, but also possibly increase the die size of a Zen module.<ref name="kitguru" />

Reportedly, the Zen architecture will be built on a more efficient [[14 nanometer]] process, rather than the 32 nm and 28 nm processes of previous [[AMD FX]] CPUs and [[AMD Accelerated Processing Unit|AMD APUs]], respectively.<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading"/> The "Summit Ridge" Zen family will also feature a unified AM4 socket with its GPU-equipped "Raven Ridge" APU counterparts,<ref name="pcgamer">{{cite web|url=http://www.pcgamer.com/amds-next-gen-zen-cpu-due-in-2016/|title=AMD's next-gen Zen CPU due in 2016 - PC Gamer|publisher=pcgamer.com|accessdate=2015-05-12}}</ref> and feature [[DDR4 SDRAM|DDR4]] support and a 95W [[Thermal design power|TDP]].<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading">{{cite news|url=http://news.softpedia.com/news/14nm-AMD-Zen-CPU-Will-Have-DDR4-and-Simultaneous-Multithreading-471401.shtml | publisher=Softpedia | title=14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading | date=28 January 2015 | accessdate=31 January 2015}}</ref> Zen does not support DDR3;{{Citation needed|date=November 2015}} only 7th generation AMD APUs (also fitting the AMD AM4 unified socket) support DDR3 and DDR4. While newer roadmaps don't confirm the TDP for desktop products, they suggest a range for low-power mobile products with up to two Zen cores from 5 to 15W and 15 to 35W for performance-oriented mobile products with up to four Zen cores.<ref name="Shattered Media article">{{cite news| url=http://www.shattered.media/amds-next-gen-cpu-zen/ | publisher=Shattered.Media | title=AMD's next gen CPU Zen |date=May 2015}}</ref>

Zen will support [[RDSEED]].<ref name="AMD Starts Linux Enablement">{{cite news|url=http://www.phoronix.com/scan.php?page=news_item&px=AMD-Zen-CPU-Znver1 | publisher=Phoronix | title=AMD Starts Linux Enablement On Next-Gen "Zen" Architecture | date=17 March 2015 | accessdate=17 March 2015}}</ref>{{explain|date=October 2015}}

Zen core will have four integer units, two address generation units and four floating point units, and the decoder can decode four instructions per clock cycle.
L1 cache size is 32 kiB and L2 cache size 512 kiB per core. Two of the floating point units are adders, two are multipliers.<ref name="dresdenboy">{{cite web|title=AMD's Zen core (family 17h) to have ten pipelines per core|url=http://dresdenboy.blogspot.fi/2015/10/amds-zen-core-family-17h-to-have-ten.html}}</ref>{{Unreliable source?|certain=y|date=October 2015}}

{{quote box|align=right|width=35em|quote="It is the first time in a very long time that we engineers have been given the total freedom to build a processor from scratch and do the best we can do. It is a multi-year project with a really large team. It's like a marathon effort with some sprints in the middle. The team is working very hard, but they can see the finish line. I guarantee that it will deliver a huge improvement in performance and (low) power consumption over the previous generation."|source=—Suzanne Plummer, Zen team leader, on September 19th, 2015.<ref>http://www.mystatesman.com/news/business/amid-challenges-chipmnaker-amd-sees-a-way-forward/nngdf/</ref>}}

==History==
AMD began planning the Zen microarchitecture shortly after re-hiring [[Jim Keller (engineer)|Jim Keller]] in early 2012.<ref>{{cite av media|url=https://www.youtube.com/watch?v=SOTFE7sJY-Q|title=Jim Keller On AMD's Next-Gen High Performance x86 Zen Core & K12 ARM Core|date=7 May 2014|work=YouTube}}</ref>

The team in charge of the Zen microarchitecture was led by Keller until he left in September 2015 after a 3-year tenure.<ref name="anandtech">{{cite web|url=http://anandtech.com/show/9643/jim-keller-leaves-amd|title=Jim Keller Leaves AMD|publisher=anandtech.com|accessdate=2015-10-14}}</ref>

Zen was originally planned for 2017 following the ARM64-based [[AMD K12|K12]] sister core, but on AMD's 2015 Financial Analyst Day it was revealed that K12 was delayed in favour of the Zen design, to allow it to enter the market within the 2016 timeframe,<ref name="Ryan Smith" /> with the release of first Zen-based processors expected for October 2016.<ref name="zenoct2016"/>

As of November 2015, AMD reported that its Zen microprocessors had been tested and "met all expectations" with "no significant bottlenecks found".<ref>http://www.overclock3d.net/articles/cpu_mainboard/amd_tests_zen_cpus_met_all_expectation_with_no_significant_bottlenecks_found/1</ref>

==See also==
{{Portal|Computing}}

* [[Bulldozer (microarchitecture)]]
* [[Steamroller (microarchitecture)]]
* [[AMD K12]]

==References==
{{Reflist|40em}}

{{AMD processors|state=collapsed}}

[[Category:Advanced Micro Devices x86 microprocessors]]
[[Category:Advanced Micro Devices microarchitectures]]
[[Category:Upcoming integrated circuits]]

{{Comp-hardware-stub}}

Call to Action (Marketing)

2015-11-09T21:05:17Z

Intgr: Sorry, I can't make sense of what is said in this edit.

{{About-distinguish|the marketing term|Call to Action}}
{{multiple issues|
{{Refimprove|date=January 2012}}
{{third-party|date=January 2012}}
}}

{{marketing}}

In marketing, a '''call to action''' (CTA) is an instruction to the audience to provoke an immediate response, usually using an [[imperative verb]] such as "call now", "find out more" or "visit a store today".<ref>http://homebusiness.about.com/od/homebusinessglossar1/g/Call-To-Action-Definition.htm</ref>

A CTA can be a simple non-demanding request like "choose a colour" or "watch this video", or a much more demanding request. An obvious CTA would be requesting the audience to purchase a product or provide personal details and contact information.

Clever marketing strategies often combine a series of small CTAs. These smaller CTAs create a pattern of behaviour that makes it easy for the audience to follow-through with just one last CTA, completing a more demanding request, had it been asked without context. An example could be the purchase of a designer torch. The website might request you choose a style, then a colour, a size and even a personalised engraving. When you get to see your personalised one-of-a-kind product, you are more likely to feel inclined to buy it as it rotates in full 3D rendered colour on your computer monitor or tablet.

==On websites==
In web design, a CTA is a [[web banner|banner]], button, or some type of graphic or text on a website meant to prompt a user to [[Click analytics|click]] it and continue down a [[conversion funnel]]. It is an essential part of [[inbound marketing]] as well as [[permission marketing]] in that it actively strives to convert a user into a lead and later into a customer. The main goal of a CTA is a click, or a scan in the case of a [[qr code]], and its success can be measured via a conversion rate formula that calculates the number of clicks over the times the CTA was seen. Another way to test the effectiveness of a CTA is using [[A/B testing]] where several graphics are presented to users and the graphic with highest success rate becomes the default.

[[File:Cta.PNG|thumb|Example of a website CTA]]

== References ==

{{Reflist}}

[[Category:Marketing]]
[[Category:Market research]]
[[Category:Internet marketing terminology]]
[[Category:Marketing terminology]]
[[Category:Internet marketing]]
[[Category:Internet terminology]]
[[Category:Types of marketing]]

Kubernetes

2015-11-04T22:58:49Z

Intgr: Revert, not clear why he should be named in particular & the source doesn't mention that name. Undid revision 689090560 by Crasch (talk)

{{Infobox software
| name = Kubernetes
| title = Kubernetes
| logo = [[File:Kubernetes_(container_engine).png|75px]]
| caption =
| developer =
| status = Active
| released = {{Start date|2015|07|17|df=yes}}<ref name="github releases"/>
| latest release version = 1.0.7<ref name="github releases">{{cite web|url=https://github.com/kubernetes/kubernetes/releases |title=GitHub Releases page |work=github.com | date=2015-10-27}}</ref>
| latest release date = {{release date|2015|10|27}}
| operating system = [[Cross-platform]]
| programming language = [[Go]]
| genre = [[Computer cluster#Cluster management|Cluster management software]]
| posix compliant =
| license = [[Apache License]] 2.0
| website = {{URL|kubernetes.io}}
}}

'''Kubernetes''' is an [[open source]] [[Container (virtualization)|container]] [[Computer cluster#Cluster management|cluster manager]] by [[Google]]. It aims to provide a "platform for automating deployment, scaling, and operations of application containers across clusters of hosts"<ref>{{cite web|title=What is Kubernetes|url=http://kubernetes.io/v1.0/docs/whatisk8s.html|website=Kubernetes|accessdate=28 August 2015}}</ref>.

== History ==
Kubernetes (from κυβερνήτης: Greek for "helmsman" or "pilot") was first announced by Google in 2014<ref>{{cite web|title=Google Open Sources Its Secret Weapon in Cloud Computing|url=http://www.wired.com/2014/06/google-kubernetes/|website=Wired|accessdate=24 September 2015}}</ref>. Its development and design are heavily influenced by Google's Borg system<ref>{{cite journal|author1=Abhishek Verma|author2=Luis Pedrosa|author3=Madhukar R. Korupolu|author4=David Oppenheimer|author5=Eric Tune|author6=John Wilkes|title=Large-scale cluster management at Google with Borg|journal=Proceedings of the European Conference on Computer Systems (EuroSys)|date=April 21–24, 2015|url=https://research.google.com/pubs/pub43438.html}}</ref>, and many of the top contributors to the project previously worked on Borg. Kubernetes v1.0 was released on July 21, 2015<ref>{{cite web|title=As Kubernetes Hits 1.0, Google Donates Technology To Newly Formed Cloud Native Computing Foundation|url=http://techcrunch.com/2015/07/21/as-kubernetes-hits-1-0-google-donates-technology-to-newly-formed-cloud-native-computing-foundation-with-ibm-intel-twitter-and-others/|website=TechCrunch|accessdate=24 September 2015}}</ref>. Along with the Kubernetes v1.0 release, Google partnered with the [[Linux Foundation]] to form the [[Cloud Native Computing Foundation]] (CNCF)<ref>{{cite web|url=https://cncf.io/|title=Cloud Native Computing Foundation}}</ref> and offered Kubernetes as a seed technology.

== Design ==
Kubernetes defines a set of building blocks ("primitives") which collectively provide mechanisms for deploying, maintaining, and scaling applications. The components which make up Kubernetes are designed to be [[Loose_coupling|loosely coupled]] and extensible so that it can meet a wide variety of different workloads. The extensibility is provided in large part by the Kubernetes API, which is used by internal components as well as extensions and containers running on Kubernetes.<ref name="do-intro">{{cite web|title=An Introduction to Kubernetes|url=https://www.digitalocean.com/community/tutorials/an-introduction-to-kubernetes|website=DigitalOcean|accessdate=24 September 2015}}</ref>

=== Pods ===
The basic scheduling unit in Kubernetes is a "pod". A pod consists of one or more containers that are guaranteed to be colocated on the host machine and can share resources<ref name="do-intro" />. Each pod in Kubernetes is assigned a unique (within the cluster) [[IP address]], which allows applications to use ports without the risk of conflict<ref name="kubernetes-101-networking">{{cite web |url=http://www.dasblinkenlichten.com/kubernetes-101-networking/ |title=Kubernetes 101 – Networking |last=Langemak |first=Jon |work=Das Blinken Lichten |date=2015-02-11 |accessdate=2015-11-02 }}</ref>. A pod can define a volume, such as a local disk directory or a network disk, and expose it to the containers in the pod<ref name="kubernetes-for-developers">{{cite web |last=Strachan |first=James |url=https://medium.com/fabric8-io/kubernetes-for-developers-2a9c7202fcd3#.b6u76jxar |title=Kubernetes for Developers |work=[[Medium (publishing platform)]] |date=2015-05-21 |accessdate=2015-11-02 }}</ref>. Pods can be manually managed through the Kubernetes [[API]], or their management can be delegated to a controller<ref name="do-intro" />.

=== Labels and Selectors ===
Kubernetes allows clients (users or internal components) to attach key-value pairs called “labels” to any API object in the system, such as pods and nodes. Correspondingly, “label selectors” are queries against labels that resolve to matching objects<ref name="do-intro" />. Labels and selectors are the primary grouping mechanism in Kubernetes, and are used to determine which components to apply an operation to<ref name="containerizing-docker-on-Kubernetes">{{cite news |last=Surana |first=Ramit |url=https://www.linkedin.com/pulse/containerizing-docker-kubernetes-ramit-surana |title=Containerizing Docker on Kubernetes |work=[[LinkedIn]] |date=2015-09-16 |accessdate=2015-11-02 }}</ref>. For example, if the Pods of an application have labels for “tier” (front-end, back-end, etc.) and “release_track” (canary, production, etc.), then an operation on all of the back-end canary nodes could use a selector <code>tier=back-end AND release_track=canary</code><ref name="redhat-docker-and-kubernetes-training-labels-examples">{{cite web |url=http://christianposta.com/slides/docker/generated/day2.html#/label-examples |title=Intro: Docker and Kubernetes training - Day 2 |publisher=[[Red Hat]] |date=2015-10-20 |accessdate=2015-11-02 }}</ref>.

=== Controllers ===
A controller is a reconciliation loop that drives actual cluster state toward the desired cluster state<ref name="coreos-replication-controller">{{cite web |url=https://coreos.com/kubernetes/docs/latest/replication-controller.html |title=Overview of a Replication Controller |work=Documentation |publisher=[[CoreOS]] |accessdate=2015-11-02 }}</ref>. It does this by managing a set of pods. One kind of controller is a Replication Controller, which handles replication and scaling by running a specified number of copies of a pod across the cluster. It also handles creating replacement pods when the node a pod is running on, fails<ref name="coreos-replication-controller" />. Other controllers that are part of the core Kubernetes system include a “DaemonSet controller” for running exactly one pod on every machine (or some subset of machines), and a “Job controller” for running pods that run to completion, e.g. as part of a batch job<ref name="exciting-experimental-features">{{cite web |url=http://www.livewyer.com/blog/2015/10/02/kubernetes-exciting-experimental-features |title=Kubernetes: Exciting Experimental Features |last=Sanders |first=Jake |work=Livewyer |date=2015-10-02 |accessdate=2015-11-02 }}</ref>. The set of pods that a controller manages is determined by label selectors that are part of the controller’s definition<ref name="redhat-docker-and-kubernetes-training-labels-examples"/>.

=== Services ===
A Kubernetes service is a set of pods that work together, such as one tier of a multi-tier application. The set of pods that constitute a service are defined by a label selector<ref name="do-intro" />.
Kubernetes provides service discovery and request routing by assigning a stable IP address and [[DNS name]] to the service, and [[Round-robin_DNS|round-robin load balances]] network connections to that IP address among the pods matching the selector (even as failures cause the pods move from machine to machine)<ref name="kubernetes-101-networking" />. By default a service is exposed inside a cluster (e.g. [[Front_and_back_ends|back end]] pods might be grouped into a service, with requests from the front-end pods load-balanced among them), but a service can also be exposed outside a cluster (e.g. for clients to reach frontend pods)<ref name="kubernetes-101-external-access">{{cite web |url=http://www.dasblinkenlichten.com/kubernetes-101-external-access-into-the-cluster/ |title=Kubernetes 101 – External Access Into The Cluster |last=Langemak |first=Jon |work=Das Blinken Lichten |date=2015-02-15 |accessdate=2015-11-02 }}</ref>

== Architecture ==
The components of Kubernetes can be divided into those that manage an individual [[Node_(networking)|node]] and those that are part of the control plane.<ref name="do-intro" /><ref>{{cite web|title=Kubernetes Infrastructure|url=https://docs.openshift.org/latest/architecture/infrastructure_components/kubernetes_infrastructure.html|website=OpenShift Community Documentation|publisher=OpenShift|accessdate=24 September 2015}}</ref>

=== Kubernetes node ===
The node is a single machine (or [[virtual machine]]) being managed by Kubernetes. Every node in the cluster must run the container [[Runtime_system|runtime]] (such as [[Docker_(software)|Docker]]), as well as the '''Kubelet''' and the '''kube-proxy'''. The Kubelet is responsible for starting, stopping, and maintaining application containers (organized into ''pods'') as directed by the control plane.<ref name="do-intro" /><ref name="kubernetes-ground-up-kubelet">{{cite web |url=http://kamalmarhubi.com/blog/2015/08/27/what-even-is-a-kubelet/ |title=What [..] is a Kubelet? |last=Marhubi |first=Kamal |work=kamalmarhubi.com |date=2015-08-27 |accessdate=2015-11-02 }}</ref>. The kube-proxy is an implementation of a [[Proxy_server|network proxy]] and a [[Load_balancing_(computing)|load balancer]], and it supports the ''service'' abstraction along with other networking operations<ref name="do-intro" />

=== Kubernetes control plane ===
The Kubernetes control plane consists of various components, each its own process, which currently run on a single master node. The '''apiserver''' serves the kubernetes API using JSON over HTTP, which provides both the internal and external interface to Kubernetes.<ref name="do-intro" /><ref name="kubernetes-ground-up-api-server">{{cite web |url=http://kamalmarhubi.com/blog/2015/09/06/kubernetes-from-the-ground-up-the-api-server/ |title=Kubernetes from the ground up: API server |last=Marhubi |first=Kamal |work=kamalmarhubi.com |date=2015-09-26 |accessdate=2015-11-02 }}</ref>. The api server writes the cluster state to [[etcd]], the persistent data store backing Kubernetes. The '''scheduler''' is the pluggable component that selects which node an unscheduled pod should run on. The '''controller manager''' is the process that the core Kubernetes controllers run in. The controllers communicate with the API server to create, update, and delete the resources they manage (pods, service endpoints, etc.)<ref name="kubernetes-ground-up-api-server" />

== References ==
{{Reflist|30em}}

== External links ==
* [http://kubernetes.io/ Official website]
* [https://github.com/kubernetes/kubernetes Source code repository]

{{Virtualization|state=collapsed}}

[[Category:Cloud infrastructure]]
[[Category:Free software for cloud computing]]
[[Category:Software using the Apache license]]
[[Category:Free software programmed in Go]]
[[Category:Virtualization-related software for Linux]]

Zen (Mikroarchitektur)

2015-11-03T19:37:37Z

Intgr: /* Architecture */ Redundant punctuation

{{Infobox CPU
| name = Zen
| image =
| image_size = 138px
| caption =
| produced-start = 2016+
| produced-end =
| designfirm = [[AMD]]
| manuf1 = [[Advanced Micro Devices|AMD]]
| size-from = 14 nm ([[Multigate device#FinFET|Bulk Silicon]])<ref name="WCCF Zen">{{cite web|last=Moammer |first=Khalid |url=http://wccftech.com/breaking-amds-gen-x86-high-performance-core-code-named-zen-debut-k12/ |title=AMD's Next Gen x86 High Performance Core is Zen |publisher=WCCF Tech | date=September 9, 2014 |accessdate=January 15, 2015}}</ref>
| predecessor = [[Excavator (microarchitecture)|Excavator Family 15h (4th-gen)]]
| successor =
| arch = [[X86-64#AMD64|AMD64]] ([[x86-64]])
| sock1 = [[Socket AM4]]<ref name="Ryan Smith">{{cite web |url=http://www.anandtech.com/show/9231/amds-20162017-x86-roadmap-zen-is-in|title=AMD’s 2016-2017 x86 Roadmap: Zen Is In, Skybridge Is Out |author=Ryan Smith |date={{date|2015-05-06}} |publisher=[[AnandTech]] }}</ref>
| application = Desktop, Laptop, Server
| core1 =
| TDP =
}}

'''Zen''' is an upcoming [[CPU]] microarchitecture created by [[AMD]].<ref name="AMD hints at high-performance Zen">{{cite news|url=http://www.bit-tech.net/news/hardware/2014/09/11/amd-zen/1 | publisher=bit-tech | title=AMD hints at high-performance Zen x86 architecture | date=11 September 2014 | accessdate=15 December 2014}}</ref> The team in charge of the Zen microarchitecture was led by [[Jim Keller (engineer)|Jim Keller]] until he left in September 2015 after a 3-year tenure.<ref name="anandtech">{{cite web|url=http://anandtech.com/show/9643/jim-keller-leaves-amd|title=Jim Keller Leaves AMD|publisher=anandtech.com|accessdate=2015-10-14}}</ref> Zen was originally planned for 2017 following the ARM64-based [[AMD K12|K12]] sister core, but on AMD's 2015 Financial Analyst Day it was revealed that K12 was delayed in favour of the Zen design for market entry in the 2016 timeframe.<ref name="Ryan Smith" />

==Architecture==
According to [[AMD]], Zen's main focus will be on increasing per-core performance rather than core count or multi-threading performance.<ref name="techspot">{{cite web|url=http://www.techspot.com/news/60626-tech-reading-amd-zen-comeback.html|title=Weekend tech reading: AMD 'Zen' and their return to high-end CPUs, tracking Windows pirates - TechSpot|publisher=techspot.com|accessdate=2015-05-12}}</ref><ref name="techreport">{{cite web|url=http://techreport.com/review/28228/amd-zen-chips-headed-to-desktops-servers-in-2016|title=AMD: Zen chips headed to desktops, servers in 2016 - The Tech Report - Page 1|publisher=techreport.com|accessdate=2015-05-12}}</ref><ref name="kitguru">{{cite news|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/ | work=KitGuru | title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be | date=11 September 2014 |author=Anton Shilov | accessdate=1 February 2015}}</ref> Reports from AMD indicate that Zen will abandon modular [[Bulldozer (microarchitecture)#CMT|CMT]] (Clustered Multithread) for a [[Simultaneous multithreading|SMT]] (Simultaneous Multithreading) microarchitecture,<ref name="WCCF Zen" /><ref>{{cite web|title=AMD 2015 comeback attempt: reforming high-performance processor, abandon modular architecture.|url=http://www.expreview.com/33161.html|publisher=Extreme Performance Review|accessdate=10 May 2015}}</ref> which is the same model that Intel uses, as well as what AMD has used in past architectures. Adapting their chips from the less-popular CMT to SMT<ref name="Ryan Smith"/> is expected to offer much higher number threading efficiency, but also possibly increase the die size of Zen module.<ref name="kitguru" />

Reportedly, the Zen architecture will be built on a more efficient [[14 nanometer]] process, rather than the 32 nm and 28 nm processes of previous [[AMD FX]] CPUs and [[AMD Accelerated Processing Unit|AMD APUs]], respectively.<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading"/> The [[Summit Ridge]] Zen family will also feature a unified AM4 socket with its GPU-equipped [[Raven Ridge]] APU counterparts,<ref name="pcgamer">{{cite web|url=http://www.pcgamer.com/amds-next-gen-zen-cpu-due-in-2016/|title=AMD's next-gen Zen CPU due in 2016 - PC Gamer|publisher=pcgamer.com|accessdate=2015-05-12}}</ref> and feature [[DDR4 SDRAM|DDR4]] support and a 95W [[Thermal design power|TDP]].<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading">{{cite news|url=http://news.softpedia.com/news/14nm-AMD-Zen-CPU-Will-Have-DDR4-and-Simultaneous-Multithreading-471401.shtml | publisher=Softpedia | title=14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading | date=28 January 2015 | accessdate=31 January 2015}}</ref> Zen does NOT support DDR3; only 7th generation AMD APUs (also fitting the AMD AM4 unified socket) support DDR3 AND DDR4. While newer roadmaps don't confirm the TDP for desktop products, they suggest a range for low-power mobile products with up to two Zen cores from 5 to 15W and 15 to 35W for performance-oriented mobile products with up to four Zen cores.<ref name="Shattered Media article">{{cite news| url=http://www.shattered.media/amds-next-gen-cpu-zen/ | publisher=Shattered.Media | title=AMD's next gen CPU Zen |date=May 2015}}</ref>

Zen will support [[RDSEED]].<ref name="AMD Starts Linux Enablement">{{cite news|url=http://www.phoronix.com/scan.php?page=news_item&px=AMD-Zen-CPU-Znver1 | publisher=Phoronix | title=AMD Starts Linux Enablement On Next-Gen "Zen" Architecture | date=17 March 2015 | accessdate=17 March 2015}}</ref>{{explain|date=October 2015}}

Zen core will have four integer units, two address generation units and four floating point units, and the decoder can decode four instructions per clock cycle.
L1 cache size is 32 kiB and L2 cache size 512 kiB per core. Two of the floating point units are adders, two are multipliers.<ref name="dresdenboy">{{cite web|title=AMD's Zen core (family 17h) to have ten pipelines per core|url=http://dresdenboy.blogspot.fi/2015/10/amds-zen-core-family-17h-to-have-ten.html}}</ref>{{Unreliable source?|certain=y|date=October 2015}}

{{quote box|align=right|width=35em|quote="It is the first time in a very long time that we engineers have been given the total freedom to build a processor from scratch and do the best we can do. It is a multi-year project with a really large team. It's like a marathon effort with some sprints in the middle. The team is working very hard, but they can see the finish line. I guarantee that it will deliver a huge improvement in performance and (low) power consumption over the previous generation."|source=—Suzanne Plummer, Zen team leader, on September 19th, 2015.<ref>http://www.mystatesman.com/news/business/amid-challenges-chipmnaker-amd-sees-a-way-forward/nngdf/</ref>}}
Zen microprocessors tested and "met all expectations" with "no significant bottlenecks found": 2 November 2015 (http://www.overclock3d.net/articles/cpu_mainboard/amd_tests_zen_cpus_met_all_expectation_with_no_significant_bottlenecks_found/1)

==History==
AMD began planning the Zen microarchitecture shortly after re-hiring [[Jim Keller (engineer)|Jim Keller]] in early 2012.<ref>{{cite av media|url=https://www.youtube.com/watch?v=SOTFE7sJY-Q|title=Jim Keller On AMD's Next-Gen High Performance x86 Zen Core & K12 ARM Core|date=7 May 2014|work=YouTube}}</ref>

The release of first Zen-based processors is expected in October 2016.<ref>{{cite news|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-set-to-release-first-zen-based-microprocessors-in-late-2016-document | website=KitGuru.net | title=AMD set to release first ‘Zen’-based microprocessors in late 2016 – document | date=12 June 2015 | accessdate=30 August 2015}}</ref>

Jim Keller left AMD on Sept. 18th, 2015. Keller was present at AMD for about three years, and it's assumed that Zen's design was completed prior to his departure.{{Citation needed|date=September 2015}}

==See also==
{{Portal|Computing}}

* [[Bulldozer (microarchitecture)]]
* [[Steamroller (microarchitecture)]]
* [[AMD K12]]

==References==
{{Reflist|40em}}

{{AMD processors|state=collapsed}}

[[Category:Advanced Micro Devices x86 microprocessors]]
[[Category:Advanced Micro Devices microarchitectures]]
[[Category:Upcoming integrated circuits]]

{{Comp-hardware-stub}}

Zen (Mikroarchitektur)

2015-11-01T23:24:41Z

Intgr: Revert partially, Bulldozer CPUs are "directly compatible" with Intel ones too, SMT vs CMT doesn't matter to applications

{{Infobox CPU
| name = Zen
| image =
| image_size = 138px
| caption =
| produced-start = 2016+
| produced-end =
| designfirm = [[AMD]]
| manuf1 = [[Advanced Micro Devices|AMD]]
| size-from = 14 nm ([[Multigate device#FinFET|Bulk Silicon]])<ref name="WCCF Zen">{{cite web|last=Moammer |first=Khalid |url=http://wccftech.com/breaking-amds-gen-x86-high-performance-core-code-named-zen-debut-k12/ |title=AMD's Next Gen x86 High Performance Core is Zen |publisher=WCCF Tech | date=September 9, 2014 |accessdate=January 15, 2015}}</ref>
| predecessor = [[Excavator (microarchitecture)|Excavator Family 15h (4th-gen)]]
| successor =
| arch = [[X86-64#AMD64|AMD64]] ([[x86-64]])
| sock1 = [[Socket AM4]]<ref name="Ryan Smith">{{cite web |url=http://www.anandtech.com/show/9231/amds-20162017-x86-roadmap-zen-is-in|title=AMD’s 2016-2017 x86 Roadmap: Zen Is In, Skybridge Is Out |author=Ryan Smith |date={{date|2015-05-06}} |publisher=[[AnandTech]] }}</ref>
| application = Desktop, Laptop, Server
| core1 =
| TDP =
}}

'''Zen''' is an upcoming [[CPU]] microarchitecture created by [[AMD]].<ref name="AMD hints at high-performance Zen">{{cite news|url=http://www.bit-tech.net/news/hardware/2014/09/11/amd-zen/1 | publisher=bit-tech | title=AMD hints at high-performance Zen x86 architecture | date=11 September 2014 | accessdate=15 December 2014}}</ref> The team in charge of the Zen microarchitecture was led by [[Jim Keller (engineer)|Jim Keller]] until he left in September 2015 after a 3-year tenure.<ref name="anandtech">{{cite web|url=http://anandtech.com/show/9643/jim-keller-leaves-amd|title=Jim Keller Leaves AMD|publisher=anandtech.com|accessdate=2015-10-14}}</ref> Zen was originally planned for 2017 following the ARM64-based [[AMD K12|K12]] sister core, but on AMD's 2015 Financial Analyst Day it was revealed that K12 was delayed in favour of the Zen design for market entry in the 2016 timeframe.<ref name="Ryan Smith" />

==Architecture==
According to [[AMD]], Zen's main focus will be on increasing per-core performance rather than core count or multi-threading performance.<ref name="techspot">{{cite web|url=http://www.techspot.com/news/60626-tech-reading-amd-zen-comeback.html|title=Weekend tech reading: AMD 'Zen' and their return to high-end CPUs, tracking Windows pirates - TechSpot|publisher=techspot.com|accessdate=2015-05-12}}</ref><ref name="techreport">{{cite web|url=http://techreport.com/review/28228/amd-zen-chips-headed-to-desktops-servers-in-2016|title=AMD: Zen chips headed to desktops, servers in 2016 - The Tech Report - Page 1|publisher=techreport.com|accessdate=2015-05-12}}</ref><ref name="kitguru">{{cite news|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/ | work=KitGuru | title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be | date=11 September 2014 |author=Anton Shilov | accessdate=1 February 2015}}</ref> Reports from AMD indicate that Zen will abandon modular [[Bulldozer (microarchitecture)#CMT|CMT]] (Clustered Multithread) for a [[Simultaneous multithreading|SMT]] (Simultaneous Multithreading) microarchitecture,<ref name="WCCF Zen" /><ref>{{cite web|title=AMD 2015 comeback attempt: reforming high-performance processor, abandon modular architecture.|url=http://www.expreview.com/33161.html|publisher=Extreme Performance Review|accessdate=10 May 2015}}</ref> which is the same model that Intel uses, as well as what AMD has used in past architectures. Adapting their chips from the less-popular CMT to SMT<ref name="Ryan Smith"/> is expected to offer much higher number threading efficiency, but also possibly increase the die size of Zen module.<ref name="kitguru" />

Reportedly, the Zen architecture will be built on a more efficient [[14 nanometer]] process, rather than the 32 nm and 28 nm processes of previous [[AMD FX]] CPUs and [[AMD Accelerated Processing Unit|AMD APUs]], respectively.<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading"/> The [[Summit Ridge]] Zen family will also feature a unified AM4 socket with its GPU-equipped [[Raven Ridge]] APU counterparts,<ref name="pcgamer">{{cite web|url=http://www.pcgamer.com/amds-next-gen-zen-cpu-due-in-2016/|title=AMD's next-gen Zen CPU due in 2016 - PC Gamer|publisher=pcgamer.com|accessdate=2015-05-12}}</ref> and feature [[DDR4 SDRAM|DDR4]] support and a 95W [[Thermal design power|TDP]].<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading">{{cite news|url=http://news.softpedia.com/news/14nm-AMD-Zen-CPU-Will-Have-DDR4-and-Simultaneous-Multithreading-471401.shtml | publisher=Softpedia | title=14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading | date=28 January 2015 | accessdate=31 January 2015}}</ref> While newer roadmaps don't confirm the TDP for desktop products, they suggest a range for low-power mobile products with up to two Zen cores from 5 to 15W and 15 to 35W for performance-oriented mobile products with up to four Zen cores.<ref name="Shattered Media article">{{cite news| url=http://www.shattered.media/amds-next-gen-cpu-zen/ | publisher=Shattered.Media | title=AMD's next gen CPU Zen |date=May 2015}}</ref>

Zen will support [[RDSEED]].<ref name="AMD Starts Linux Enablement">{{cite news|url=http://www.phoronix.com/scan.php?page=news_item&px=AMD-Zen-CPU-Znver1 | publisher=Phoronix | title=AMD Starts Linux Enablement On Next-Gen "Zen" Architecture | date=17 March 2015 | accessdate=17 March 2015}}</ref>{{explain|date=October 2015}}

Zen core will have four integer units, two address generation units and four floating point units, and the decoder can decode four instructions per clock cycle.
L1 cache size is 32 kiB and L2 cache size 512 kiB per core. Two of the floating point units are adders, two are multipliers.<ref name="dresdenboy">{{cite web|title=AMD's Zen core (family 17h) to have ten pipelines per core|url=http://dresdenboy.blogspot.fi/2015/10/amds-zen-core-family-17h-to-have-ten.html}}</ref>{{Unreliable source?|certain=y|date=October 2015}}

{{quote box|align=right|width=35em|quote="It is the first time in a very long time that we engineers have been given the total freedom to build a processor from scratch and do the best we can do. It is a multi-year project with a really large team. It's like a marathon effort with some sprints in the middle. The team is working very hard, but they can see the finish line. I guarantee that it will deliver a huge improvement in performance and (low) power consumption over the previous generation."|source=—Suzanne Plummer, Zen team leader, on September 19th, 2015.<ref>http://www.mystatesman.com/news/business/amid-challenges-chipmnaker-amd-sees-a-way-forward/nngdf/</ref>}}

==History==
AMD began planning the Zen microarchitecture shortly after re-hiring [[Jim Keller (engineer)|Jim Keller]] in early 2012.<ref>{{cite av media|url=https://www.youtube.com/watch?v=SOTFE7sJY-Q|title=Jim Keller On AMD's Next-Gen High Performance x86 Zen Core & K12 ARM Core|date=7 May 2014|work=YouTube}}</ref>

The release of first Zen-based processors is expected in October 2016.<ref>{{cite news|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-set-to-release-first-zen-based-microprocessors-in-late-2016-document | website=KitGuru.net | title=AMD set to release first ‘Zen’-based microprocessors in late 2016 – document | date=12 June 2015 | accessdate=30 August 2015}}</ref>

Jim Keller left AMD on Sept. 18th, 2015. Keller was present at AMD for about three years, and it's assumed that Zen's design was completed prior to his departure.{{Citation needed|date=September 2015}}

==See also==
{{Portal|Computing}}

* [[Bulldozer (microarchitecture)]]
* [[Steamroller (microarchitecture)]]
* [[AMD K12]]

==References==
{{Reflist|40em}}

{{AMD processors|state=collapsed}}

[[Category:Advanced Micro Devices x86 microprocessors]]
[[Category:Advanced Micro Devices microarchitectures]]
[[Category:Upcoming integrated circuits]]

{{Comp-hardware-stub}}

Linux Security Modules

2015-10-27T08:09:27Z

Intgr: Fix citation

'''Linux Security Modules''' ('''LSM''') is a [[Software framework|framework]] that allows the [[Linux kernel]] to support a variety of [[computer security model]]s while avoiding favoritism toward any single security implementation. The framework is licensed under the terms of the [[GNU General Public License]] and is standard part of the Linux kernel since Linux 2.6. [[AppArmor]], [[SELinux]], [[Smack (Linux security module)|Smack]] and [[TOMOYO Linux]] are the currently accepted modules in the official kernel.

== Design ==
LSM was designed to provide the specific needs of everything needed to successfully implement a [[mandatory access control]] module, while imposing the fewest possible changes to the Linux kernel. LSM avoids the approach of [[system call interposition]] as used in [[Systrace]] because it does not scale to [[multiprocessor]] kernels and is subject to [[TOCTTOU]] (race) attacks. Instead, LSM inserts "hooks" (upcalls to the module) at every point in the kernel where a user-level system call is about to result in access to an important internal kernel object such as inodes and task control blocks.

The project is narrowly scoped to solve the problem of [[access control]] to avoid imposing a large and complex change patch on the mainstream kernel. It is not intended as a general "''hook''" or "''upcall''" mechanism, nor does it support [[Operating system-level virtualization]].

LSM's access control goal is very closely related to the problem of [[system auditing]], but is subtly different. Auditing requires that every attempt at access be recorded. LSM cannot deliver that, because it would require a great many more hooks, so as to detect cases where the kernel "''short circuits''" failing system calls and returns an error code before getting near significant objects.

The LSM design is described in the paper ''Linux Security Modules: General Security Support for the Linux Kernel''<ref>{{cite web|url=http://www.usenix.org/event/sec02/wright.html|title=Linux Security Modules: General Security Support for the Linux Kernel|accessdate = 2007-02-03|year = 2002}}</ref> presented at USENIX Security 2002.<ref>{{cite web|url=http://www.usenix.org/event/sec02/|title=11th USENIX Security Symposium|accessdate = 2007-02-03|year = 2002}}</ref> At the same conference was the paper ''Using CQUAL for Static Analysis of Authorization Hook Placement''<ref>{{cite web|url=http://www.usenix.org/event/sec02/zhang.html|title=Using CQUAL for Static Analysis of Authorization Hook Placement|accessdate = 2007-02-03|year = 2002}}</ref> which studied automatic static analysis of the kernel code to verify that all of the necessary hooks have actually been inserted into the Linux kernel.

== Adoption ==
*[[AppArmor]]
*[[Security-Enhanced Linux|SELinux]]
*[[Smack (Linux security module)|Smack]]
*[[TOMOYO Linux|TOMOYO]]

== History ==
At the 2001 Linux Kernel Summit, the [[National Security Agency|NSA]] proposed that [[Security-Enhanced Linux|SELinux]] be included in Linux 2.5.<ref>{{cite web | url=http://www.hep.by/gnu/kernel/lsm/ |authors=Stephen Smalley, Timothy Fraser, Chris Vance |title=Linux Security Modules: General Security Hooks for Linux |accessdate=2015-10-26 }}</ref> [[Linus Torvalds]] rejected SELinux at that time, because he observed that there are many different security projects in development, and since they all differ, the security community has not yet formed consensus on the ultimate security model. Instead, Linus charged the security community to "make it a module".

In response, [[Crispin Cowan]] proposed<ref>{{cite web|url=http://marc.info/?l=linux-kernel&m=98695004126478&w=2|title=Linux Security Module Interface|accessdate=2007-02-03|author=Crispin Cowan|work=linux-kernel mailing list|date=2001-04-11}}</ref> LSM: an interface for the Linux kernel that provides sufficient "hooks" (upcalls) from within the Linux kernel to a [[Loadable kernel module|loadable module]] so as to allow the module to enforce mandatory access controls. Development of LSM over the next two years was conducted by the LSM community, including substantial contributions from the [[Immunix|Immunix Corporation]], the [[NSA]], [[McAfee]], [[IBM]], [[Silicon Graphics]], and many independent contributors. LSM was ultimately accepted into the Linux kernel mainstream and was included as a standard part of Linux 2.6 in December 2003.

In 2006, some kernel developers observed that SELinux was the only widely used LSM module included in the mainstream Linux kernel source tree. If there is to be only one widely used LSM module, it was reasoned, then the indirection of LSM is unnecessary, and LSM should be removed and replaced with SELinux itself. However, there are other LSM modules maintained outside of the mainstream kernel tree ([[AppArmor]], [[Linux Intrusion Detection System]], [[FireFlier]], [[CIPSO]], [[Multi ADM]], etc.), so this argument led to two results: 1. that developers of these modules started putting effort into upstreaming their respective modules, and 2. at the 2006 [[Kernel Summit]], Linus once again asserted that LSM would stay because he does not want to arbitrate which is the best security model. LSM is likely to remain since an additional security module [[TOMOYO Linux]] was accepted in the mainline kernel version 2.6.30 (June 2009). With version 2.6.36, another security module ([[AppArmor]]) was accepted in the mainline kernel.

== Criticism ==
Some Linux kernel developers dislike LSM for a variety of reasons. LSM strives to impose the least overhead possible, especially in the case where no module is loaded, but this cost is not zero, and some Linux developers object to that cost. LSM is designed to provide only for access control, but does not actually prevent people from using LSM for other reasons, and so some Linux kernel developers dislike that it can be "abused" by being used for other purposes, especially if the purpose is to bypass the Linux kernel's [[GPL]] license with a proprietary module to extend Linux kernel functionality.

Some security developers also dislike LSM. The author of [[grsecurity]] dislikes LSM<ref>{{cite web|url=http://www.grsecurity.net/lsm.php|title=grsecurity|accessdate=2007-02-03|publisher=grsecurity}}</ref> because of its history, and that because LSM exports all of its symbols it facilitates the insertion of malicious modules ([[rootkits]]) as well as security modules. The author of [[RSBAC]] dislikes LSM<ref>{{cite web|url=http://www.rsbac.org/documentation/why_rsbac_does_not_use_lsm|title=RSBAC and LSM|accessdate=2007-02-03|publisher=RSBAC}}</ref> because it is incomplete with respect to the needs of RSBAC. In particular, the author of RSBAC argues that: "LSM is only about additional, restrictive access control. However, the RSBAC system provides a lot of additional functionality, e.g. symlink redirection, secure_delete, partial Linux DAC disabling. All this has to be patched into kernel functions in a separate patch.". The author of [[Dazuko]] argues<ref>{{cite web|url=http://dazuko.org/tgen.shtml#LSM|title=dazuko|accessdate=2007-10-02|publisher=dazuko}}</ref> that targeting the LSM API is a moving target, as it changes with each kernel release, leading to extra maintenance work. Other developers would like to have LSM modules stacked, e.g. the developer of the Yama LSM.<ref>{{cite web|last1=Edge|first1=Jake|title=LSM stacking (again)|url=http://lwn.net/Articles/393008/|publisher=www.lwn.net|accessdate=28 May 2015|date=23 June 2010}}</ref>

==References==
{{Reflist|2}}

==External links==
{{Portal|Free software}}
* [http://lsm.bkbits.net/ Source code and project statistics]
* [http://web.archive.org/web/20040816140809/http://www.samag.com/documents/s=9304/sam0409a/0409a.htm SysAdmin magazine article on BSD Secure Levels]
* [http://kernsec.org/wiki/index.php/Projects Security Projects based on the Linux kernel]
{{Linux}}

[[Category:Linux kernel]]
[[Category:Operating system security]]

Zen (Mikroarchitektur)

2015-10-18T23:05:53Z

Intgr: Fix redundant dot

{{Infobox CPU
| name = Zen
| image =
| image_size = 138px
| caption =
| produced-start = 2016+
| produced-end =
| designfirm = [[AMD]]
| manuf1 = [[Advanced Micro Devices|AMD]]
| size-from = 14 nm ([[Multigate device#FinFET|Bulk Silicon]])<ref name="WCCF Zen">{{cite web|last=Moammer |first=Khalid |url=http://wccftech.com/breaking-amds-gen-x86-high-performance-core-code-named-zen-debut-k12/ |title=AMD's Next Gen x86 High Performance Core is Zen |publisher=WCCF Tech | date=September 9, 2014 |accessdate=January 15, 2015}}</ref>
| predecessor = [[Excavator (microarchitecture)|Excavator Family 15h (4th-gen)]]
| successor =
| arch = [[X86-64#AMD64|AMD64]] ([[x86-64]])
| sock1 = [[Socket AM4]]<ref name="Ryan Smith">{{cite web |url=http://www.anandtech.com/show/9231/amds-20162017-x86-roadmap-zen-is-in|title=AMD’s 2016-2017 x86 Roadmap: Zen Is In, Skybridge Is Out |author=Ryan Smith |date={{date|2015-05-06}} |publisher=[[AnandTech]] }}</ref>
| application = Desktop, Laptop, Server
| core1 =
| TDP =
}}

'''Zen''' is an upcoming [[CPU]] microarchitecture created by [[AMD]].<ref name="AMD hints at high-performance Zen">{{cite news|url=http://www.bit-tech.net/news/hardware/2014/09/11/amd-zen/1 | publisher=bit-tech | title=AMD hints at high-performance Zen x86 architecture | date=11 September 2014 | accessdate=15 December 2014}}</ref> The team in charge of the Zen microarchitecture was led by [[Jim Keller (engineer)|Jim Keller]] until he left in September 2015 after a 3 year tenure.<ref name="anandtech">{{cite web|url=http://anandtech.com/show/9643/jim-keller-leaves-amd|title=Jim Keller Leaves AMD|publisher=anandtech.com|accessdate=2015-10-14}}</ref> Zen was originally planned for 2017 following the ARM64-based [[AMD K12|K12]] sister core, but on AMD's 2015 Financial Analyst Day it was revealed that K12 was delayed in favour of the Zen design for market entry in the 2016 timeframe.<ref name="Ryan Smith" />

==Architecture==
According to [[AMD]], Zen's main focus will be on increasing per-core performance rather than core count or multi-threading performance.<ref name="techspot">{{cite web|url=http://www.techspot.com/news/60626-tech-reading-amd-zen-comeback.html|title=Weekend tech reading: AMD 'Zen' and their return to high-end CPUs, tracking Windows pirates - TechSpot|publisher=techspot.com|accessdate=2015-05-12}}</ref><ref name="techreport">{{cite web|url=http://techreport.com/review/28228/amd-zen-chips-headed-to-desktops-servers-in-2016|title=AMD: Zen chips headed to desktops, servers in 2016 - The Tech Report - Page 1|publisher=techreport.com|accessdate=2015-05-12}}</ref><ref name="kitguru">{{cite news|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/ | work=KitGuru | title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be | date=11 September 2014 |author=Anton Shilov | accessdate=1 February 2015}}</ref> Reports from AMD indicate that Zen will abandon modular [[Bulldozer (microarchitecture)#CMT|CMT]] (Clustered Multithread) for a [[Simultaneous multithreading|SMT]] (Simultaneous Multithreading) microarchitecture,<ref name="WCCF Zen" /><ref>{{cite web|title=AMD 2015 comeback attempt: reforming high-performance processor, abandon modular architecture.|url=http://www.expreview.com/33161.html|publisher=Extreme Performance Review|accessdate=10 May 2015}}</ref> the model Intel uses. Adapting their chips from the less-popular CMT to SMT<ref name="Ryan Smith"/> is expected to offer much higher number threading efficiency, but also possibly increase the die size of Zen module.<ref name="kitguru" />

Reportedly, the Zen architecture will be built on a more efficient [[14 nanometer]] process, rather than the 32nm and 28nm processes of previous [[AMD FX]] CPUs and [[AMD Accelerated Processing Unit|AMD APUs]], respectively.<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading"/> It will feature a unified AM4 socket with its GPU-equipped APU counterparts,<ref name="pcgamer">{{cite web|url=http://www.pcgamer.com/amds-next-gen-zen-cpu-due-in-2016/|title=AMD's next-gen Zen CPU due in 2016 - PC Gamer|publisher=pcgamer.com|accessdate=2015-05-12}}</ref> and feature [[DDR4 SDRAM|DDR4]] support and a 95W [[Thermal design power|TDP]].<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading">{{cite news|url=http://news.softpedia.com/news/14nm-AMD-Zen-CPU-Will-Have-DDR4-and-Simultaneous-Multithreading-471401.shtml | publisher=Softpedia | title=14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading | date=28 January 2015 | accessdate=31 January 2015}}</ref> While newer roadmaps don't confirm the TDP for desktop products, they suggest a range for low-power mobile products with up to two Zen cores from 5 to 15W and 15 to 35W for performance-oriented mobile products with up to four Zen cores.<ref name="Shattered Media article">{{cite news| url=http://www.shattered.media/amds-next-gen-cpu-zen/ | publisher=Shattered.Media | title=AMD's next gen CPU Zen |date=May 2015}}</ref>

Zen will support [[RDSEED]].<ref name="AMD Starts Linux Enablement">{{cite news|url=http://www.phoronix.com/scan.php?page=news_item&px=AMD-Zen-CPU-Znver1 | publisher=Phoronix | title=AMD Starts Linux Enablement On Next-Gen "Zen" Architecture | date=17 March 2015 | accessdate=17 March 2015}}</ref>{{explain}}

Zen core will have four integer units, two address generation units and four floating point units, and the decoder can decode four instructions per clock cycle.
L1 cache size is 32 kiB and L2 cache size 512 kiB per core. Two of the floating point units are adders, two are multipliers.<ref name="dresdenboy">{{cite web|title=AMD's Zen core (family 17h) to have ten pipelines per core|url=http://dresdenboy.blogspot.fi/2015/10/amds-zen-core-family-17h-to-have-ten.html}}</ref>{{Unreliable source inline|certain=y|date=October 2015}}

{{quote box|align=right|width=35em|quote="It is the first time in a very long time that we engineers have been given the total freedom to build a processor from scratch and do the best we can do. It is a multi-year project with a really large team. It's like a marathon effort with some sprints in the middle. The team is working very hard, but they can see the finish line. I guarantee that it will deliver a huge improvement in performance and (low) power consumption over the previous generation."|source=—Suzanne Plummer, Zen team leader, on September 19th, 2015.<ref>http://www.mystatesman.com/news/business/amid-challenges-chipmnaker-amd-sees-a-way-forward/nngdf/</ref>}}

==History==
AMD began planning the Zen microarchitecture shortly after re-hiring [[Jim Keller (engineer)|Jim Keller]] in early 2012.<ref>{{cite av media|url=https://www.youtube.com/watch?v=SOTFE7sJY-Q|title=Jim Keller On AMD's Next-Gen High Performance x86 Zen Core & K12 ARM Core|date=7 May 2014|work=YouTube}}</ref>

The release of first Zen-based processors is expected in October 2016.<ref>{{cite news|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-set-to-release-first-zen-based-microprocessors-in-late-2016-document | website=KitGuru.net | title=AMD set to release first ‘Zen’-based microprocessors in late 2016 – document | date=12 June 2015 | accessdate=30 August 2015}}</ref>

Jim Keller left AMD on Sept. 18th, 2015. Jim was present at AMD for about three years, and it's assumed that Zen's design was completed prior to his departure.{{Citation needed|date=September 2015}}

==See also==
{{Portal|Computing}}

* [[Bulldozer (microarchitecture)]]
* [[Steamroller (microarchitecture)]]
* [[AMD K12]]

==References==
{{Reflist|40em}}

{{AMD processors|state=collapsed}}

[[Category:Advanced Micro Devices x86 microprocessors]]
[[Category:Advanced Micro Devices microarchitectures]]
[[Category:Upcoming integrated circuits]]

{{Comp-hardware-stub}}

Kubernetes

2015-10-18T13:33:52Z

Intgr: Tag article for sourcing issues; please add sources to satisfy WP:GNG.

{{Under construction}}
{{Multiple issues|
{{Single source|date=October 2015}}
{{Primary sources|date=October 2015}}
{{Notability|date=October 2015}}
}}
{{Infobox software
| name = Kubernetes
| title = Kubernetes
| logo = [[File:Kubernetes_(container_engine).png|75px]]
| screenshot =
| caption =
| collapsible =
| author =
| developer =
| released =
| discontinued =
| latest release version = 1.0.6<ref>{{cite web|url=https://github.com/kubernetes/kubernetes/releases |title=GitHub Releases page |work=github.com |date=2015-09-10}}</ref>
| latest release date = {{Start date and age|2015|09|10|df=yes/no}}
| latest preview version =
| latest preview date = 
| frequently updated = 
| programming language = [[Go (programming language)|Go]]
| operating system = [[Linux]]
| platform =
| language =
| status =
| genre = [[Operating system-level virtualization]]
| license = [[Apache License]] 2.0
| website = {{URL|http://kubernetes.io/}}
}}

'''Kubernetes''' is an [[open-source]] system for managing and deploying [[software container|containerized]] [[application software|application]]s across multiple hosts. It automatically determines which node in a cluster should receive each application ("pod" in Kubernetes lingo), based on their current workload. It also provides some means of discovery and communication between containers.

Kubernetes sits on top of virtualization software, such as [[Docker (software)|Docker]] or rkt; it is used to run the containers that are part of a pod.

== Concepts ==

* '''Cluster''': the set of machines on which Kubernetes will run the applications. Though Kubernetes was originally developed for Google Cloud Engine (under the name ''Borg''), it can now be used anywhere.
* '''Node''': one of the host machines that are part of the cluster, and onto which pods can be deployed and run.
* '''Pod''': a group of one or more containers is called a ''pod''. Containers in a pod share volumes, are deployed together, and are started, stopped and replicated as a group.
* '''Replication controller''': this is the controller that manage the lifetime of each pod. They ensure that a specified number of each pods are running, creating or killing pods to match the redundancy target.
* '''Service''': the abstraction through which a set of pods can be accessed (via service proxies), hiding the fact that they are not stable over time (as the replication controller create and destroy pods).
* '''Label''': key/value pairs attached to objects (such as pods) to dynamically select them (for instance, to assign them to a service)

== References ==
{{reflist}}

== External links ==
* {{Official website|http://kubernetes.io/}}
* [https://github.com/kubernetes/kubernetes Source code repository]

{{Virtualization|state=collapsed}}

[[Category:Free software]]
[[Category:Virtualization software]]
[[Category:Linux-only software]]
[[Category:Free software programmed in Go]]
[[Category:Virtualization-related software for Linux]]

Zen (Mikroarchitektur)

2015-10-14T13:50:31Z

Intgr: Fix apostrophes that aren't from source titles, per WP:'

{{Infobox CPU
| name = Zen
| image =
| image_size = 138px
| caption =
| produced-start = 2016+
| produced-end =
| designfirm = [[AMD]]
| manuf1 = [[Advanced Micro Devices|AMD]]
| size-from = 14 nm ([[Multigate device#FinFET|Bulk Silicon]])<ref name="WCCF Zen">{{cite web|last=Moammer |first=Khalid |url=http://wccftech.com/breaking-amds-gen-x86-high-performance-core-code-named-zen-debut-k12/ |title=AMD's Next Gen x86 High Performance Core is Zen |publisher=WCCF Tech | date=September 9, 2014 |accessdate=January 15, 2015}}</ref>
| predecessor = [[Excavator (microarchitecture)|Excavator Family 15h (4th-gen)]]
| successor =
| arch = [[X86-64#AMD64|AMD64]] ([[x86-64]])
| sock1 = [[Socket AM4]]<ref name="Ryan Smith">{{cite web |url=http://www.anandtech.com/show/9231/amds-20162017-x86-roadmap-zen-is-in|title=AMD’s 2016-2017 x86 Roadmap: Zen Is In, Skybridge Is Out |author=Ryan Smith |date={{date|2015-05-06}} |publisher=[[AnandTech]] }}</ref>
| application = Desktop, Laptop, Server
| core1 =
| TDP =
}}

'''Zen''' is an upcoming [[CPU]] microarchitecture created by [[AMD]].<ref name="AMD hints at high-performance Zen">{{cite news|url=http://www.bit-tech.net/news/hardware/2014/09/11/amd-zen/1 | publisher=bit-tech | title=AMD hints at high-performance Zen x86 architecture | date=11 September 2014 | accessdate=15 December 2014}}</ref> The team in charge of the Zen microarchitecture was led by [[Jim Keller (engineer)|Jim Keller]] until he left in September 2015 after a 3 year tenure.<ref name="anandtech">{{cite web|url=http://anandtech.com/show/9643/jim-keller-leaves-amd|title=Jim Keller Leaves AMD|publisher=anandtech.com|accessdate=2015-10-14}}</ref>. Zen was originally planned for 2017 following the ARM64-based [[AMD K12|K12]] sister core, but on AMD's 2015 Financial Analyst Day it was revealed that K12 was delayed in favour of the Zen design for market entry in the 2016 timeframe.<ref name="Ryan Smith" />

==Architecture==
According to [[AMD]], Zen's main focus will be on increasing per-core performance rather than core count or multi-threading performance.<ref name="techspot">{{cite web|url=http://www.techspot.com/news/60626-tech-reading-amd-zen-comeback.html|title=Weekend tech reading: AMD 'Zen' and their return to high-end CPUs, tracking Windows pirates - TechSpot|publisher=techspot.com|accessdate=2015-05-12}}</ref><ref name="techreport">{{cite web|url=http://techreport.com/review/28228/amd-zen-chips-headed-to-desktops-servers-in-2016|title=AMD: Zen chips headed to desktops, servers in 2016 - The Tech Report - Page 1|publisher=techreport.com|accessdate=2015-05-12}}</ref><ref name="kitguru">{{cite news|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/ | work=KitGuru | title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be | date=11 September 2014 |author=Anton Shilov | accessdate=1 February 2015}}</ref> Reports from AMD indicate that Zen will abandon modular [[Bulldozer (microarchitecture)#CMT|CMT]] (Clustered Multithread) for a [[Simultaneous multithreading|SMT]] (Simultaneous Multithreading) microarchitecture,<ref name="WCCF Zen" /><ref>{{cite web|title=AMD 2015 comeback attempt: reforming high-performance processor, abandon modular architecture.|url=http://www.expreview.com/33161.html|publisher=Extreme Performance Review|accessdate=10 May 2015}}</ref> the model Intel uses. Adapting their chips from the less-popular CMT to SMT<ref name="Ryan Smith"/> is expected to offer much higher number threading efficiency, but also possibly increase the die size of Zen module.<ref name="kitguru" />

Reportedly, the Zen architecture will be built on a more efficient [[14 nanometer]] process, rather than the 32nm and 28nm processes of previous [[AMD FX]] CPUs and [[AMD Accelerated Processing Unit|AMD APUs]], respectively.<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading"/> It will feature a unified AM4 socket with its GPU-equipped APU counterparts,<ref name="pcgamer">{{cite web|url=http://www.pcgamer.com/amds-next-gen-zen-cpu-due-in-2016/|title=AMD's next-gen Zen CPU due in 2016 - PC Gamer|publisher=pcgamer.com|accessdate=2015-05-12}}</ref> and feature [[DDR4 SDRAM|DDR4]] support and a 95W [[Thermal design power|TDP]].<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading">{{cite news|url=http://news.softpedia.com/news/14nm-AMD-Zen-CPU-Will-Have-DDR4-and-Simultaneous-Multithreading-471401.shtml | publisher=Softpedia | title=14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading | date=28 January 2015 | accessdate=31 January 2015}}</ref> While newer roadmaps don't confirm the TDP for desktop products, they suggest a range for low-power mobile products with up to two Zen cores from 5 to 15W and 15 to 35W for performance-oriented mobile products with up to four Zen cores.<ref name="Shattered Media article">{{cite news| url=http://www.shattered.media/amds-next-gen-cpu-zen/ | publisher=Shattered.Media | title=AMD's next gen CPU Zen |date=May 2015}}</ref>

Zen will support [[RDSEED]].<ref name="AMD Starts Linux Enablement">{{cite news|url=http://www.phoronix.com/scan.php?page=news_item&px=AMD-Zen-CPU-Znver1 | publisher=Phoronix | title=AMD Starts Linux Enablement On Next-Gen "Zen" Architecture | date=17 March 2015 | accessdate=17 March 2015}}</ref>{{explain}}

Zen core will have four integer units, two address generation units and four floating point units, and the decoder can decode four instructions per clock cycle.
L1 cache size is 32 kiB and L2 cache size 512 kiB per core. Two of the floating point units are adders, two are multipliers.<ref name="dresdenboy">{{cite web|title=AMD's Zen core (family 17h) to have ten pipelines per core|url=http://dresdenboy.blogspot.fi/2015/10/amds-zen-core-family-17h-to-have-ten.html}}</ref>{{Unreliable source inline|certain=y|date=October 2015}}

{{quote box|align=right|width=35em|quote="It is the first time in a very long time that we engineers have been given the total freedom to build a processor from scratch and do the best we can do. It is a multi-year project with a really large team. It's like a marathon effort with some sprints in the middle. The team is working very hard, but they can see the finish line. I guarantee that it will deliver a huge improvement in performance and (low) power consumption over the previous generation."|source=—Suzanne Plummer, Zen team leader, on September 19th, 2015.<ref>http://www.mystatesman.com/news/business/amid-challenges-chipmnaker-amd-sees-a-way-forward/nngdf/</ref>}}

==History==
AMD began planning the Zen microarchitecture shortly after re-hiring [[Jim Keller (engineer)|Jim Keller]] in early 2012.<ref>{{cite av media|url=https://www.youtube.com/watch?v=SOTFE7sJY-Q|title=Jim Keller On AMD's Next-Gen High Performance x86 Zen Core & K12 ARM Core|date=7 May 2014|work=YouTube}}</ref>

The release of first Zen-based processors is expected in October 2016.<ref>{{cite news|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-set-to-release-first-zen-based-microprocessors-in-late-2016-document | website=KitGuru.net | title=AMD set to release first ‘Zen’-based microprocessors in late 2016 – document | date=12 June 2015 | accessdate=30 August 2015}}</ref>

Jim Keller left AMD on Sept. 18th, 2015. Jim was present at AMD for about three years, and it's assumed that Zen's design was completed prior to his departure.{{Citation needed|date=September 2015}}

==See also==
{{Portal|Computing}}

* [[Bulldozer (microarchitecture)]]
* [[Steamroller (microarchitecture)]]
* [[AMD K12]]

==References==
{{Reflist|40em}}

{{AMD processors|state=collapsed}}

[[Category:Advanced Micro Devices x86 microprocessors]]
[[Category:Advanced Micro Devices microarchitectures]]
[[Category:Upcoming integrated circuits]]

{{Comp-hardware-stub}}

Zen (Mikroarchitektur)

2015-10-13T20:00:15Z

Intgr: /* Architecture */ Need a reliable source for these claims, WP:USERGENERATED

{{Infobox CPU
| name = Zen
| image =
| image_size = 138px
| caption =
| produced-start = 2016–2017
| produced-end =
| designfirm = [[AMD]]
| manuf1 = [[Advanced Micro Devices|AMD]]
| size-from = 14 nm ([[Multigate device#FinFET|Bulk Silicon]])<ref name="WCCF Zen">{{cite web|last=Moammer |first=Khalid |url=http://wccftech.com/breaking-amds-gen-x86-high-performance-core-code-named-zen-debut-k12/ |title=AMD's Next Gen x86 High Performance Core is Zen |publisher=WCCF Tech | date=September 9, 2014 |accessdate=January 15, 2015}}</ref>
| predecessor = [[Excavator (microarchitecture)|Excavator Family 15h (4th-gen)]]
| successor =
| arch = [[X86-64#AMD64|AMD64]] ([[x86-64]])
| sock1 = [[Socket AM4]]<ref name="Ryan Smith">{{cite web |url=http://www.anandtech.com/show/9231/amds-20162017-x86-roadmap-zen-is-in|title=AMD’s 2016-2017 x86 Roadmap: Zen Is In, Skybridge Is Out |author=Ryan Smith |date={{date|2015-05-06}} |publisher=[[AnandTech]] }}</ref>
| application = Desktop, Laptop, Server
| core1 =
| TDP =
}}

'''Zen''' is an upcoming [[CPU]] microarchitecture created by [[AMD]].<ref name="AMD hints at high-performance Zen">{{cite news|url=http://www.bit-tech.net/news/hardware/2014/09/11/amd-zen/1 | publisher=bit-tech | title=AMD hints at high-performance Zen x86 architecture | date=11 September 2014 | accessdate=15 December 2014}}</ref> The team in charge of the Zen microarchitecture was previously led by [[Jim Keller (engineer)|Jim Keller]], the engineer who recently left the company and is also responsible for the [[Athlon 64]].<ref name="techspot">{{cite web|url=http://www.techspot.com/news/60626-tech-reading-amd-zen-comeback.html|title=Weekend tech reading: AMD 'Zen' and their return to high-end CPUs, tracking Windows pirates - TechSpot|publisher=techspot.com|accessdate=2015-05-12}}</ref><ref name="techreport">{{cite web|url=http://techreport.com/review/28228/amd-zen-chips-headed-to-desktops-servers-in-2016|title=AMD: Zen chips headed to desktops, servers in 2016 - The Tech Report - Page 1|publisher=techreport.com|accessdate=2015-05-12}}</ref> Zen was originally planned for 2017 following the ARM64-based [[AMD K12|K12]] sister core, but on AMD’s 2015 Financial Analyst Day it was revealed that K12 was delayed in favour of the Zen design for market entry in the 2016 timeframe.<ref name="Ryan Smith" />

==Architecture==
According to [[AMD]], Zen's main focus will be on increasing per-core performance rather than core count or multi-threading performance.<ref name="kitguru">{{cite news|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/ | work=KitGuru | title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be | date=11 September 2014 |author=Anton Shilov | accessdate=1 February 2015}}</ref> Reports from AMD indicate that Zen will abandon modular [[Bulldozer (microarchitecture)#CMT|CMT]] (Clustered Multithread) for a [[Simultaneous multithreading|SMT]] (Simultaneous Multithreading) microarchitecture,<ref name="WCCF Zen" /><ref>{{cite web|title=AMD 2015 comeback attempt: reforming high-performance processor, abandon modular architecture.|url=http://www.expreview.com/33161.html|publisher=Extreme Performance Review|accessdate=10 May 2015}}</ref> the model Intel uses. Adapting their chips from the less-popular CMT to SMT<ref name="Ryan Smith"/> is expected to offer much higher number threading efficiency, but also possibly increase the die size of Zen module.<ref name="kitguru" />

Reportedly, the Zen architecture will be built on a more efficient [[14 nanometer]] process, rather than the 32nm and 28nm processes of previous [[AMD FX]] CPUs and [[AMD Accelerated Processing Unit|AMD APUs]], respectively.<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading"/> It will feature a unified AM4 socket with its GPU-equipped APU counterparts,<ref name="pcgamer">{{cite web|url=http://www.pcgamer.com/amds-next-gen-zen-cpu-due-in-2016/|title=AMD's next-gen Zen CPU due in 2016 - PC Gamer|publisher=pcgamer.com|accessdate=2015-05-12}}</ref> and feature [[DDR4 SDRAM|DDR4]] support and a 95W [[Thermal design power|TDP]].<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading">{{cite news|url=http://news.softpedia.com/news/14nm-AMD-Zen-CPU-Will-Have-DDR4-and-Simultaneous-Multithreading-471401.shtml | publisher=Softpedia | title=14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading | date=28 January 2015 | accessdate=31 January 2015}}</ref> While newer roadmaps don't confirm the TDP for desktop products, they suggest a range for low-power mobile products with up to two Zen cores from 5 to 15W and 15 to 35W for performance-oriented mobile products with up to four Zen cores.<ref name="Shattered Media article">{{cite news| url=http://www.shattered.media/amds-next-gen-cpu-zen/ | publisher=Shattered.Media | title=AMD's next gen CPU Zen |date=May 2015}}</ref>

Zen will support [[RDSEED]].<ref name="AMD Starts Linux Enablement">{{cite news|url=http://www.phoronix.com/scan.php?page=news_item&px=AMD-Zen-CPU-Znver1 | publisher=Phoronix | title=AMD Starts Linux Enablement On Next-Gen "Zen" Architecture | date=17 March 2015 | accessdate=17 March 2015}}</ref>{{explain}}

Zen core will have four integer units, two address generation units and four floating point units, and the decoder can decode four instructions per clock cycle.
L1 cache size is 32 kiB and L2 cache size 512 kiB per core. Two of the floating point units are adders, two are multipliers.<ref name="dresdenboy">{{cite web|title=AMD's Zen core (family 17h) to have ten pipelines per core|url=http://dresdenboy.blogspot.fi/2015/10/amds-zen-core-family-17h-to-have-ten.html}}</ref>{{Unreliable source inline|certain=y|date=October 2015}}

{{quote box|align=right|width=35em|quote="It is the first time in a very long time that we engineers have been given the total freedom to build a processor from scratch and do the best we can do. It is a multi-year project with a really large team. It’s like a marathon effort with some sprints in the middle. The team is working very hard, but they can see the finish line. I guarantee that it will deliver a huge improvement in performance and (low) power consumption over the previous generation."|source=—Suzanne Plummer, Zen team leader, on September 19th, 2015.<ref>http://www.mystatesman.com/news/business/amid-challenges-chipmnaker-amd-sees-a-way-forward/nngdf/</ref>}}

==History==
AMD began planning the Zen microarchitecture shortly after re-hiring [[Jim Keller (engineer)|Jim Keller]] in early 2012.<ref>{{cite av media|url=https://www.youtube.com/watch?v=SOTFE7sJY-Q|title=Jim Keller On AMD's Next-Gen High Performance x86 Zen Core & K12 ARM Core|date=7 May 2014|work=YouTube}}</ref>

The release of first Zen-based processors is expected in October 2016.<ref>{{cite news|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-set-to-release-first-zen-based-microprocessors-in-late-2016-document | website=KitGuru.net | title=AMD set to release first ‘Zen’-based microprocessors in late 2016 – document | date=12 June 2015 | accessdate=30 August 2015}}</ref>

Jim Keller left AMD on Sept. 18th, 2015. Jim was present at AMD for about three years, and it's assumed that Zen's design was completed prior to his departure.{{Citation needed|date=September 2015}}

==See also==
{{Portal|Computing}}

* [[Bulldozer (microarchitecture)]]
* [[Steamroller (microarchitecture)]]
* [[AMD K12]]

==References==
{{Reflist|40em}}

{{AMD processors|state=collapsed}}

[[Category:Advanced Micro Devices x86 microprocessors]]
[[Category:Advanced Micro Devices microarchitectures]]
[[Category:Upcoming integrated circuits]]

{{Comp-hardware-stub}}

Zen (Mikroarchitektur)

2015-09-21T20:47:49Z

Intgr: /* History */ Citation needed for this claim, "expected" by whom?

{{Infobox CPU
| name = Zen
| image =
| image_size = 138px
| caption =
| produced-start = 2016–2017
| produced-end =
| designfirm = [[AMD]]
| manuf1 = [[Advanced Micro Devices|AMD]]
| size-from = 14 nm ([[Multigate device#FinFET|Bulk Silicon]])<ref name="WCCF Zen">{{cite web|last=Moammer |first=Khalid |url=http://wccftech.com/breaking-amds-gen-x86-high-performance-core-code-named-zen-debut-k12/ |title=AMD's Next Gen x86 High Performance Core is Zen |publisher=WCCF Tech | date=September 9, 2014 |accessdate=January 15, 2015}}</ref>
| predecessor = [[Excavator (microarchitecture)|Excavator Family 15h (4th-gen)]]
| successor =
| arch = [[X86-64#AMD64|AMD64]] ([[x86-64]])
| sock1 = [[Socket AM4]]<ref name="Ryan Smith">{{cite web |url=http://www.anandtech.com/show/9231/amds-20162017-x86-roadmap-zen-is-in|title=AMD’s 2016-2017 x86 Roadmap: Zen Is In, Skybridge Is Out |author=Ryan Smith |date={{date|2015-05-06}} |publisher=[[AnandTech]] }}</ref>
| application = Desktop, Laptop, Server
| core1 =
| TDP =
}}

'''Zen''' is an upcoming [[CPU]] microarchitecture created by [[AMD]].<ref name="AMD hints at high-performance Zen">{{cite news|url=http://www.bit-tech.net/news/hardware/2014/09/11/amd-zen/1 | publisher=bit-tech | title=AMD hints at high-performance Zen x86 architecture | date=11 September 2014 | accessdate=15 December 2014}}</ref> The team in charge of the Zen microarchitecture was previosly led by [[Jim Keller (engineer)|Jim Keller]], the engineer who recently left the company and is also responsible for the [[Athlon 64]].<ref name="techspot">{{cite web|url=http://www.techspot.com/news/60626-tech-reading-amd-zen-comeback.html|title=Weekend tech reading: AMD 'Zen' and their return to high-end CPUs, tracking Windows pirates - TechSpot|publisher=techspot.com|accessdate=2015-05-12}}</ref><ref name="techreport">{{cite web|url=http://techreport.com/review/28228/amd-zen-chips-headed-to-desktops-servers-in-2016|title=AMD: Zen chips headed to desktops, servers in 2016 - The Tech Report - Page 1|publisher=techreport.com|accessdate=2015-05-12}}</ref> Zen was originally planned for 2017 following the ARM64-based [[AMD K12|K12]] sister core, but on AMD’s 2015 Financial Analyst Day it was revealed that K12 was delayed in favour of the Zen design for market entry in the 2016 timeframe.<ref name="Ryan Smith" />

==Architecture==
According to [[AMD]], Zen's main focus will be on increasing per-core performance rather than core count or multi-threading performance.<ref name="kitguru">{{cite news|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/ | work=KitGuru | title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be | date=11 September 2014 |author=Anton Shilov | accessdate=1 February 2015}}</ref> Reports from AMD indicate that Zen will abandon modular [[Bulldozer (microarchitecture)#CMT|CMT]] (Clustered Multithread) for a [[Simultaneous multithreading|SMT]] (Simultaneous Multithreading) microarchitecture,<ref name="WCCF Zen" /><ref>{{cite web|title=AMD 2015 comeback attempt: reforming high-performance processor, abandon modular architecture.|url=http://www.expreview.com/33161.html|publisher=Extreme Performance Review|accessdate=10 May 2015}}</ref> the model Intel uses. Adapting their chips from the less-popular CMT to SMT<ref name="Ryan Smith"/> is expected to offer much higher number threading efficiency, but also possibly increase the die size of Zen module.<ref name="kitguru" />

Reportedly, the Zen architecture will be built on a more efficient [[14 nanometer]] process, rather than the 32 nm and 28 nm processes of previous [[AMD FX]] CPUs and [[AMD Accelerated Processing Unit|AMD APUs]], respectively.<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading"/> It will feature a unified AM4 socket with its GPU-equipped APU counterparts,<ref name="pcgamer">{{cite web|url=http://www.pcgamer.com/amds-next-gen-zen-cpu-due-in-2016/|title=AMD's next-gen Zen CPU due in 2016 - PC Gamer|publisher=pcgamer.com|accessdate=2015-05-12}}</ref> and feature [[DDR4 SDRAM|DDR4]] support and 95 W [[Thermal design power|TDP]].<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading">{{cite news|url=http://news.softpedia.com/news/14nm-AMD-Zen-CPU-Will-Have-DDR4-and-Simultaneous-Multithreading-471401.shtml | publisher=Softpedia | title=14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading | date=28 January 2015 | accessdate=31 January 2015}}</ref> While newer roadmaps don't confirm the TDP for desktop products, they suggest a range for low-power mobile products with up to two Zen cores from 5 to 15 W and 15 to 35 W for performance-oriented mobile products with up to four Zen cores.<ref name="Shattered Media article">{{cite news| url=http://www.shattered.media/amds-next-gen-cpu-zen/ | publisher=Shattered.Media | title=AMD's next gen CPU Zen |date=May 2015}}</ref>

Zen will support [[RDSEED]].<ref name="AMD Starts Linux Enablement">{{cite news|url=http://www.phoronix.com/scan.php?page=news_item&px=AMD-Zen-CPU-Znver1 | publisher=Phoronix | title=AMD Starts Linux Enablement On Next-Gen "Zen" Architecture | date=17 March 2015 | accessdate=17 March 2015}}</ref>{{explain}}

==History==
AMD began planning the Zen microarchitecture shortly after re-hiring [[Jim Keller (engineer)|Jim Keller]] in early 2012.<ref>{{cite av media|url=https://www.youtube.com/watch?v=SOTFE7sJY-Q|title=Jim Keller On AMD's Next-Gen High Performance x86 Zen Core & K12 ARM Core|date=7 May 2014|work=YouTube}}</ref>

The release of first Zen-based processors is expected in October 2016.<ref>{{cite news|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-set-to-release-first-zen-based-microprocessors-in-late-2016-document | website=KitGuru.net | title=AMD set to release first ‘Zen’-based microprocessors in late 2016 – document | date=12 June 2015 | accessdate=30 August 2015}}</ref>

Jim Keller left AMD on Sept. 18th, 2015. Jim was present at AMD for about three years, and it's expected that Zen's design was completed prior to his departure.{{Citation needed|date=September 2015}}

==See also==
{{Portal|Computing}}

* [[Bulldozer (microarchitecture)]]
* [[Steamroller (microarchitecture)]]
* [[AMD K12]]

==References==
{{Reflist|40em}}

{{AMD processors|state=collapsed}}

[[Category:Advanced Micro Devices x86 microprocessors]]
[[Category:Advanced Micro Devices microarchitectures]]
[[Category:Upcoming integrated circuits]]

{{Comp-hardware-stub}}

Binärblob

2015-09-15T22:23:21Z

Intgr: Replace LWN.net SubscriberLink with ordinary link

{{About|drivers|the database data type|binary large object}}
{{Cleanup-rewrite|the article's POV and style is not neutral. It contains contradictory and confusing content|date=April 2012}}

In the context of [[Free and open source software|open-source software]], a '''binary blob''' is a [[Proprietary software|closed-source]] binary-only piece of software without publicly available [[source code]]. The term usually refers to a closed-source [[Loadable kernel module|kernel module]] [[Linker (computing)|loaded]] into the [[Kernel (computer science)|kernel]] of an open-source [[operating system]], and is sometimes also applied to code running outside the kernel, such as system [[firmware]] images, [[microcode]] updates, or [[User space|userland]] programs.<ref>{{cite web
| url = http://www.phoronix.com/scan.php?page=news_item&px=MTE1NDc
| title = Coreboot: Replacing Intel's Binary Video BIOS Blob
| date = 2012-08-06 | accessdate = 2015-06-23
| author = Michael Larabel | publisher = [[Phoronix]]
}}</ref><ref>{{cite web
| url = http://www.pcworld.com/article/2883903/how-intel-and-pc-makers-prevent-you-from-modifying-your-pcs-firmware.html
| title = How Intel and PC makers prevent you from modifying your laptop's firmware
| date = 2015-02-13 | accessdate = 2015-06-23
| author = Chris Hoffmann | website = pcworld.com
}}</ref><ref>{{cite web
| url = https://puri.sm/posts/bios-freedom-status/
| title = BIOS Freedom Status
| date = 2014-11-12 | accessdate = 2015-06-23
| website = puri.sm
}}</ref><ref>{{cite web
| url = http://www.phoronix.com/scan.php?page=news_item&px=MTIxNDk
| title = Raspberry Pi GPU Driver Turns Out To Be Crap
| date = 2012-10-24 | accessdate = 2015-06-23
| author = Michael Larabel | publisher = [[Phoronix]]
}}</ref><ref>{{cite web
| url = https://lwn.net/Articles/648392/
| title = Chromium suddenly starts downloading a binary blob
| date = 2015-06-17 | accessdate = 2015-06-23
| author = Jake Edge | publisher = [[LWN.net]]
}}</ref> The term ''[[Binary large object|blob]]'' was first used in [[database management system]]s to describe a collection of [[binary data]] stored as a single entity.

When [[computer hardware]] vendors provide complete technical documentation for their products, operating system developers are able to write hardware device drivers to be included in the operating system kernels. However, some vendors, such as [[NVIDIA#Documentation and drivers|NVIDIA]], do not provide complete documentation for some of their products and instead provide binary-only drivers (binary blobs); this practice is most common for [[GPU|accelerated graphics]] drivers, [[Network adapter|networking device]]s, and hardware [[RAID]] controllers.<ref>{{cite web | url = http://packages.debian.org/source/sid/firmware-nonfree | title = Debian packages built from the source package 'firmware-nonfree' - Binary firmware for various drivers in the Linux kernel | year = 2010 | accessdate = 2010-03-25}}</ref>

== Acceptance ==
Some projects try to create a free operating system, and will not accept binary blobs if they cannot get documentation for hardware or source code for device drivers; such projects include [[Trisquel]], [[Parabola GNU/Linux-libre|Parabola]] and [[LibreCMC]]. Other projects make a distinction between binary-only software and binary-only firmware, and hence distribute firmware blobs; such projects include [[NetBSD]], [[FreeBSD]], [[DragonFly BSD]], and some [[Linux distribution]]s.<ref name="bsdinterview">{{cite web | url = http://os.newsforge.com/os/05/06/09/2132233.shtml?tid=8&tid=2 | title = BSD cognoscenti on Linux | accessdate = 2006-07-07 | last = Matzan | first = Jem | date = 15 June 2005| publisher = NewsForge }} See Christos Zoulas's response to "Is sharing between Free/Open/NetBSD and the Linux kernel a common occurrence? And if so, does it go both ways?"</ref>

The [[OpenBSD]] project has a notable policy of not accepting any binary blobs into its source tree (however, OpenBSD distributes firmware blobs), citing not only the potential for undetectable or irreparable security flaws, but also the encroachment onto the openness and freedom of its software.<ref name="deraadt_interview_200605">{{citation
|url = http://kerneltrap.org/node/6550
|title = Interview: Theo de Raadt
|first = Jeremy
|last = Andrews
|work = [[KernelTrap]]
|publisher = Jeremy Andrews
|date = 2006-05-02
|archiveurl =
|archivedate =
}}</ref> The [[Free Software Foundation]] (FSF) is actively campaigning against binary blobs.<ref>{{cite web|url=http://www.fsf.org/blogs/community/rms-ati-protest.html|title=Protest against ATI nearly led to the arrest of RMS|date=27 April 2006|accessdate=2006-10-10|publisher=Free Software Foundation}}</ref> It also considers OpenBSD's policy confusingly worded, as "blobs" in the BSD community refer to what it considers non-free drivers, and not non-free firmware.<ref>{{cite web|url=https://www.gnu.org/distros/common-distros.html#BSD|title=Explaining Why We Don't Endorse Other Systems|date=July 13, 2011|accessdate=2011-09-10|publisher=GNU Project}}</ref> The [[Debian]] project included both free and non-free binary firmware blobs from the [[Linux kernel]], clearly marking and separating the non-free packages<ref>{{cite web | url = http://packages.debian.org/firmware-linux | title = Debian firmware-linux packages | year = 2010 | accessdate = 2010-03-25}}</ref> according to the [[Debian Social Contract]]. As of Debian 6.0 those blobs were removed.<ref>{{cite web | url =https://www.gnu.org/distros/common-distros.en.html#Debian | title = Explaining Why We Don't Endorse Other Systems # Debian | year = 2013 | accessdate = 2013-03-29}}</ref>

For OpenBSD, project leader Theo de Raadt defends the policy of only asking for distribution rights for microcode firmware blobs. "Once they are distributed... at least the device works." Implying that the alternative would be for the members of his small project to code free firmware themselves in the assembly language of many chipsets, he pleads "don't load us up with more tasks." Despite this he favours chipsets that run without firmware and speaks warmly of Asian designs which he describes as slower to market but more mature.<ref name="deraadt_interview_200605" />

In the [[Linux kernel]] development community, [[Linus Torvalds]] has made strong statements on the issue of binary-only modules, asserting: "I ''refuse'' to even consider tying my hands over some binary-only module", and continuing: "I want people to know that when they use binary-only modules, it's THEIR problem."<ref>{{cite web|url=http://lwn.net/1999/0211/a/lt-binary.html|title=a/lt-binary|work=lwn.net}}</ref> In 2008, 176 Linux kernel developers signed a ''Position Statement on Linux Kernel Modules'' that stated "We, the undersigned Linux kernel developers, consider any closed-source Linux kernel module or driver to be harmful and undesirable... We have repeatedly found them to be detrimental to Linux users, businesses, and the greater Linux ecosystem."<ref>{{cite web|url=http://lwn.net/Articles/287056/|title=A position statement on Linux Kernel Modules|date=June 2008|author=[[Greg Kroah-Hartman]]|publisher=[[The Linux Foundation]]}}</ref>

However, the Linux kernel contains numerous binary blobs, primarily containing closed-source firmwares required by various device drivers.<ref>{{cite web|url=https://www.gnu.org/distros/free-system-distribution-guidelines.html#nonfree-firmware|title=Free System Distribution Guidelines (GNU FSDG) - GNU Project - Free Software Foundation|work=gnu.org}}</ref><ref>{{cite web|url=https://www.gnu.org/distros/common-distros.html|title=Explaining Why We Don't Endorse Other Systems - GNU Project - Free Software Foundation|work=gnu.org}}</ref> Alexandre Oliva, the maintainer of [[Linux-libre]], a version of the Linux kernel that does not contain binary blobs, wrote in 2011: "Linux hasn't been Free Software since 1996, when Mr Torvalds accepted the first pieces of non-Free Software in the distributions of Linux he has published since 1991. Over these years, while this kernel grew by a factor of 14, the amount of non-Free firmware required by Linux drivers grew by an alarming factor of 83. We, Free Software users, need to join forces to reverse this trend, and part of the solution is Linux-libre, whose release 2.6.33-libre was recently published by FSFLA, bringing with it freedom, major improvements and plans for the future."<ref>{{cite web|url=http://www.fsfla.org/ikiwiki/anuncio/2010-03-Linux-2.6.33-libre.en|title=::[FSFLA]:: Take your freedom back, with Linux-2.6.33-libre|work=fsfla.org}}</ref>

== Legality ==
Prominent Linux kernel developer [[Greg Kroah-Hartman]] has stated that it is illegal to redistribute closed source modules for the GPL-licensed Linux kernel.<ref>{{cite web|url=http://www.kroah.com/log/linux/ols_2006_keynote.html|author=[[Greg Kroah-Hartman]]|publisher=[[Linux Symposium]]|title=Myths, Lies, and Truths about the Linux kernel|year=2006|quote=So, here's the simple answer to this issue: Closed source Linux kernel modules are illegal. That's it, it is very simple. I've had the misfortune of talking to a lot of different IP lawyers over the years about this topic, and every one that I've talked to all agree that there is no way that anyone can create a Linux kernel module, today, that can be closed source. It just violates the GPL due to fun things like derivative works and linking and other stuff. Again, it's very simple. Now no lawyer will ever come out in public and say this, as lawyer really aren't allowed to make public statements like this at all. But if you hire one, and talk to them in the client/lawyer setting, they will advise you of this issue.}}</ref>

== Problems ==
There are a number of reasons why binary blobs can be problematic.<ref>{{cite web | url = http://kerneltrap.org/node/6497 | first = Jeremy | last = Andrews | title = Interview with Jonathan Gray and Damien Bergamini | accessdate = 2008-01-06 | date = 2006-04-19 | publisher = kerneltrap.org }}</ref>

Firstly, their precise operation is not known and bugs cannot be detected by auditing source code, but are frequently only diagnosed by painstaking detective work when a system begins to behave unexpectedly. Such undetected bugs may also silently expose users and systems to security hazards. The fitness for purpose of the driver thus cannot be checked, and even if a bug is found there is no way to fix it.

Secondly, because the [[source code]] is not available the driver cannot be improved by its users, nor ported from one architecture to another not originally supported, nor adapted to operate slight variants of the hardware.

Thirdly, users are forced to trust vendors or malicious third parties not to put backdoors and spyware into the blob. Again on the theme of trust, the hardware vendor can decide not to support some operating systems, or to abandon driver maintenance at any time, or simply go out of business leaving the driver in limbo.

Finally, binary blobs drive a wedge between the portion of the community that believes in free software ideals and rejects the proprietary software, and the portion that sees open source as desirable for purely technical reasons and lacks a strong opposition to binary blobs "as long as they work". This fragmentation, and the acceptance of a growing number of proprietary components into Linux, weakens the ability of the community to resist the trend of manufacturers increasingly refusing to provide documentation for their hardware. At some point in the future, it may become infeasible to run a truly free operating system on most PCs.

== Use via wrappers ==
A [[Driver wrapper|wrapper]] is software which allows one operating system to use a binary blob driver written for another operating system. Examples of wrappers are [[NdisWrapper]] for [[Linux]], and [[Project Evil]] for [[FreeBSD]] and [[NetBSD]]. These wrappers allow these operating systems to use network drivers written for [[Microsoft Windows]] by implementing [[Microsoft]]'s [[Network Driver Interface Specification|NDIS]] [[Application programming interface|API]].

== Device firmware ==
[[Firmware]], the software required by the onboard [[microcontroller]]s that accompany some hardware, is generally not considered to be a binary blob{{Citation needed|date=September 2013}}. In many devices, firmware is stored in [[non-volatile]] onboard [[flash memory]], but to decrease costs and ease upgrades, some devices contain only [[static RAM]] and require the host operating system to upload firmware each time they are connected (especially [[USB]] devices). Although the firmware is thus present in the operating system driver, it is merely copied to the device and not executed by the CPU, lessening concerns about hidden security flaws{{Citation needed|date=October 2014}}. The OpenBSD project accepts binary firmware images and will redistribute these images if the license permits.<ref>{{cite web | title = OpenBSD Works To Open Wireless Chipsets|date = November 2, 2004|publisher=KernelTrap|url = http://kerneltrap.org/node/4118 | accessdate = 2006-06-23}}</ref>

== BIOS ==
The [[BIOS]], which functions as a [[bootloader]] and supports legacy [[real mode]] applications, is a crucial component of many [[IBM-compatible]] computers. The BIOS is always 16-bit, often has networking functions, and can be a security [[Backdoor (computing)|backdoor]] (sometimes deliberate,<ref>{{cite web|url=http://www.intel.com/content/www/us/en/architecture-and-technology/vpro/vpro-technology-general.html |title=Intel vPro Technology |publisher=Intel.com |date=2012-05-14 |accessdate=2014-04-10}}</ref><ref>{{cite web|url=http://www.absolute.com/en/partners/bios-compatibility.aspx |title=BIOS & Firmware Compatibility |publisher=Absolute.com |date= |accessdate=2014-04-10}}</ref>{{failed verification|date=April 2014}} and the operating system has no control over this backdoor).<ref>as per IBM PC specs</ref> The FSF promotes [[libreboot]] in its campaign for free BIOS firmware.<ref>{{cite web|url=http://www.fsf.org/campaigns/free-bios.html|title=Campaign for Free BIOS|publisher=Free Software Foundation|date=2006-11-29|accessdate=2007-01-02}}</ref>

== See also ==
{{Portal|Free software}}

{{Div col||22em}}
* [[Loadable kernel module]]
* [[Graphics hardware and FOSS]]
* [[Wireless security]]
* [[Proprietary firmware]]
* [[Proprietary software]]
* [[Opaque binary blob]]
{{Div col end}}

== References ==
{{Reflist|30em}}

== External links ==
{{Wiktionary|blob}}

* {{cite web|last = McMillan|first = Robert|date = June 21, 2006|url = http://www.infoworld.com/article/06/06/21/79536_HNwifibreach_1.html|title = Researchers hack Wi-Fi driver to breach laptop|publisher = InfoWorld|accessdate = 2006-06-23}}
* [http://kerneltrap.org/node/6650 KernelTrap article] on Damien Bergamini's wpi(4) driver, a blobless ipw3945 alternative for OpenBSD
* [http://kerneltrap.org/node/6497 KernelTrap interview] with Jonathan Gray and Damien Bergamini regarding binary blobs
* [http://blog.washingtonpost.com/securityfix/2006/08/the_macbook_wireless_exploit_i.html The Black Hat Wireless Exploit Interview, Verbatim] by Brian Krebs on the Washington Post's website, http://washingtonpost.com


{{FOSS}}

[[Category:OpenBSD]]
[[Category:Free software culture and documents]]
[[Category:Pejoratives]]

Zen (Mikroarchitektur)

2015-09-15T20:31:43Z

Intgr: Collapse citations for same source, found another one

{{Infobox CPU
| name = Zen
| image =
| image_size = 138px
| caption =
| produced-start = 2016–2017
| produced-end =
| designfirm = [[AMD]]
| manuf1 = [[Advanced Micro Devices|AMD]]
| size-from = 14 nm ([[Multigate device#FinFET|Bulk Silicon]])<ref name="WCCF Zen">{{cite web|last=Moammer |first=Khalid |url=http://wccftech.com/breaking-amds-gen-x86-high-performance-core-code-named-zen-debut-k12/ |title=AMD's Next Gen x86 High Performance Core is Zen |publisher=WCCF Tech | date=September 9, 2014 |accessdate=January 15, 2015}}</ref>
| predecessor = [[Excavator (microarchitecture)|Excavator Family 15h (4th-gen)]]
| successor =
| arch = [[X86-64#AMD64|AMD64]] ([[x86-64]])
| sock1 = [[Socket AM4]]<ref name="Ryan Smith">{{cite web |url=http://www.anandtech.com/show/9231/amds-20162017-x86-roadmap-zen-is-in|title=AMD’s 2016-2017 x86 Roadmap: Zen Is In, Skybridge Is Out |author=Ryan Smith |date={{date|2015-05-06}} |publisher=[[AnandTech]] }}</ref>
| application = Desktop, Laptop, Server
| core1 =
| TDP =
}}

'''Zen''' is an upcoming [[CPU]] microarchitecture created by [[AMD]].<ref name="AMD hints at high-performance Zen">{{cite news|url=http://www.bit-tech.net/news/hardware/2014/09/11/amd-zen/1 | publisher=bit-tech | title=AMD hints at high-performance Zen x86 architecture | date=11 September 2014 | accessdate=15 December 2014}}</ref> The team in charge of the Zen microarchitecture is being led by [[Jim Keller (engineer)|Jim Keller]], the engineer also responsible for the [[Athlon 64]].<ref name="techspot">{{cite web|url=http://www.techspot.com/news/60626-tech-reading-amd-zen-comeback.html|title=Weekend tech reading: AMD 'Zen' and their return to high-end CPUs, tracking Windows pirates - TechSpot|publisher=techspot.com|accessdate=2015-05-12}}</ref><ref name="techreport">{{cite web|url=http://techreport.com/review/28228/amd-zen-chips-headed-to-desktops-servers-in-2016|title=AMD: Zen chips headed to desktops, servers in 2016 - The Tech Report - Page 1|publisher=techreport.com|accessdate=2015-05-12}}</ref> Zen was originally planned for 2017 following the ARM64-based [[AMD K12|K12]] sister core, but on AMD’s 2015 Financial Analyst Day it was revealed that K12 was delayed in favour of the Zen design for market entry in the 2016 timeframe.<ref name="Ryan Smith" />

==Architecture==
According to [[AMD]], Zen's main focus will be on increasing per-core performance rather than core count or multi-threading performance.<ref name="kitguru">{{cite news|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/ | work=KitGuru | title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be | date=11 September 2014 |author=Anton Shilov | accessdate=1 February 2015}}</ref> Reports from AMD indicate that Zen will abandon modular [[Bulldozer (microarchitecture)#CMT|CMT]] (Clustered Multithread) for a [[Simultaneous multithreading|SMT]] (Simultaneous Multithreading) microarchitecture,<ref name="WCCF Zen" /><ref>{{cite web|title=AMD 2015 comeback attempt: reforming high-performance processor, abandon modular architecture.|url=http://www.expreview.com/33161.html|publisher=Extreme Performance Review|accessdate=10 May 2015}}</ref> the model Intel uses. Adapting their chips from the less-popular CMT to SMT<ref name="Ryan Smith"/> is expected to offer much higher number threading efficiency, but also possibly increase the die size of Zen module.<ref name="kitguru" />

Reportedly, the Zen architecture will be built on a more efficient [[14 nanometer]] process, rather than the 32 nm and 28 nm processes of previous [[AMD FX]] CPUs and [[AMD Accelerated Processing Unit|AMD APUs]], respectively.<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading"/> It will feature a unified AM4 socket with its GPU-equipped APU counterparts,<ref name="pcgamer">{{cite web|url=http://www.pcgamer.com/amds-next-gen-zen-cpu-due-in-2016/|title=AMD's next-gen Zen CPU due in 2016 - PC Gamer|publisher=pcgamer.com|accessdate=2015-05-12}}</ref> and feature [[DDR4 SDRAM|DDR4]] support and 95 W [[Thermal design power|TDP]].<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading">{{cite news|url=http://news.softpedia.com/news/14nm-AMD-Zen-CPU-Will-Have-DDR4-and-Simultaneous-Multithreading-471401.shtml | publisher=Softpedia | title=14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading | date=28 January 2015 | accessdate=31 January 2015}}</ref> While newer roadmaps don't confirm the TDP for desktop products, they suggest a range for low-power mobile products with up to two Zen cores from 5 to 15 W and 15 to 35 W for performance-oriented mobile products with up to four Zen cores.<ref name="Shattered Media article">{{cite news| url=http://www.shattered.media/amds-next-gen-cpu-zen/ | publisher=Shattered.Media | title=AMD's next gen CPU Zen |date=May 2015}}</ref>

Zen will support [[RDSEED]].<ref name="AMD Starts Linux Enablement">{{cite news|url=http://www.phoronix.com/scan.php?page=news_item&px=AMD-Zen-CPU-Znver1 | publisher=Phoronix | title=AMD Starts Linux Enablement On Next-Gen "Zen" Architecture | date=17 March 2015 | accessdate=17 March 2015}}</ref>{{explain}}

==History==
AMD began planning the Zen microarchitecture shortly after re-hiring [[Jim Keller (engineer)|Jim Keller]] in early 2012.<ref>{{cite av media|url=https://www.youtube.com/watch?v=SOTFE7sJY-Q|title=Jim Keller On AMD's Next-Gen High Performance x86 Zen Core & K12 ARM Core|date=7 May 2014|work=YouTube}}</ref>

The release of first Zen-based processors is expected in October 2016.<ref>{{cite news|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-set-to-release-first-zen-based-microprocessors-in-late-2016-document | website=KitGuru.net | title=AMD set to release first ‘Zen’-based microprocessors in late 2016 – document | date=12 June 2015 | accessdate=30 August 2015}}</ref>

==See also==
{{Portal|Computing}}

* [[Bulldozer (microarchitecture)]]
* [[Steamroller (microarchitecture)]]
* [[AMD K12]]

==References==
{{Reflist|40em}}

{{AMD processors|state=collapsed}}

[[Category:Advanced Micro Devices x86 microprocessors]]
[[Category:Advanced Micro Devices microarchitectures]]

{{Comp-hardware-stub}}

Zen (Mikroarchitektur)

2015-09-15T20:28:36Z

Intgr: Collapse citations for same source

{{Infobox CPU
| name = Zen
| image =
| image_size = 138px
| caption =
| produced-start = 2016–2017
| produced-end =
| designfirm = [[AMD]]
| manuf1 = [[Advanced Micro Devices|AMD]]
| size-from = 14 nm ([[Multigate device#FinFET|Bulk Silicon]])<ref name="WCCF Zen">{{cite web|last=Moammer |first=Khalid |url=http://wccftech.com/breaking-amds-gen-x86-high-performance-core-code-named-zen-debut-k12/ |title=AMD's Next Gen x86 High Performance Core is Zen |publisher=WCCF Tech | date=September 9, 2014 |accessdate=January 15, 2015}}</ref>
| predecessor = [[Excavator (microarchitecture)|Excavator Family 15h (4th-gen)]]
| successor =
| arch = [[X86-64#AMD64|AMD64]] ([[x86-64]])
| sock1 = [[Socket AM4]]<ref>{{cite web |url=http://www.anandtech.com/show/9231/amds-20162017-x86-roadmap-zen-is-in|title=AMD’s 2016-2017 x86 Roadmap: Zen Is In, Skybridge Is Out |author=Ryan Smith |date={{date|2015-05-06}} |publisher=[[AnandTech]] }}</ref>
| application = Desktop, Laptop, Server
| core1 =
| TDP =
}}

'''Zen''' is an upcoming [[CPU]] microarchitecture created by [[AMD]].<ref name="AMD hints at high-performance Zen">{{cite news|url=http://www.bit-tech.net/news/hardware/2014/09/11/amd-zen/1 | publisher=bit-tech | title=AMD hints at high-performance Zen x86 architecture | date=11 September 2014 | accessdate=15 December 2014}}</ref> The team in charge of the Zen microarchitecture is being led by [[Jim Keller (engineer)|Jim Keller]], the engineer also responsible for the [[Athlon 64]].<ref name="techspot">{{cite web|url=http://www.techspot.com/news/60626-tech-reading-amd-zen-comeback.html|title=Weekend tech reading: AMD 'Zen' and their return to high-end CPUs, tracking Windows pirates - TechSpot|publisher=techspot.com|accessdate=2015-05-12}}</ref><ref name="techreport">{{cite web|url=http://techreport.com/review/28228/amd-zen-chips-headed-to-desktops-servers-in-2016|title=AMD: Zen chips headed to desktops, servers in 2016 - The Tech Report - Page 1|publisher=techreport.com|accessdate=2015-05-12}}</ref> Zen was originally planned for 2017 following the ARM64-based [[AMD K12|K12]] sister core, but on AMD’s 2015 Financial Analyst Day it was revealed that K12 was delayed in favour of the Zen design for market entry in the 2016 timeframe.<ref name="Ryan Smith">{{cite web|last1=Smith|first1=Ryan|title=AMD's 2016-2017 x86 Roadmap: Zen Is In, Skybridge Is Out|url=http://www.anandtech.com/show/9231/amds-20162017-x86-roadmap-zen-is-in|publisher=Anandtech|accessdate=10 May 2015}}</ref>

==Architecture==
According to [[AMD]], Zen's main focus will be on increasing per-core performance rather than core count or multi-threading performance.<ref name="kitguru">{{cite news|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/ | work=KitGuru | title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be | date=11 September 2014 |author=Anton Shilov | accessdate=1 February 2015}}</ref> Reports from AMD indicate that Zen will abandon modular [[Bulldozer (microarchitecture)#CMT|CMT]] (Clustered Multithread) for a [[Simultaneous multithreading|SMT]] (Simultaneous Multithreading) microarchitecture,<ref name="WCCF Zen" /><ref>{{cite web|title=AMD 2015 comeback attempt: reforming high-performance processor, abandon modular architecture.|url=http://www.expreview.com/33161.html|publisher=Extreme Performance Review|accessdate=10 May 2015}}</ref> the model Intel uses. Adapting their chips from the less-popular CMT to SMT<ref name="Ryan Smith"/> is expected to offer much higher number threading efficiency, but also possibly increase the die size of Zen module.<ref name="kitguru" />

Reportedly, the Zen architecture will be built on a more efficient [[14 nanometer]] process, rather than the 32 nm and 28 nm processes of previous [[AMD FX]] CPUs and [[AMD Accelerated Processing Unit|AMD APUs]], respectively.<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading"/> It will feature a unified AM4 socket with its GPU-equipped APU counterparts,<ref name="pcgamer">{{cite web|url=http://www.pcgamer.com/amds-next-gen-zen-cpu-due-in-2016/|title=AMD's next-gen Zen CPU due in 2016 - PC Gamer|publisher=pcgamer.com|accessdate=2015-05-12}}</ref> and feature [[DDR4 SDRAM|DDR4]] support and 95 W [[Thermal design power|TDP]].<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading">{{cite news|url=http://news.softpedia.com/news/14nm-AMD-Zen-CPU-Will-Have-DDR4-and-Simultaneous-Multithreading-471401.shtml | publisher=Softpedia | title=14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading | date=28 January 2015 | accessdate=31 January 2015}}</ref> While newer roadmaps don't confirm the TDP for desktop products, they suggest a range for low-power mobile products with up to two Zen cores from 5 to 15 W and 15 to 35 W for performance-oriented mobile products with up to four Zen cores.<ref name="Shattered Media article">{{cite news| url=http://www.shattered.media/amds-next-gen-cpu-zen/ | publisher=Shattered.Media | title=AMD's next gen CPU Zen |date=May 2015}}</ref>

Zen will support [[RDSEED]].<ref name="AMD Starts Linux Enablement">{{cite news|url=http://www.phoronix.com/scan.php?page=news_item&px=AMD-Zen-CPU-Znver1 | publisher=Phoronix | title=AMD Starts Linux Enablement On Next-Gen "Zen" Architecture | date=17 March 2015 | accessdate=17 March 2015}}</ref>{{explain}}

==History==
AMD began planning the Zen microarchitecture shortly after re-hiring [[Jim Keller (engineer)|Jim Keller]] in early 2012.<ref>{{cite av media|url=https://www.youtube.com/watch?v=SOTFE7sJY-Q|title=Jim Keller On AMD's Next-Gen High Performance x86 Zen Core & K12 ARM Core|date=7 May 2014|work=YouTube}}</ref>

The release of first Zen-based processors is expected in October 2016.<ref>{{cite news|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-set-to-release-first-zen-based-microprocessors-in-late-2016-document | website=KitGuru.net | title=AMD set to release first ‘Zen’-based microprocessors in late 2016 – document | date=12 June 2015 | accessdate=30 August 2015}}</ref>

==See also==
{{Portal|Computing}}

* [[Bulldozer (microarchitecture)]]
* [[Steamroller (microarchitecture)]]
* [[AMD K12]]

==References==
{{Reflist|40em}}

{{AMD processors|state=collapsed}}

[[Category:Advanced Micro Devices x86 microprocessors]]
[[Category:Advanced Micro Devices microarchitectures]]

{{Comp-hardware-stub}}

Zen (Mikroarchitektur)

2015-09-15T20:25:56Z

Intgr: Revert, contradicts source. Undid revision 681201292 by 128.172.34.3 (talk)

{{Infobox CPU
| name = Zen
| image =
| image_size = 138px
| caption =
| produced-start = 2016–2017
| produced-end =
| designfirm = [[AMD]]
| manuf1 = [[Advanced Micro Devices|AMD]]
| size-from = 14 nm ([[Multigate device#FinFET|Bulk Silicon]])<ref name="WCCF Zen">{{cite web|last=Moammer |first=Khalid |url=http://wccftech.com/breaking-amds-gen-x86-high-performance-core-code-named-zen-debut-k12/ |title=AMD's Next Gen x86 High Performance Core is Zen |publisher=WCCF Tech | date=September 9, 2014 |accessdate=January 15, 2015}}</ref>
| predecessor = [[Excavator (microarchitecture)|Excavator Family 15h (4th-gen)]]
| successor =
| arch = [[X86-64#AMD64|AMD64]] ([[x86-64]])
| sock1 = [[Socket AM4]]<ref>{{cite web |url=http://www.anandtech.com/show/9231/amds-20162017-x86-roadmap-zen-is-in|title=AMD’s 2016-2017 x86 Roadmap: Zen Is In, Skybridge Is Out |author=Ryan Smith |date={{date|2015-05-06}} |publisher=[[AnandTech]] }}</ref>
| application = Desktop, Laptop, Server
| core1 =
| TDP =
}}

'''Zen''' is an upcoming [[CPU]] microarchitecture created by [[AMD]].<ref name="AMD hints at high-performance Zen">{{cite news|url=http://www.bit-tech.net/news/hardware/2014/09/11/amd-zen/1 | publisher=bit-tech | title=AMD hints at high-performance Zen x86 architecture | date=11 September 2014 | accessdate=15 December 2014}}</ref> The team in charge of the Zen microarchitecture is being led by [[Jim Keller (engineer)|Jim Keller]], the engineer also responsible for the [[Athlon 64]].<ref name="techspot">{{cite web|url=http://www.techspot.com/news/60626-tech-reading-amd-zen-comeback.html|title=Weekend tech reading: AMD 'Zen' and their return to high-end CPUs, tracking Windows pirates - TechSpot|publisher=techspot.com|accessdate=2015-05-12}}</ref><ref name="techreport">{{cite web|url=http://techreport.com/review/28228/amd-zen-chips-headed-to-desktops-servers-in-2016|title=AMD: Zen chips headed to desktops, servers in 2016 - The Tech Report - Page 1|publisher=techreport.com|accessdate=2015-05-12}}</ref> Zen was originally planned for 2017 following the ARM64-based [[AMD K12|K12]] sister core, but on AMD’s 2015 Financial Analyst Day it was revealed that K12 was delayed in favour of the Zen design for market entry in the 2016 timeframe.<ref name="Ryan Smith">{{cite web|last1=Smith|first1=Ryan|title=AMD's 2016-2017 x86 Roadmap: Zen Is In, Skybridge Is Out|url=http://www.anandtech.com/show/9231/amds-20162017-x86-roadmap-zen-is-in|publisher=Anandtech|accessdate=10 May 2015}}</ref>

==Architecture==
According to [[AMD]], Zen's main focus will be on increasing per-core performance rather than core count or multi-threading performance.<ref name="kitguru">{{cite web|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/|title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be | KitGuru|publisher=kitguru.net|accessdate=2015-05-12}}</ref> Reports from AMD indicate that Zen will abandon modular [[Bulldozer (microarchitecture)#CMT|CMT]] (Clustered Multithread) for a [[Simultaneous multithreading|SMT]] (Simultaneous Multithreading) microarchitecture,<ref name="WCCF Zen" /><ref>{{cite web|title=AMD 2015 comeback attempt: reforming high-performance processor, abandon modular architecture.|url=http://www.expreview.com/33161.html|publisher=Extreme Performance Review|accessdate=10 May 2015}}</ref> the model Intel uses. Adapting their chips from the less-popular CMT to SMT<ref name="Ryan Smith"/> is expected to offer much higher number threading efficiency, but also possibly increase the die size of Zen module.<ref name="AMD: ‘Bulldozer’ was not a game-changer">{{cite news|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/ | publisher=KitGuru | title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be | date=11 September 2014 | accessdate=1 February 2015}}</ref>

Reportedly, the Zen architecture will be built on a more efficient [[14 nanometer]] process, rather than the 32 nm and 28 nm processes of previous [[AMD FX]] CPUs and [[AMD Accelerated Processing Unit|AMD APUs]], respectively.<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading"/> It will feature a unified AM4 socket with its GPU-equipped APU counterparts,<ref name="pcgamer">{{cite web|url=http://www.pcgamer.com/amds-next-gen-zen-cpu-due-in-2016/|title=AMD's next-gen Zen CPU due in 2016 - PC Gamer|publisher=pcgamer.com|accessdate=2015-05-12}}</ref> and feature [[DDR4 SDRAM|DDR4]] support and 95 W [[Thermal design power|TDP]].<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading">{{cite news|url=http://news.softpedia.com/news/14nm-AMD-Zen-CPU-Will-Have-DDR4-and-Simultaneous-Multithreading-471401.shtml | publisher=Softpedia | title=14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading | date=28 January 2015 | accessdate=31 January 2015}}</ref> While newer roadmaps don't confirm the TDP for desktop products, they suggest a range for low-power mobile products with up to two Zen cores from 5 to 15 W and 15 to 35 W for performance-oriented mobile products with up to four Zen cores.<ref name="Shattered Media article">{{cite news| url=http://www.shattered.media/amds-next-gen-cpu-zen/ | publisher=Shattered.Media | title=AMD's next gen CPU Zen |date=May 2015}}</ref>

Zen will support [[RDSEED]].<ref name="AMD Starts Linux Enablement">{{cite news|url=http://www.phoronix.com/scan.php?page=news_item&px=AMD-Zen-CPU-Znver1 | publisher=Phoronix | title=AMD Starts Linux Enablement On Next-Gen "Zen" Architecture | date=17 March 2015 | accessdate=17 March 2015}}</ref>{{explain}}

==History==
AMD began planning the Zen microarchitecture shortly after re-hiring [[Jim Keller (engineer)|Jim Keller]] in early 2012.<ref>{{cite av media|url=https://www.youtube.com/watch?v=SOTFE7sJY-Q|title=Jim Keller On AMD's Next-Gen High Performance x86 Zen Core & K12 ARM Core|date=7 May 2014|work=YouTube}}</ref>

The release of first Zen-based processors is expected in October 2016.<ref>{{cite news|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-set-to-release-first-zen-based-microprocessors-in-late-2016-document | website=KitGuru.net | title=AMD set to release first ‘Zen’-based microprocessors in late 2016 – document | date=12 June 2015 | accessdate=30 August 2015}}</ref>

==See also==
{{Portal|Computing}}

* [[Bulldozer (microarchitecture)]]
* [[Steamroller (microarchitecture)]]
* [[AMD K12]]

==References==
{{Reflist|40em}}

{{AMD processors|state=collapsed}}

[[Category:Advanced Micro Devices x86 microprocessors]]
[[Category:Advanced Micro Devices microarchitectures]]

{{Comp-hardware-stub}}

Jim Keller

2015-08-17T07:22:48Z

Intgr: rephrase

{{Infobox person
| name = Jim Keller
| image = 
| alt =
| caption =
| birth_name = 
| birth_date = 
| birth_place =
| death_date = 
| death_place =
| nationality =
| other_names =
| occupation = Chief Architect of Microprocessor Cores and Corporate Vice President, Advanced Micro Devices<ref>{{cite web |url=http://www.bloomberg.com/research/stocks/people/person.asp?personId=215060089&ticker=AMD&previousCapId=168864&previousTitle=ADVANCED%20MICRO%20DEVICES |title=Jim Keller: Executive Profile & Biography |work=[[Bloomberg Business]] |accessdate={{date|2015-05-14}} }}</ref><ref name=bit-tech>{{cite web |url=http://www.bit-tech.net/news/hardware/2012/08/02/amd-jim-keller/1 |title=AMD re-hires Athlon 64 K8 designer Jim Keller |author=Gareth Halfacree |date=2 August 2012 |work=bit-tech }}</ref>
| years_active =
| known_for = {{Plainlist|
* AMD K7
* AMD K8 (lead architect)
* Apple A4, A5
* x86-64 (coauthor)
* HyperTransport (coauthor)
}}
| notable_works =
}}

'''Jim Keller''' is a [[microprocessor]] [[engineer]] most well known for his work at [[AMD]] and [[Apple Inc.|Apple]]. He was the lead architect of [[AMD K8]] microarchitecture<ref name=anandtech>{{cite news |url=http://www.anandtech.com/show/6129/apple-a4a5-designer-k8-lead-architect-jim-keller-returns-to-amd |title=Apple A4/A5 Designer & K8 Lead Architect, Jim Keller, Returns to AMD |author=[[Anand Lal Shimpi]] |date=1 August 2012 |work=[[AnandTech]] }}</ref><ref name=xbitlabs>{{cite news |url=http://www.xbitlabs.com/news/cpu/display/20120801190422_Return_of_the_King_AMD_K7_and_K8_Designer_Jim_Keller_Back_at_AMD.html |title=Return of the King: AMD K7 and K8 Designer Jim Keller Back at AMD |author=Anton Shilov |date=1 August 2012 |work=X-bit Labs }}</ref><ref name=computing>{{cite news |url=http://www.computing.co.uk/ctg/news/2344223/amd-to-design-new-micro-architecture-for-2015-launch-under-chip-guru-jim-keller |title=AMD to design new micro-architecture for 2015 launch under chip guru Jim Keller |author=Graeme Burton |date=12 May 2014 |work=computing.co.uk }}</ref> (including the original [[Athlon 64]])<ref name=anandtech /><ref name=thenextweb>{{cite news |url=http://thenextweb.com/insider/2012/08/01/apples-cpu-architect-jim-keller-departs-to-head-up-chipmaker-amds-processor-group/ |title=Apple's CPU Architect Jim Keller Jumps To AMD |author=Robin Wauters |date=1 August 2012 |work=[[The Next Web]] }}</ref><ref name=cultofmac>{{cite news |url=http://www.cultofmac.com/182296/amd-hires-ax-series-architect-jim-keller-away-from-apple-to-report-to-mark-papermaster/ |title=AMD Hires Ax Series Architect Jim Keller Away From Apple To Report To Mark Papermaster |author=John Brownlee |date=1 August 2012 |work=Cult of Mac}}</ref> and was involved in designing the [[Athlon]] (K7)<ref name=computing /> and [[Apple A4]]/[[Apple A5|A5]] processors.<ref name=anandtech /><ref name=venturebeat>{{cite news |url=http://venturebeat.com/2012/08/01/apple-cpu-jim-keller-amd/ |title=Apple CPU lead Jim Keller heads back to AMD as chief architect |author=Devindra Hardawar |date=1 August 2012 |work=[[VentureBeat]] }}</ref><ref name=theverge>{{cite news |url=http://www.theverge.com/2012/8/1/3212406/jim-keller-joins-amd-vp-chief-architect |title=Former Apple chip designer Jim Keller joins AMD as chief architect and VP |author=Adi Robertson |date=1 August 2012 |publisher=Vox Media |work=[[The Verge]] }}</ref><ref name=allthingsd>{{cite news |url=http://allthingsd.com/20120801/amd-hires-apples-head-chip-designer/ |title=AMD Hires Apple's Head Chip Designer |author=Arik Hesseldahl |date=1 August 2012 |work=[[AllThingsD]] }}</ref> He was also the coauthor of the specifications for the [[x86-64]] instruction set<ref name=venturebeat /><ref name=itworld>{{cite news |url=http://www.itworld.com/article/2693371/is-amd-finally-ready-to-give-intel-a-real-fight.html |title=AMD roadmap: Is AMD finally ready to give Intel a real fight? |author=Andy Patrizio |date=16 May 2014 |work=ITworld}}</ref> and [[HyperTransport]] interconnect.<ref name=anandtech/><ref name=itworld /><ref name=semiaccurate>{{cite news |url=http://semiaccurate.com/2012/08/01/apples-cpu-architect-jim-keller-moves-back-to-amd/ |title=Apple's CPU architect Jim Keller moves back to AMD |author=Charlie Demerjian |date=1 August 2012 |work=[[SemiAccurate]] }}</ref> In 2012, he returned to AMD to work on the [[AMD K12]]<ref name=decryptedtech>{{cite news |url=http://www.decryptedtech.com/news/amd-brings-k7-k8-creator-jim-keller-back-into-the-fold |title=AMD Brings K7/K8 Creator, Jim Keller, Back Into the Fold |author=Sean Kalinich |date=27 June 2014 |work=decryptedtech.com }}</ref> and [[AMD Zen|Zen]] microarchitectures,<ref name=kitguru>{{cite news |url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/ |title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be |author=Anton Shilov |date=11 September 2014 |work=kitguru.net }}</ref><ref name=wccftech>{{cite news |url=http://wccftech.com/amd-confirms-development-of-high-performance-x86-core-with-completely-new-architecture/ |title=AMD Confirms Development of High-Performance x86 Core With Completely New Architecture |author=Hassan Mujtaba |date=5 May 2014 |work=WCCFtech }}</ref> particularly on the low-power/embedded versions.<ref name=cultofmac /><ref name=allthingsd />

== Career ==
Jim Keller was working at [[Digital Equipment Corporation|DEC]] until 1998, where he was involved in designing the [[Alpha 21164]] and [[Alpha 21264|21264]] processors.<ref name=anandtech /><ref name=xbitlabs /> In 1998 he moved to AMD, where he worked to launch the AMD [[Athlon]] (K7) processor and was the lead architect of the [[AMD K8]] microarchitecture,<ref name=9to5mac>{{cite news |url=http://9to5mac.com/2012/08/01/apple-cpu-guru-jim-keller-who-came-with-pa-semi-deal-departs-back-to-amd-to-lead-group-under-mark-papermaster/ |title=Apple CPU guru Jim Keller, who came with PA Semi deal, departs back to AMD to lead group under Mark Papermaster |author=Seth Weintraub |date=1 August 2012 |work=9to5Mac }}</ref> which also included designing the x86-64 instruction set and HyperTransport interconnect mainly used for [[multiprocessor]] communications.<ref name=anandtech />

In 1999, he left AMD to work at SiByte to design [[MIPS instruction set|MIPS]]-based processors for 1 Gbit/s network interfaces and other devices.<ref name=xbitlabs /><ref name=semiaccurate /><ref>{{cite web |url=http://www.techspot.com/news/49611-apple-chip-designer-jim-keller-heads-back-to-amd.html |title=Apple chip designer Jim Keller heads back to AMD |author=Jose Vilches |date=1 August 2012 |work=[[TechSpot]] }}</ref> In November 2000, SiByte was acquired by [[Broadcom]],<ref>{{cite news |url=http://www.wsj.com/articles/SB973519053768422247 |title=Broadcom Agrees to Acquire SiByte for $2 Billion in Stock |author=Molly Williams |date=7 November 2000 |work=[[Wall Street Journal]] }}</ref> where he continued as chief architect<ref name=theverge /> until 2004.<ref name=anandtech />

In 2004 he moved to serve as the Vice President of Engineering at [[P.A. Semi]],<ref name=anandtech /><ref name=itworld /> a company specializing in low-power mobile processors.<ref name=xbitlabs /> P.A. Semi was acquired by Apple in 2008, and Keller followed,<ref name=thenextweb /><ref name=9to5mac /> becoming part of a team to design the Apple A4 and A5 [[system-on-a-chip]] mobile processors. These processors were used in several Apple products, including [[iPhone 4]], [[iPhone 4S|4S]], [[iPad]] and [[iPad 2]].

In August 2012, Jim Keller returned to AMD, where his primary task is to design a new generation [[microarchitecture]]<ref name=computing /><ref name=itworld /><ref name=wccftech /> called [[Zen (microarchitecture)|Zen]].<ref name=kitguru /> After years of being unable to compete with [[Intel]] in the desktop [[CPU]] market, the new generation of Zen processors is hoped to restore AMD's position in the high-end [[x86-64]] processor market.<ref name=anandtech /><ref name=decryptedtech />

== References ==
{{Reflist|30em}}

{{DEFAULTSORT:Keller, Jim}}
[[Category:Living people]]
[[Category:Advanced Micro Devices people]]
[[Category:American engineers]]
[[Category:Computer hardware engineers]]
[[Category:Apple Inc. ex-employees]]

{{engineer-stub}}

Zen (Mikroarchitektur)

2015-07-09T00:34:35Z

Intgr: /* top */ Missing space

{{Infobox CPU
| name = Zen
| image =
| image_size = 138px
| caption =
| produced-start = 2016–2017
| produced-end =
| designfirm = [[AMD]]
| manuf1 = [[Advanced Micro Devices|AMD]]
| size-from = 14 nm ([[Multigate device#FinFET|Bulk Silicon]])<ref name="WCCF Zen">{{cite web|last=Moammer |first=Khalid |url=http://wccftech.com/breaking-amds-gen-x86-high-performance-core-code-named-zen-debut-k12/ |title=AMD's Next Gen x86 High Performance Core is Zen |publisher=WCCF Tech | date=September 9, 2014 |accessdate=January 15, 2015}}</ref>
| predecessor = [[Excavator (microarchitecture)|Excavator]] ([[x86-64|x86/64]])
| successor =
| arch = [[x86-64|x86/64]]
| sock1 = [[Socket AM4]]<ref>{{cite web |url=http://www.anandtech.com/show/9231/amds-20162017-x86-roadmap-zen-is-in|title=AMD’s 2016-2017 x86 Roadmap: Zen Is In, Skybridge Is Out |author=Ryan Smith |date={{date|2015-05-06}} |publisher=[[AnandTech]] }}</ref>
| application = Desktop, Laptop, Server
| core1 =
| TDP =
}}

'''Zen''' is an upcoming [[CPU]] microarchitecture created by [[AMD]].<ref name="AMD hints at high-performance Zen">{{cite news|url=http://www.bit-tech.net/news/hardware/2014/09/11/amd-zen/1 | publisher=bit-tech | title=AMD hints at high-performance Zen x86 architecture | date=11 September 2014 | accessdate=15 December 2014}}</ref> The team in charge of the Zen microarchitecture is being led by [[Jim Keller (engineer)|Jim Keller]], the engineer also responsible for the [[Athlon 64]].<ref name="techspot">{{cite web|url=http://www.techspot.com/news/60626-tech-reading-amd-zen-comeback.html|title=Weekend tech reading: AMD 'Zen' and their return to high-end CPUs, tracking Windows pirates - TechSpot|publisher=techspot.com|accessdate=2015-05-12}}</ref><ref name="techreport">{{cite web|url=http://techreport.com/review/28228/amd-zen-chips-headed-to-desktops-servers-in-2016|title=AMD: Zen chips headed to desktops, servers in 2016 - The Tech Report - Page 1|publisher=techreport.com|accessdate=2015-05-12}}</ref> Zen was originally planned for 2017 following the ARM64-based [[AMD K12|K12]] sister core, but on AMD’s 2015 Financial Analyst Day it was revealed that K12 was delayed in favour of the Zen design for market entry in the 2016 timeframe.<ref name="Ryan Smith">{{cite web|last1=Smith|first1=Ryan|title=AMD's 2016-2017 x86 Roadmap: Zen Is In, Skybridge Is Out|url=http://www.anandtech.com/show/9231/amds-20162017-x86-roadmap-zen-is-in|publisher=Anandtech|accessdate=10 May 2015}}</ref>

==Architecture==
According to [[AMD]], Zen's main focus will be on increasing per-core performance rather than core count or multi-threading performance.<ref name="kitguru">{{cite web|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/|title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be | KitGuru|publisher=kitguru.net|accessdate=2015-05-12}}</ref> Reports from AMD indicate that Zen will abandon modular [[Bulldozer (microarchitecture)#CMT|CMT]] (Clustered Multithread) for a [[Simultaneous multithreading|SMT]] (Simultaneous Multithreading) microarchitecture,<ref>{{cite web|title=AMD 2015 comeback attempt: reforming high-performance processor, abandon modular architecture.|url=http://www.expreview.com/33161.html|publisher=Extreme Performance Review|accessdate=10 May 2015}}</ref><ref name="WCCF Zen" /> the model Intel uses. Adapting their chips from the less-popular CMT to SMT<ref name="Ryan Smith">{{cite web|last1=Smith|first1=Ryan|title=AMD's 2016-2017 x86 Roadmap: Zen Is In, Skybridge Is Out|url=http://www.anandtech.com/show/9231/amds-20162017-x86-roadmap-zen-is-in|publisher=Anandtech|accessdate=10 May 2015}}</ref> is expected to offer much higher number threading efficiency, but also possibly increase the die size of Zen module.<ref name="AMD: ‘Bulldozer’ was not a game-changer">{{cite news|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/ | publisher=KitGuru | title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be | date=11 September 2014 | accessdate=1 February 2015}}</ref>

Reportedly, the Zen architecture will be built on a more efficient [[14 nanometer]], rather than 32 nm process.<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading"/> It will feature a unified AM4 socket with its GPU-equipped APU counterparts,<ref name="pcgamer">{{cite web|url=http://www.pcgamer.com/amds-next-gen-zen-cpu-due-in-2016/|title=AMD's next-gen Zen CPU due in 2016 - PC Gamer|publisher=pcgamer.com|accessdate=2015-05-12}}</ref> and feature [[DDR4 SDRAM|DDR4]] support and 95 W [[Thermal design power|TDP]].<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading">{{cite news|url=http://news.softpedia.com/news/14nm-AMD-Zen-CPU-Will-Have-DDR4-and-Simultaneous-Multithreading-471401.shtml | publisher=Softpedia | title=14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading | date=28 January 2015 | accessdate=31 January 2015}}</ref> While newer roadmaps don't confirm the TDP for desktop products, they suggest a range for low-power mobile products with up to two Zen cores from 5 to 15 W and 15 to 35 W for performance-oriented mobile products with up to four Zen cores.<ref name="Shattered Media article">{{cite news| url=http://www.shattered.media/amds-next-gen-cpu-zen/ | publisher=Shattered.Media | title=AMD's next gen CPU Zen |date=May 2015}}</ref>

Zen will support [[RDSEED]].<ref name="AMD Starts Linux Enablement">{{cite news|url=http://www.phoronix.com/scan.php?page=news_item&px=AMD-Zen-CPU-Znver1 | publisher=Phoronix | title=AMD Starts Linux Enablement On Next-Gen "Zen" Architecture | date=17 March 2015 | accessdate=17 March 2015}}</ref>{{explain}}

==History==
AMD began planning Zen shortly after re-hiring [[Jim Keller (engineer)|Jim Keller]] in early 2012.<ref>https://www.youtube.com/watch?v=SOTFE7sJY-Q</ref>

Zen's release is expected at some point in 2016.<ref name="pcgamer" />

==See also==
* [[Bulldozer (microarchitecture)]]
* [[Steamroller (microarchitecture)]]
* [[AMD K12]]

==References==
{{Reflist|30em}}

{{-}}

{{AMD processors}}

[[Category:Advanced Micro Devices x86 microprocessors]]
[[Category:Advanced Micro Devices microarchitectures]]

{{Comp-hardware-stub}}

Jim Keller

2015-06-15T13:02:07Z

Intgr: /* Career */ Clarify that it competes with x86-64 CPUs from other vendors, too

{{Infobox person
| name = Jim Keller
| image = 
| alt =
| caption =
| birth_name = 
| birth_date = 
| birth_place =
| death_date = 
| death_place =
| nationality =
| other_names =
| occupation = Chief Architect of Microprocessor Cores and Corporate Vice President, Advanced Micro Devices<ref>{{cite web |url=http://www.bloomberg.com/research/stocks/people/person.asp?personId=215060089&ticker=AMD&previousCapId=168864&previousTitle=ADVANCED%20MICRO%20DEVICES |title=Jim Keller: Executive Profile & Biography |work=[[Bloomberg Business]] |accessdate={{date|2015-05-14}} }}</ref><ref name=bit-tech>{{cite web |url=http://www.bit-tech.net/news/hardware/2012/08/02/amd-jim-keller/1 |title=AMD re-hires Athlon 64 K8 designer Jim Keller |author=Gareth Halfacree |date=2 August 2012 |work=bit-tech }}</ref>
| years_active =
| known_for = {{Plainlist|
* AMD K7
* AMD K8 (lead architect)
* Apple A4, A5
* x86-64 (coauthor)
* HyperTransport (coauthor)
}}
| notable_works =
}}

'''Jim Keller''' is a [[microprocessor]] [[engineer]] most well known for his work at [[AMD]] and [[Apple Inc.|Apple]]. He was the lead architect of [[AMD K8]] microarchitecture<ref name=anandtech>{{cite news |url=http://www.anandtech.com/show/6129/apple-a4a5-designer-k8-lead-architect-jim-keller-returns-to-amd |title=Apple A4/A5 Designer & K8 Lead Architect, Jim Keller, Returns to AMD |author=[[Anand Lal Shimpi]] |date=1 August 2012 |work=[[AnandTech]] }}</ref><ref name=xbitlabs>{{cite news |url=http://www.xbitlabs.com/news/cpu/display/20120801190422_Return_of_the_King_AMD_K7_and_K8_Designer_Jim_Keller_Back_at_AMD.html |title=Return of the King: AMD K7 and K8 Designer Jim Keller Back at AMD |author=Anton Shilov |date=1 August 2012 |work=X-bit Labs }}</ref><ref name=computing>{{cite news |url=http://www.computing.co.uk/ctg/news/2344223/amd-to-design-new-micro-architecture-for-2015-launch-under-chip-guru-jim-keller |title=AMD to design new micro-architecture for 2015 launch under chip guru Jim Keller |author=Graeme Burton |date=12 May 2014 |work=computing.co.uk }}</ref> (including the original [[Athlon 64]])<ref name=anandtech /><ref name=thenextweb>{{cite news |url=http://thenextweb.com/insider/2012/08/01/apples-cpu-architect-jim-keller-departs-to-head-up-chipmaker-amds-processor-group/ |title=Apple's CPU Architect Jim Keller Jumps To AMD |author=Robin Wauters |date=1 August 2012 |work=[[The Next Web]] }}</ref><ref name=cultofmac>{{cite news |url=http://www.cultofmac.com/182296/amd-hires-ax-series-architect-jim-keller-away-from-apple-to-report-to-mark-papermaster/ |title=AMD Hires Ax Series Architect Jim Keller Away From Apple To Report To Mark Papermaster |author=John Brownlee |date=1 August 2012 |work=Cult of Mac}}</ref> and was involved in designing the [[Athlon]] (K7)<ref name=computing /> and [[Apple A4]]/[[Apple A5|A5]] processors.<ref name=anandtech /><ref name=venturebeat>{{cite news |url=http://venturebeat.com/2012/08/01/apple-cpu-jim-keller-amd/ |title=Apple CPU lead Jim Keller heads back to AMD as chief architect |author=Devindra Hardawar |date=1 August 2012 |work=[[VentureBeat]] }}</ref><ref name=theverge>{{cite news |url=http://www.theverge.com/2012/8/1/3212406/jim-keller-joins-amd-vp-chief-architect |title=Former Apple chip designer Jim Keller joins AMD as chief architect and VP |author=Adi Robertson |date=1 August 2012 |publisher=Vox Media |work=[[The Verge]] }}</ref><ref name=allthingsd>{{cite news |url=http://allthingsd.com/20120801/amd-hires-apples-head-chip-designer/ |title=AMD Hires Apple's Head Chip Designer |author=Arik Hesseldahl |date=1 August 2012 |work=[[AllThingsD]] }}</ref> He was also the coauthor of the specifications for the [[x86-64]] instruction set<ref name=venturebeat /><ref name=itworld>{{cite news |url=http://www.itworld.com/article/2693371/is-amd-finally-ready-to-give-intel-a-real-fight.html |title=AMD roadmap: Is AMD finally ready to give Intel a real fight? |author=Andy Patrizio |date=16 May 2014 |work=ITworld}}</ref> and [[HyperTransport]] interconnect.<ref name=anandtech/><ref name=itworld /><ref name=semiaccurate>{{cite news |url=http://semiaccurate.com/2012/08/01/apples-cpu-architect-jim-keller-moves-back-to-amd/ |title=Apple's CPU architect Jim Keller moves back to AMD |author=Charlie Demerjian |date=1 August 2012 |work=[[SemiAccurate]] }}</ref> In 2012, he returned to AMD to work on the [[AMD K12]]<ref name=decryptedtech>{{cite news |url=http://www.decryptedtech.com/news/amd-brings-k7-k8-creator-jim-keller-back-into-the-fold |title=AMD Brings K7/K8 Creator, Jim Keller, Back Into the Fold |author=Sean Kalinich |date=27 June 2014 |work=decryptedtech.com }}</ref> and [[AMD Zen|Zen]] microarchitectures,<ref name=kitguru>{{cite news |url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/ |title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be |author=Anton Shilov |date=11 September 2014 |work=kitguru.net }}</ref><ref name=wccftech>{{cite news |url=http://wccftech.com/amd-confirms-development-of-high-performance-x86-core-with-completely-new-architecture/ |title=AMD Confirms Development of High-Performance x86 Core With Completely New Architecture |author=Hassan Mujtaba |date=5 May 2014 |work=WCCFtech }}</ref> particularly on the low-power/embedded versions.<ref name=cultofmac /><ref name=allthingsd />

== Career ==
Jim Keller was working at [[Digital Equipment Corporation|DEC]] until 1998, where he was involved in designing the [[Alpha 21164]] and [[Alpha 21264|21264]] processors.<ref name=anandtech /><ref name=xbitlabs /> In 1998 he moved to AMD, where he worked to launch the AMD [[Athlon]] (K7) processor and was the lead architect of the [[AMD K8]] microarchitecture,<ref name=9to5mac>{{cite news |url=http://9to5mac.com/2012/08/01/apple-cpu-guru-jim-keller-who-came-with-pa-semi-deal-departs-back-to-amd-to-lead-group-under-mark-papermaster/ |title=Apple CPU guru Jim Keller, who came with PA Semi deal, departs back to AMD to lead group under Mark Papermaster |author=Seth Weintraub |date=1 August 2012 |work=9to5Mac }}</ref> which also included designing the x86-64 instruction set and HyperTransport interconnect mainly used for [[multiprocessor]] communications.<ref name=anandtech />

In 1999, he left AMD to work at SiByte to design [[MIPS instruction set|MIPS]]-based processors for 1 Gbit/s network interfaces and other devices.<ref name=xbitlabs /><ref name=semiaccurate /><ref>{{cite web |url=http://www.techspot.com/news/49611-apple-chip-designer-jim-keller-heads-back-to-amd.html |title=Apple chip designer Jim Keller heads back to AMD |author=Jose Vilches |date=1 August 2012 |work=[[TechSpot]] }}</ref> In November 2000, SiByte was acquired by [[Broadcom]],<ref>{{cite news |url=http://www.wsj.com/articles/SB973519053768422247 |title=Broadcom Agrees to Acquire SiByte for $2 Billion in Stock |author=Molly Williams |date=7 November 2000 |work=[[Wall Street Journal]] }}</ref> where he continued as chief architect<ref name=theverge /> until 2004.<ref name=anandtech />

In 2004 he moved to serve as the Vice President of Engineering at [[P.A. Semi]],<ref name=anandtech /><ref name=itworld /> a company specializing in low-power mobile processors.<ref name=xbitlabs /> P.A. Semi was acquired by Apple in 2008, and Keller followed,<ref name=thenextweb /><ref name=9to5mac /> becoming part of a team to design the Apple A4 and A5 [[system-on-a-chip]] mobile processors. These processors were used in several Apple products, including [[iPhone 4]], [[iPhone 4S|4S]], [[iPad]] and [[iPad 2]].

In August 2012, Jim Keller returned to AMD, where his primary task is to design a new generation [[microarchitecture]]<ref name=computing /><ref name=itworld /><ref name=wccftech /> called [[Zen (microarchitecture)|Zen]].<ref name=kitguru /> After years of disappointing processors from AMD, the Zen is hoped to restore AMD's position in the high-end [[x86-64]] processor market.<ref name=anandtech /><ref name=decryptedtech />

== References ==
{{Reflist|30em}}

[[Category:Living people]]
[[Category:Advanced Micro Devices people]]
[[Category:American engineers]]
[[Category:Computer hardware engineers]]
[[Category:Apple Inc. ex-employees]]

{{engineer-stub}}

Verteilter Cache

2015-06-10T08:35:42Z

Intgr: Revert WP:REFSPAM, WP:SELFCITE.

{{Use dmy dates|date=February 2013}}
In computing, a '''distributed cache''' is an extension of the traditional concept of [[cache (computing)|cache]] used in a single [[Locale (computer hardware)|locale]]. A distributed cache may span multiple servers so that it can grow in size and in transactional capacity. It is mainly used to store application data residing in [[database]] and web [[session (computer science)|session]] data. The idea of distributed caching<ref>
{{cite journal
| last = Paul
| first = S
|author2=Z Fei
| date = 2001-02-01
| title = Distributed caching with centralized control
| journal = Computer Communications
| volume = 24
| issue = 2
| pages = 256–268
| doi = 10.1016/S0140-3664(00)00322-4
| accessdate = 2009-11-18
}}
</ref> has become feasible now because [[Random-access memory|main memory]] has become very cheap and [[Network interface controller|network cards]] have become very fast, with 1 Gbit now standard everywhere and 10 Gbit gaining traction. Also, a distributed cache works well on lower cost machines usually employed for [[web server]]s as opposed to [[database server]]s which require expensive hardware.<ref>
{{cite journal
| last = Khan
| first = Iqbal
| title = Distributed Caching On The Path To Scalability
| magazine = MSDN
| issue = July 2009
| url = http://msdn.microsoft.com/en-us/magazine/dd942840.aspx
| accessdate = 2012-03-30
}}
</ref>

== Examples ==
* [[Aerospike_database|Aerospike]]
* [[Ehcache]]
* [[GigaSpaces]]
* [[Hazelcast]]
* [[Memcached]]
* [[Oracle Coherence]]
* [[Riak]]
* [[Redis]]
* [[SafePeak]]
* [[Tarantool]]
* [[NCache]]
* GridGain
* [[Velocity_(memory_cache)|Velocity]]/[[AppFabric]]

== See also ==
* [[Cache algorithms]]
* [[Cache coherence]]
* [[Cache-oblivious algorithm]]
* [[Cache stampede]]
* [[Cache language model]]
* [[Database cache]]
* [[Cache manifest in HTML5]]

== References ==
{{Reflist}}

[[Category:Cache (computing)| ]]

WolfSSL

2015-06-02T07:36:11Z

Intgr: /* Product history */ Remove list of versions/dates, see WP:CHANGELOG, WP:PROSE

{{lowercasetitle}}
{{primary sources|date=September 2010}}
{{Infobox software
| name = wolfSSL
| logo =
| screenshot =
| caption =
| developer = Todd Ouska
| released = {{Start date|2006|02|19}}<ref name="wolfSSL-ChangeLog">{{cite web |title=wolfSSL ChangeLog |url=https://www.wolfssl.com/wolfSSL/Docs-wolfssl-changelog.html}}</ref>
| operating_system = Multi-platform
| frequently_updated = yes
| programming_language = [[C (programming language)|C language]]
| genre = [[Library (computer science)|Security library]]
| status = Active
| license = [[GNU General Public License]] or Commercial Distribution License
| website = {{URL|http://www.wolfssl.com/wolfSSL/Home.html}}
}}
'''wolfSSL''' (formerly '''CyaSSL''' or '''yet another SSL''') is a small, portable, embedded SSL programming library targeted for use by embedded systems developers. It is an [[open source]] implementation of [[Secure Sockets Layer|SSL]] (SSL 3, TLS 1.0, 1.1, 1.2, and DTLS 1.0 and 1.2) built in the [[C (programming language)|C language]]. It includes SSL client libraries and an SSL server implementation as well as support for multiple API's, including those defined by [[Secure Sockets Layer|SSL]] and [[Transport Layer Security|TLS]]. CyaSSL also includes an [[OpenSSL]] compatibility interface with the most commonly used OpenSSL functions.<ref name="compatibility">[https://www.wolfssl.com/wolfSSL/Products.html wolfSSL - Embedded Communications Products]</ref>

A predecessor of CyaSSL, yaSSL is a [[C++]] based SSL library for embedded environments and real time operating systems with constrained resources.

==Platforms==
wolfSSL is currently available for [[Windows API|Win32/64]], [[Linux]], [[Mac OS X]], [[Solaris (operating system)|Solaris]], [[Threadx]], [[VxWorks]], [[FreeBSD]], [[NetBSD]], [[OpenBSD]], [[embedded Linux]], [[WinCE]], [[Haiku os|Haiku]], [[OpenWrt]], [[iPhone]], [[Android (operating system)|Android]], [[Wii|Nintendo Wii]] and [[Nintendo GameCube|Gamecube]] through DevKitPro support, [[QNX]], [[MontaVista]], [[TRON Project|Tron]] variants, [[NonStop]], [[OpenCL]], Micrium's [[MicroC/OS-II]], [[FreeRTOS]], [[SafeRTOS]], [[MQX|Freescale MQX]], [[Nucleus RTOS|Nucleus]], [[TinyOS]], [[TI-RTOS]], and [[HP-UX]].

==History==
The genesis of yaSSL, or yet another SSL, dates to 2004. [[OpenSSL]] was available at the time, and was dual licensed under the ''OpenSSL License'' and the ''SSLeay license''.<ref>[http://www.openssl.org/source/license.html OpenSSL: Source, License]</ref> yaSSL, alternatively, was developed and dual-licensed under both a commercial license and the GPL.<ref>[https://www.wolfssl.com/wolfSSL/License.html wolfSSL - License]</ref> yaSSL offered a more modern API, commercial style developer support and was complete with an OpenSSL compatibility layer.<ref name="compatibility"/> The first major user of wolfSSL/CyaSSL/yaSSL was [[MySQL]].<ref>[http://dev.mysql.com/doc/refman/5.7/en/configuring-for-ssl.html MySQL, Using SSL Connections]</ref> Through bundling with MySQL, yaSSL has achieved extremely high distribution volumes in the millions.

Today wolfSSL is used in both open source<ref>[https://www.wolfssl.com/wolfSSL/Community.html wolfSSL - Community]</ref> and commercial{{Citation needed|date=March 2015}} projects. CyaSSL is included in many{{Citation needed|date=March 2015}} types of network devices such as smart devices on automobiles, IP phones, mobile phones, routers, printers, and credit card scanners.

==Protocols==
{{main|Transport Layer Security}}
The wolfSSL lightweight SSL library implements the following protocols:<ref name="protocols">[https://www.wolfssl.com/wolfSSL/Docs-cyassl-manual-4-features.html wolfSSL - Docs | CyaSSL Manual - Chapter 4 (Features)]</ref>
* SSL 3.0, TLS 1.0, TLS 1.1, TLS 1.2
* DTLS 1.0, DTLS 1.2
CyaSSL does not support SSL 2.0 as it is insecure.

==Algorithms==
CyaSSL uses the following cryptography libraries:

===wolfCrypt===
By default, wolfSSL uses the cryptographic services provided by wolfCrypt.<ref>[https://www.wolfssl.com/wolfSSL/Docs-cyassl-manual-10-ctaocrypt-usage-reference.html wolfSSL - Docs | CyaSSL Manual - Chapter 10 (CTaoCrypt Usage Reference)]</ref> wolfCrypt Provides [[RSA (algorithm)|RSA]], [[Elliptic curve cryptography|ECC]], [[Digital Signature Algorithm|DSS]], [[Diffie–Hellman key exchange|Diffie–Hellman]], [[EDH]], [[NTRU]], [[Data Encryption Standard|DES]], [[Triple DES]], [[Advanced Encryption Standard|AES]] (CBC, CTR, CCM, GCM), [[Camellia (cipher)|Camellia]], [[ARC4]], [[HC-128]], [[ChaCha20]], [[MD2 (cryptography)|MD2]], [[MD4]], [[MD5]], [[SHA-1]], [[SHA-2]], [[BLAKE (hash function)|BLAKE2]], [[RIPEMD-160]], [[Poly1305]], Random Number Generation, Large Integer support, and base 16/64 encoding/decoding. An experimental cipher called [[Rabbit (cipher)|Rabbit]], a public domain stream cipher from the EU's eSTREAM project, is also included. Rabbit is potentially useful to those encrypting streaming media in high performance, high demand environments.

wolfCrypt acts as a back-end crypto implementation for several popular software packages and libraries, including [[Kerberos (protocol)|MIT Kerberos]]<ref>[http://web.mit.edu/kerberos/ Kerberos: The Network Authentication Protocol]</ref> (where it can be enabled using a build option).

===NTRU===
CyaSSL+ includes [[NTRUEncrypt|NTRU]]<ref name="securityinnovation">[http://securityinnovation.com/cryptolab/ NTRU CryptoLabs]</ref> public key encryption. The addition of NTRU in CyaSSL+ was a result of the partnership between yaSSL and Security Innovation.<ref name="securityinnovation" /> NTRU works well in mobile and embedded environments due to the reduced bit size needed to provide the same security as other public key systems. In addition, it's not known to be vulnerable to quantum attacks. Several cipher suites utilizing NTRU are available with CyaSSL+ including AES-256, RC4, and HC-128.

==Licensing==
wolfSSL is [[Open Source]], licensed under the GNU General Public License GPLv2.<ref>[http://www.gnu.org/licenses/license-list.html GNU License]</ref>

==Awards==
2011 Tomorrow's Technology Today - Mobile Encryption<ref>[http://www.infosecurityproductsguide.com/technology/2011/Security-Innovation.html 2011 Tomorrow's Technology Today - Mobile Encryption]</ref>

2015 Cybersecurity 500 - wolfSSL<ref>[http://cybersecurityventures.com/cybersecurity-500/ Cybersecurity Ventures - Cybersecurity 500]</ref>

==See also==
{{Portal|Free software|Cryptography}}
*[[Transport Layer Security]]
*[[Comparison of TLS implementations]]
*[[GnuTLS]]
*[[Network Security Services]]
*[[OpenSSL]]

==References==
{{Reflist|2}}

==External links==
* [http://www.wolfssl.com/wolfSSL/Home.html wolfSSL/CyaSSL Homepage]

{{Cryptographic software}}
{{SSL/TLS}}

{{DEFAULTSORT:wolfSSL}}
[[Category:Cryptographic software]]
[[Category:C libraries]]
[[Category:Transport Layer Security implementation]]

Zen (Mikroarchitektur)

2015-06-01T08:31:14Z

Intgr: This is a marketing primary source, almost no reliable information. +copyedit

{{Infobox CPU
| name = Zen
| image =
| image_size = 138px
| caption =
| produced-start = 2016–2017
| produced-end =
| designfirm = [[AMD]]
| manuf1 = [[Advanced Micro Devices|AMD]]
| size-from = 14 nm ([[Multigate device#FinFET|Bulk Silicon]])<ref name="WCCF Zen">{{cite web|last=Moammer |first=Khalid |url=http://wccftech.com/breaking-amds-gen-x86-high-performance-core-code-named-zen-debut-k12/ |title=AMD's Next Gen x86 High Performance Core is Zen |publisher=WCCF Tech | date=September 9, 2014 |accessdate=January 15, 2015}}</ref>
| predecessor = [[Excavator (microarchitecture)|Excavator]] ([[x86-64|x86/64]])
| successor =
| arch = [[x86-64|x86/64]]
| sock1 = [[Socket AM4]]<ref>{{cite web |url=http://www.anandtech.com/show/9231/amds-20162017-x86-roadmap-zen-is-in|title=AMD’s 2016-2017 x86 Roadmap: Zen Is In, Skybridge Is Out |author=Ryan Smith |date={{date|2015-05-06}} |publisher=[[AnandTech]] }}</ref>
| application = Desktop, Laptop, Server
| core1 =
| TDP =
}}

'''Zen''' is an upcoming chip microarchitecture created from scratch by [[AMD]].<ref name="AMD hints at high-performance Zen">{{cite news|url=http://www.bit-tech.net/news/hardware/2014/09/11/amd-zen/1 | publisher=bit-tech | title=AMD hints at high-performance Zen x86 architecture | date=11 September 2014 | accessdate=15 December 2014}}</ref><ref name="WCCF 2016 roadmap">{{cite web|last=Mujtaba |first=Hassan |url=http://wccftech.com/amd-announces-20142016-roadmap-20nm-project-skybridge-k12-64bit-arm-cores-2016/ |title=AMD Announces 2014-2016 Roadmap – 20nm Project SkyBridge and K12 64-bit ARM Cores For 2016 |publisher=WCCF Tech | date=May 5, 2014 |accessdate=January 15, 2015}}</ref> The team in charge of the Zen microarchitecture is being led by [[Jim Keller (engineer)|Jim Keller]], the engineer also responsible for the [[Athlon 64]].<ref name="techspot">{{cite web|url=http://www.techspot.com/news/60626-tech-reading-amd-zen-comeback.html|title=Weekend tech reading: AMD 'Zen' and their return to high-end CPUs, tracking Windows pirates - TechSpot|publisher=techspot.com|accessdate=2015-05-12}}</ref><ref name="techreport">{{cite web|url=http://techreport.com/review/28228/amd-zen-chips-headed-to-desktops-servers-in-2016|title=AMD: Zen chips headed to desktops, servers in 2016 - The Tech Report - Page 1|publisher=techreport.com|accessdate=2015-05-12}}</ref> Starting in 2015 the upcoming AMD Project Skybridge plans to develop x86 cores and ARM cores that are pin-to-pin compatible for both [[AMD Accelerated Processing Unit|APUs]] and [[System on a chip|SoCs]] to control the motherboard with full support for [[Heterogeneous System Architecture|HSA]].<ref name="WCCF 2016 roadmap" /> Zen is the [[x86-64|x86/64]] sister core architecture to the solely 64-bit [[ARM architecture#ARMv8-A|ARMv8-A]] [[AMD K12|K12]].<ref name="WCCF Zen" />
==Architecture==
According to [[AMD]], Zen's main focus will be on increasing per-core performance rather than core count or multi-threading performance.<ref name="kitguru">{{cite web|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/|title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be | KitGuru|publisher=kitguru.net|accessdate=2015-05-12}}</ref> Initial rumors indicate that Zen may abandon modular CMT (Clustered Multi-Thread) for [[Simultaneous multithreading|SMT]]-style microarchitecture,<ref>{{cite web|title=AMD 2015 comeback attempt: reforming high-performance processor, abandon modular architecture.|url=http://www.expreview.com/33161.html|publisher=Extreme Performance Review|accessdate=10 May 2015}}</ref><ref name="WCCF Zen" /> the model Intel uses and software developers more commonly develop for.{{fact|date=May 2015}} Adapting their chips from the less-popular CMT to SMT<ref name="Ryan Smith">{{cite web|last1=Smith|first1=Ryan|title=AMD's 2016-2017 x86 Roadmap: Zen Is In, Skybridge Is Out|url=http://www.anandtech.com/show/9231/amds-20162017-x86-roadmap-zen-is-in|publisher=Anandtech|accessdate=10 May 2015}}</ref> is expected to offer much higher number threading efficiency, but also possibly increase the die size of Zen module.<ref name="AMD: ‘Bulldozer’ was not a game-changer">{{cite news|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/ | publisher=KitGuru | title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be | date=11 September 2014 | accessdate=1 February 2015}}</ref>

Reportedly, the Zen architecture will be built on a more efficient [[14 nanometer]], rather than 32 nm process.<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading"/> It will feature a unified AM4 socket with its GPU-equipped APU counterparts,<ref name="pcgamer">{{cite web|url=http://www.pcgamer.com/amds-next-gen-zen-cpu-due-in-2016/|title=AMD's next-gen Zen CPU due in 2016 - PC Gamer|publisher=pcgamer.com|accessdate=2015-05-12}}</ref> and feature [[DDR4 SDRAM|DDR4]] support and 95 W [[Thermal design power|TDP]].<ref name="14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading">{{cite news|url=http://news.softpedia.com/news/14nm-AMD-Zen-CPU-Will-Have-DDR4-and-Simultaneous-Multithreading-471401.shtml | publisher=Softpedia | title=14nm AMD Zen CPU Will Have DDR4 and Simultaneous Multithreading | date=28 January 2015 | accessdate=31 January 2015}}</ref> While newer roadmaps don't confirm the TDP for desktop products, they suggest a range for low-power mobile products with up to two Zen cores from 5 to 15 W and 15 to 35 W for performance-oriented mobile products with up to four Zen cores.<ref name="Shattered Media article">{{cite news| url=http://www.shattered.media/amds-next-gen-cpu-zen/ | publisher=Shattered.Media | title=AMD's next gen CPU Zen |date=May 2015}}</ref>

Zen will support [[RDSEED]].<ref name="AMD Starts Linux Enablement">{{cite news|url=http://www.phoronix.com/scan.php?page=news_item&px=AMD-Zen-CPU-Znver1 | publisher=Phoronix | title=AMD Starts Linux Enablement On Next-Gen "Zen" Architecture | date=17 March 2015 | accessdate=17 March 2015}}</ref>{{explain}}

==History==

AMD began planning Zen shortly after hiring [[Jim Keller (engineer)|Jim Keller]] in early 2012.<ref>https://www.youtube.com/watch?v=SOTFE7sJY-Q</ref>

==Release date==
Zen is said to be slated for release some time in 2016.<ref name="pcgamer"/>

==See also==
* [[Bulldozer (microarchitecture)]]
* [[Steamroller (microarchitecture)]]

==References==
{{reflist}}

{{AMD processors}}

[[Category:Advanced Micro Devices x86 microprocessors]]
[[Category:Advanced Micro Devices microarchitectures]]
{{Comp-hardware-stub}}

Linux Security Modules

2015-05-28T09:00:09Z

Intgr: /* External links */ Revert spamlink, this is a blog advertising some hosting service that doesn't discuss LSM any further than name-dropping SELinux and AppArmor

'''Linux Security Modules''' ('''LSM''') is a [[Software framework|framework]] that allows the [[Linux kernel]] to support a variety of [[computer security model]]s while avoiding favoritism toward any single security implementation. The framework is licensed under the terms of the [[GNU General Public License]] and is standard part of the Linux kernel since Linux 2.6. [[AppArmor]], [[SELinux]], [[Smack (Linux security module)|Smack]] and [[TOMOYO Linux]] are the currently accepted modules in the official kernel.

== Design ==
LSM was designed to provide the specific needs of everything needed to successfully implement a [[mandatory access control]] module, while imposing the fewest possible changes to the Linux kernel. LSM avoids the approach of [[system call interposition]] as used in [[Systrace]] because it does not scale to [[multiprocessor]] kernels and is subject to [[TOCTTOU]] (race) attacks. Instead, LSM inserts "hooks" (upcalls to the module) at every point in the kernel where a user-level system call is about to result in access to an important internal kernel object such as inodes and task control blocks.

The project is narrowly scoped to solve the problem of [[access control]] to avoid imposing a large and complex change patch on the mainstream kernel. It is not intended as a general "''hook''" or "''upcall''" mechanism, nor does it support [[Operating system-level virtualization]].

LSM's access control goal is very closely related to the problem of [[system auditing]], but is subtly different. Auditing requires that every attempt at access be recorded. LSM cannot deliver that, because it would require a great many more hooks, so as to detect cases where the kernel "''short circuits''" failing system calls and returns an error code before getting near significant objects.

The LSM design is described in the paper ''Linux Security Modules: General Security Support for the Linux Kernel''<ref>{{cite web|url=http://www.usenix.org/event/sec02/wright.html|title=Linux Security Modules: General Security Support for the Linux Kernel|accessdate = 2007-02-03|year = 2002}}</ref> presented at USENIX Security 2002.<ref>{{cite web|url=http://www.usenix.org/event/sec02/|title=11th USENIX Security Symposium|accessdate = 2007-02-03|year = 2002}}</ref> At the same conference was the paper ''Using CQUAL for Static Analysis of Authorization Hook Placement''<ref>{{cite web|url=http://www.usenix.org/event/sec02/zhang.html|title=Using CQUAL for Static Analysis of Authorization Hook Placement|accessdate = 2007-02-03|year = 2002}}</ref> which studied automatic static analysis of the kernel code to verify that all of the necessary hooks have actually been inserted into the Linux kernel.

== Adoption ==
*[[AppArmor]]
*[[Security-Enhanced Linux|SELinux]]
*[[Smack_(Linux_security_module)|Smack]]
*[[TOMOYO Linux|TOMOYO]]

== History ==
At the 2001 Linux Kernel Summit, the [[National Security Agency|NSA]] proposed that [[Security-Enhanced Linux|SELinux]] be included in Linux 2.5. [[Linus Torvalds]] rejected SELinux at that time, because he observed that there are many different security projects in development, and since they all differ, the security community has not yet formed consensus on the ultimate security model. Instead, Linus charged the security community to "make it a module".

In response, [[Crispin Cowan]] proposed<ref>{{cite web|url=http://marc.info/?l=linux-kernel&m=98695004126478&w=2|title=Linux Security Module Interface|accessdate=2007-02-03|author=Crispin Cowan|work=linux-kernel mailing list|date=2001-04-11}}</ref> LSM: an interface for the Linux kernel that provides sufficient "hooks" (upcalls) from within the Linux kernel to a [[Loadable kernel module|loadable module]] so as to allow the module to enforce mandatory access controls. Development of LSM over the next two years was conducted by the LSM community, including substantial contributions from the [[Immunix|Immunix Corporation]], the [[NSA]], [[McAfee]], [[IBM]], [[Silicon Graphics]], and many independent contributors. LSM was ultimately accepted into the Linux kernel mainstream and was included as a standard part of Linux 2.6 in December 2003.

In 2006, some kernel developers observed that SELinux was the only widely used LSM module included in the mainstream Linux kernel source tree. If there is to be only one widely used LSM module, it was reasoned, then the indirection of LSM is unnecessary, and LSM should be removed and replaced with SELinux itself. However, there are other LSM modules maintained outside of the mainstream kernel tree ([[AppArmor]], [[Linux Intrusion Detection System]], [[FireFlier]], [[CIPSO]], [[Multi ADM]], etc.), so this argument led to two results: 1. that developers of these modules started putting effort into upstreaming their respective modules, and 2. at the 2006 [[Kernel Summit]], Linus once again asserted that LSM would stay because he does not want to arbitrate which is the best security model. LSM is likely to remain since an additional security module [[TOMOYO Linux]] was accepted in the mainline kernel version 2.6.30 (June 2009). With version 2.6.36, another security module ([[AppArmor]]) was accepted in the mainline kernel.

== Criticism ==
Some Linux kernel developers dislike LSM for a variety of reasons. LSM strives to impose the least overhead possible, especially in the case where no module is loaded, but this cost is not zero, and some Linux developers object to that cost. LSM is designed to provide only for access control, but does not actually prevent people from using LSM for other reasons, and so some Linux kernel developers dislike that it can be "abused" by being used for other purposes, especially if the purpose is to bypass the Linux kernel's [[GPL]] license with a proprietary module to extend Linux kernel functionality.

Some security developers also dislike LSM. The author of [[grsecurity]] dislikes LSM<ref>{{cite web|url=http://www.grsecurity.net/lsm.php|title=grsecurity|accessdate=2007-02-03|publisher=grsecurity}}</ref> because of its history, and that because LSM exports all of its symbols it facilitates the insertion of malicious modules ([[rootkits]]) as well as security modules. The author of [[RSBAC]] dislikes LSM<ref>{{cite web|url=http://www.rsbac.org/documentation/why_rsbac_does_not_use_lsm|title=RSBAC and LSM|accessdate=2007-02-03|publisher=RSBAC}}</ref> because it is incomplete with respect to the needs of RSBAC. In particular, the author of RSBAC argues that: "LSM is only about additional, restrictive access control. However, the RSBAC system provides a lot of additional functionality, e.g. symlink redirection, secure_delete, partial Linux DAC disabling. All this has to be patched into kernel functions in a separate patch.". The author of [[Dazuko]] argues<ref>{{cite web|url=http://dazuko.org/tgen.shtml#LSM|title=dazuko|accessdate=2007-10-02|publisher=dazuko}}</ref> that targeting the LSM API is a moving target, as it changes with each kernel release, leading to extra maintenance work. Other developers would like to have LSM modules stacked, e.g. the developer of the Yama LSM.<ref>{{cite web|last1=Edge|first1=Jake|title=LSM stacking (again)|url=http://lwn.net/Articles/393008/|publisher=www.lwn.net|accessdate=28 May 2015|date=23 June 2010}}</ref><ref>[http://lwn.net/Articles/393008/ LSM stacking (again)], Jake Edge, LWN, 2010-06-23</ref>

==References==
{{Reflist|2}}

==External links==
{{Portal|Free software}}
* [http://lsm.bkbits.net/ Source code and project statistics]
* [http://web.archive.org/web/20040816140809/http://www.samag.com/documents/s=9304/sam0409a/0409a.htm SysAdmin magazine article on BSD Secure Levels]
* [http://kernsec.org/wiki/index.php/Projects Security Projects based on the Linux kernel]
{{Linux}}

[[Category:Linux kernel]]

Jim Keller

2015-05-26T10:50:00Z

Intgr: As it stands, I don't think this paragraph of two sentences warrants its own section

{{Infobox person
| name = Jim Keller
| image = 
| alt =
| caption =
| birth_name = 
| birth_date = 
| birth_place =
| death_date = 
| death_place =
| nationality =
| other_names =
| occupation = Chief Architect of Microprocessor Cores and Corporate Vice President, Advanced Micro Devices<ref>{{cite web |url=http://www.bloomberg.com/research/stocks/people/person.asp?personId=215060089&ticker=AMD&previousCapId=168864&previousTitle=ADVANCED%20MICRO%20DEVICES |title=Jim Keller: Executive Profile & Biography |work=[[Bloomberg Business]] |accessdate={{date|2015-05-14}} }}</ref><ref name=bit-tech>{{cite web |url=http://www.bit-tech.net/news/hardware/2012/08/02/amd-jim-keller/1 |title=AMD re-hires Athlon 64 K8 designer Jim Keller |author=Gareth Halfacree |date=2 August 2012 |work=bit-tech }}</ref>
| years_active =
| known_for = {{Plainlist|
* AMD K7
* AMD K8 (lead architect)
* Apple A4, A5
* x86-64 (coauthor)
* HyperTransport (coauthor)
}}
| notable_works =
}}

'''Jim Keller''' is a [[microprocessor]] [[engineer]] most well known for his work at [[AMD]] and [[Apple Inc.|Apple]]. He was the lead architect of [[AMD K8]] microarchitecture<ref name=anandtech>{{cite news |url=http://www.anandtech.com/show/6129/apple-a4a5-designer-k8-lead-architect-jim-keller-returns-to-amd |title=Apple A4/A5 Designer & K8 Lead Architect, Jim Keller, Returns to AMD |author=[[Anand Lal Shimpi]] |date=1 August 2012 |work=[[AnandTech]] }}</ref><ref name=xbitlabs>{{cite news |url=http://www.xbitlabs.com/news/cpu/display/20120801190422_Return_of_the_King_AMD_K7_and_K8_Designer_Jim_Keller_Back_at_AMD.html |title=Return of the King: AMD K7 and K8 Designer Jim Keller Back at AMD |author=Anton Shilov |date=1 August 2012 |work=X-bit Labs }}</ref><ref name=computing>{{cite news |url=http://www.computing.co.uk/ctg/news/2344223/amd-to-design-new-micro-architecture-for-2015-launch-under-chip-guru-jim-keller |title=AMD to design new micro-architecture for 2015 launch under chip guru Jim Keller |author=Graeme Burton |date=12 May 2014 |work=computing.co.uk }}</ref> (including the original [[Athlon 64]])<ref name=anandtech /><ref name=thenextweb>{{cite news |url=http://thenextweb.com/insider/2012/08/01/apples-cpu-architect-jim-keller-departs-to-head-up-chipmaker-amds-processor-group/ |title=Apple's CPU Architect Jim Keller Jumps To AMD |author=Robin Wauters |date=1 August 2012 |work=[[The Next Web]] }}</ref><ref name=cultofmac>{{cite news |url=http://www.cultofmac.com/182296/amd-hires-ax-series-architect-jim-keller-away-from-apple-to-report-to-mark-papermaster/ |title=AMD Hires Ax Series Architect Jim Keller Away From Apple To Report To Mark Papermaster |author=John Brownlee |date=1 August 2012 |work=Cult of Mac}}</ref> and was involved in designing the [[Athlon]] (K7)<ref name=computing /> and [[Apple A4]]/[[Apple A5|A5]] processors.<ref name=anandtech /><ref name=venturebeat>{{cite news |url=http://venturebeat.com/2012/08/01/apple-cpu-jim-keller-amd/ |title=Apple CPU lead Jim Keller heads back to AMD as chief architect |author=Devindra Hardawar |date=1 August 2012 |work=[[VentureBeat]] }}</ref><ref name=theverge>{{cite news |url=http://www.theverge.com/2012/8/1/3212406/jim-keller-joins-amd-vp-chief-architect |title=Former Apple chip designer Jim Keller joins AMD as chief architect and VP |author=Adi Robertson |date=1 August 2012 |publisher=Vox Media |work=[[The Verge]] }}</ref><ref name=allthingsd>{{cite news |url=http://allthingsd.com/20120801/amd-hires-apples-head-chip-designer/ |title=AMD Hires Apple's Head Chip Designer |author=Arik Hesseldahl |date=1 August 2012 |work=[[AllThingsD]] }}</ref> He was also the coauthor of the specifications for the [[x86-64]] instruction set<ref name=venturebeat /><ref name=itworld>{{cite news |url=http://www.itworld.com/article/2693371/is-amd-finally-ready-to-give-intel-a-real-fight.html |title=AMD roadmap: Is AMD finally ready to give Intel a real fight? |author=Andy Patrizio |date=16 May 2014 |work=ITworld}}</ref> and [[HyperTransport]] interconnect.<ref name=anandtech/><ref name=itworld /><ref name=semiaccurate>{{cite news |url=http://semiaccurate.com/2012/08/01/apples-cpu-architect-jim-keller-moves-back-to-amd/ |title=Apple's CPU architect Jim Keller moves back to AMD |author=Charlie Demerjian |date=1 August 2012 |work=[[SemiAccurate]] }}</ref> In 2012, he returned to AMD to work on the [[AMD K12]]<ref name=decryptedtech>{{cite news |url=http://www.decryptedtech.com/news/amd-brings-k7-k8-creator-jim-keller-back-into-the-fold |title=AMD Brings K7/K8 Creator, Jim Keller, Back Into the Fold |author=Sean Kalinich |date=27 June 2014 |work=decryptedtech.com }}</ref> and [[AMD Zen|Zen]] microarchitectures,<ref name=kitguru>{{cite news |url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/ |title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be |author=Anton Shilov |date=11 September 2014 |work=kitguru.net }}</ref><ref name=wccftech>{{cite news |url=http://wccftech.com/amd-confirms-development-of-high-performance-x86-core-with-completely-new-architecture/ |title=AMD Confirms Development of High-Performance x86 Core With Completely New Architecture |author=Hassan Mujtaba |date=5 May 2014 |work=WCCFtech }}</ref> particularly on the low-power/embedded versions.<ref name=cultofmac /><ref name=allthingsd />

== Career ==
Jim Keller was working at [[Digital Equipment Corporation|DEC]] until 1998, where he was involved in designing the [[Alpha 21164]] and [[Alpha 21264|21264]] processors.<ref name=anandtech /><ref name=xbitlabs /> In 1998 he moved to AMD, where he worked to launch the AMD [[Athlon]] (K7) processor and was the lead architect of the [[AMD K8]] microarchitecture,<ref name=9to5mac>{{cite news |url=http://9to5mac.com/2012/08/01/apple-cpu-guru-jim-keller-who-came-with-pa-semi-deal-departs-back-to-amd-to-lead-group-under-mark-papermaster/ |title=Apple CPU guru Jim Keller, who came with PA Semi deal, departs back to AMD to lead group under Mark Papermaster |author=Seth Weintraub |date=1 August 2012 |work=9to5Mac }}</ref> which also included designing the x86-64 instruction set and HyperTransport interconnect mainly used for [[multiprocessor]] communications.<ref name=anandtech />

In 1999, he left AMD to work at SiByte to design [[MIPS instruction set|MIPS]]-based processors for 1 Gbit/s network interfaces and other devices.<ref name=xbitlabs /><ref name=semiaccurate /><ref>{{cite web |url=http://www.techspot.com/news/49611-apple-chip-designer-jim-keller-heads-back-to-amd.html |title=Apple chip designer Jim Keller heads back to AMD |author=Jose Vilches |date=1 August 2012 |work=[[TechSpot]] }}</ref> In November 2000, SiByte was acquired by [[Broadcom]],<ref>{{cite news |url=http://www.wsj.com/articles/SB973519053768422247 |title=Broadcom Agrees to Acquire SiByte for $2 Billion in Stock |author=Molly Williams |date=7 November 2000 |work=[[Wall Street Journal]] }}</ref> where he continued as chief architect<ref name=theverge /> until 2004.<ref name=anandtech />

In 2004 he moved to serve as the Vice President of Engineering at [[P.A. Semi]],<ref name=anandtech /><ref name=itworld /> a company specializing in low-power mobile processors.<ref name=xbitlabs /> P.A. Semi was acquired by Apple in 2008, and Keller followed,<ref name=thenextweb /><ref name=9to5mac /> becoming part of a team to design the Apple A4 and A5 [[system-on-a-chip]] mobile processors. These processors were used in several Apple products, including [[iPhone 4]], [[iPhone 4S|4S]], [[iPad]] and [[iPad 2]].

In August 2012, Jim Keller returned to AMD, where his primary task is to design a new generation [[microarchitecture]]<ref name=computing /><ref name=itworld /><ref name=wccftech /> called [[Zen (microarchitecture)|Zen]].<ref name=kitguru /> After years of disappointing processors from AMD, the Zen is hoped to restore AMD's position in the high-end [[x86]] processor market.<ref name=anandtech /><ref name=decryptedtech />

== References ==
{{Reflist}}

[[Category:Living people]]
[[Category:Advanced Micro Devices people]]
[[Category:American engineers]]
[[Category:Computer hardware engineers]]
[[Category:Apple Inc. ex-employees]]

{{engineer-stub}}

Jim Keller

2015-05-15T08:20:03Z

Intgr: Convert to citation template

{{Infobox person
| name = Jim Keller
| image = 
| alt =
| caption =
| birth_name = 
| birth_date = 
| birth_place =
| death_date = 
| death_place =
| nationality =
| other_names =
| occupation = Chief Architect of Microprocessor Cores and Corporate Vice President, Advanced Micro Devices<ref>{{cite web |url=http://www.bloomberg.com/research/stocks/people/person.asp?personId=215060089&ticker=AMD&previousCapId=168864&previousTitle=ADVANCED%20MICRO%20DEVICES |title=Jim Keller: Executive Profile & Biography |work=[[Bloomberg Business]] |accessdate={{date|2015-05-14}} }}</ref><ref name=bit-tech>{{cite web |url=http://www.bit-tech.net/news/hardware/2012/08/02/amd-jim-keller/1 |title=AMD re-hires Athlon 64 K8 designer Jim Keller |author=Gareth Halfacree |date=2 August 2012 |work=bit-tech }}</ref>
| years_active =
| known_for = {{Plainlist|
* AMD K7
* AMD K8 (lead architect)
* Apple A4, A5
* x86-64 (coauthor)
* HyperTransport (coauthor)
}}
| notable_works =
}}

'''Jim Keller''' is a [[microprocessor]] [[engineer]] most well known for his work at [[AMD]] and [[Apple Inc.|Apple]]. He was the lead architect of [[AMD K8]] microarchitecture<ref name=anandtech>{{cite news |url=http://www.anandtech.com/show/6129/apple-a4a5-designer-k8-lead-architect-jim-keller-returns-to-amd |title=Apple A4/A5 Designer & K8 Lead Architect, Jim Keller, Returns to AMD |author=[[Anand Lal Shimpi]] |date=1 August 2012 |work=[[AnandTech]] }}</ref><ref name=xbitlabs>{{cite news |url=http://www.xbitlabs.com/news/cpu/display/20120801190422_Return_of_the_King_AMD_K7_and_K8_Designer_Jim_Keller_Back_at_AMD.html |title=Return of the King: AMD K7 and K8 Designer Jim Keller Back at AMD |author=Anton Shilov |date=1 August 2012 |work=X-bit Labs }}</ref><ref name=computing>{{cite news |url=http://www.computing.co.uk/ctg/news/2344223/amd-to-design-new-micro-architecture-for-2015-launch-under-chip-guru-jim-keller |title=AMD to design new micro-architecture for 2015 launch under chip guru Jim Keller |author=Graeme Burton |date=12 May 2014 |work=computing.co.uk }}</ref> (including the original [[Athlon 64]])<ref name=anandtech /><ref name=thenextweb>{{cite news |url=http://thenextweb.com/insider/2012/08/01/apples-cpu-architect-jim-keller-departs-to-head-up-chipmaker-amds-processor-group/ |title=Apple's CPU Architect Jim Keller Jumps To AMD |author=Robin Wauters |date=1 August 2012 |work=[[The Next Web]] }}</ref><ref name=cultofmac>{{cite news |url=http://www.cultofmac.com/182296/amd-hires-ax-series-architect-jim-keller-away-from-apple-to-report-to-mark-papermaster/ |title=AMD Hires Ax Series Architect Jim Keller Away From Apple To Report To Mark Papermaster |author=John Brownlee |date=1 August 2012 |work=Cult of Mac}}</ref> and was involved in designing the [[Athlon]] (K7)<ref name=computing /> and [[Apple A4]]/[[Apple A5|A5]] processors.<ref name=anandtech /><ref name=venturebeat>{{cite news |url=http://venturebeat.com/2012/08/01/apple-cpu-jim-keller-amd/ |title=Apple CPU lead Jim Keller heads back to AMD as chief architect |author=Devindra Hardawar |date=1 August 2012 |work=[[VentureBeat]] }}</ref><ref name=theverge>{{cite news |url=http://www.theverge.com/2012/8/1/3212406/jim-keller-joins-amd-vp-chief-architect |title=Former Apple chip designer Jim Keller joins AMD as chief architect and VP |author=Adi Robertson |date=1 August 2012 |publisher=Vox Media |work=[[The Verge]] }}</ref><ref name=allthingsd>{{cite news |url=http://allthingsd.com/20120801/amd-hires-apples-head-chip-designer/ |title=AMD Hires Apple's Head Chip Designer |author=Arik Hesseldahl |date=1 August 2012 |work=[[AllThingsD]] }}</ref> He was also the coauthor of the specifications for the [[x86-64]] instruction set<ref name=venturebeat /><ref name=itworld>{{cite news |url=http://www.itworld.com/article/2693371/is-amd-finally-ready-to-give-intel-a-real-fight.html |title=AMD roadmap: Is AMD finally ready to give Intel a real fight? |author=Andy Patrizio |date=16 May 2014 |work=ITworld}}</ref> and [[HyperTransport]] interconnect.<ref name=anandtech/><ref name=itworld /><ref name=semiaccurate>{{cite news |url=http://semiaccurate.com/2012/08/01/apples-cpu-architect-jim-keller-moves-back-to-amd/ |title=Apple's CPU architect Jim Keller moves back to AMD |author=Charlie Demerjian |date=1 August 2012 |work=[[SemiAccurate]] }}</ref> In 2012, he returned to AMD to work on the [[AMD K12]]<ref name=decryptedtech>{{cite news |url=http://www.decryptedtech.com/news/amd-brings-k7-k8-creator-jim-keller-back-into-the-fold |title=AMD Brings K7/K8 Creator, Jim Keller, Back Into the Fold |author=Sean Kalinich |date=27 June 2014 |work=decryptedtech.com }}</ref> and [[AMD Zen|Zen]] microarchitectures,<ref name=kitguru>{{cite news |url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/ |title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be |author=Anton Shilov |date=11 September 2014 |work=kitguru.net }}</ref><ref name=wccftech>{{cite news |url=http://wccftech.com/amd-confirms-development-of-high-performance-x86-core-with-completely-new-architecture/ |title=AMD Confirms Development of High-Performance x86 Core With Completely New Architecture |author=Hassan Mujtaba |date=5 May 2014 |work=WCCFtech }}</ref> particularly on the low-power/embedded versions.<ref name=cultofmac /><ref name=allthingsd />

== Career ==
Jim Keller was working at [[Digital Equipment Corporation|DEC]] until 1998, where he was involved in designing the [[Alpha 21164]] and [[Alpha 21264|21264]] processors.<ref name=anandtech /><ref name=xbitlabs /> In 1998 he moved to AMD, where he worked to launch the AMD [[Athlon]] (K7) processor and was the lead architect of the [[AMD K8]] microarchitecture,<ref name=9to5mac>{{cite news |url=http://9to5mac.com/2012/08/01/apple-cpu-guru-jim-keller-who-came-with-pa-semi-deal-departs-back-to-amd-to-lead-group-under-mark-papermaster/ |title=Apple CPU guru Jim Keller, who came with PA Semi deal, departs back to AMD to lead group under Mark Papermaster |author=Seth Weintraub |date=1 August 2012 |work=9to5Mac }}</ref> which also included designing the x86-64 instruction set and HyperTransport interconnect mainly used for [[multiprocessor]] communications.<ref name=anandtech />

In 1999, he left AMD to work at SiByte to design [[MIPS instruction set|MIPS]]-based processors for 1 Gbit/s network interfaces and other devices.<ref name=xbitlabs /><ref name=semiaccurate /><ref>{{cite web |url=http://www.techspot.com/news/49611-apple-chip-designer-jim-keller-heads-back-to-amd.html |title=Apple chip designer Jim Keller heads back to AMD |author=Jose Vilches |date=1 August 2012 |work=[[TechSpot]] }}</ref> In November 2000, SiByte was acquired by [[Broadcom]],<ref>{{cite news |url=http://www.wsj.com/articles/SB973519053768422247 |title=Broadcom Agrees to Acquire SiByte for $2 Billion in Stock |author=Molly Williams |date=7 November 2000 |work=[[Wall Street Journal]] }}</ref> where he continued as chief architect<ref name=theverge /> until 2004.<ref name=anandtech />

In 2004 he moved to serve as the Vice President of Engineering at [[P.A. Semi]],<ref name=anandtech /><ref name=itworld /> a company specializing in low-power mobile processors.<ref name=xbitlabs /> P.A. Semi was acquired by Apple in 2008, and Keller followed,<ref name=thenextweb /><ref name=9to5mac /> becoming part of a team to design the Apple A4 and A5 [[system-on-a-chip]] mobile processors. These processors were used in several Apple products, including [[iPhone 4]], [[iPhone 4S|4S]], [[iPad]] and [[iPad 2]].

In August 2012, Jim Keller returned to AMD, where his primary task is to design a new generation [[microarchitecture]]<ref name=computing /><ref name=itworld /><ref name=wccftech /> called [[AMD Zen]].<ref name=kitguru /> After years disappointing processors from AMD, the Zen is hoped to restore AMD's position in the high-end [[x86]] processor market.<ref name=anandtech /><ref name=decryptedtech />

== References ==
{{Reflist}}

[[Category:Living people]]
[[Category:Advanced Micro Devices people]]
[[Category:American engineers]]
[[Category:Computer hardware engineers]]
[[Category:Apple Inc. ex-employees]]

{{engineer-stub}}

Jim Keller

2015-05-15T08:16:27Z

Intgr: /* Career */ +ref

{{Infobox person
| name = Jim Keller
| image = 
| alt =
| caption =
| birth_name = 
| birth_date = 
| birth_place =
| death_date = 
| death_place =
| nationality =
| other_names =
| occupation = Chief Architect of Microprocessor Cores and Corporate Vice President, Advanced Micro Devices<ref>{{cite web |url=http://www.bloomberg.com/research/stocks/people/person.asp?personId=215060089&ticker=AMD&previousCapId=168864&previousTitle=ADVANCED%20MICRO%20DEVICES |title=Jim Keller: Executive Profile & Biography |work=[[Bloomberg Business]] |accessdate={{date|2015-05-14}} }}</ref><ref name=bit-tech>{{cite web |url=http://www.bit-tech.net/news/hardware/2012/08/02/amd-jim-keller/1 |title=AMD re-hires Athlon 64 K8 designer Jim Keller |author=Gareth Halfacree |date=2 August 2012 |work=bit-tech }}</ref>
| years_active =
| known_for = {{Plainlist|
* AMD K7
* AMD K8 (lead architect)
* Apple A4, A5
* x86-64 (coauthor)
* HyperTransport (coauthor)
}}
| notable_works =
}}

'''Jim Keller''' is a [[microprocessor]] [[engineer]] most well known for his work at [[AMD]] and [[Apple Inc.|Apple]]. He was the lead architect of [[AMD K8]] microarchitecture<ref name=anandtech>{{cite news |url=http://www.anandtech.com/show/6129/apple-a4a5-designer-k8-lead-architect-jim-keller-returns-to-amd |title=Apple A4/A5 Designer & K8 Lead Architect, Jim Keller, Returns to AMD |author=[[Anand Lal Shimpi]] |date=1 August 2012 |work=[[AnandTech]] }}</ref><ref name=xbitlabs>{{cite news |url=http://www.xbitlabs.com/news/cpu/display/20120801190422_Return_of_the_King_AMD_K7_and_K8_Designer_Jim_Keller_Back_at_AMD.html |title=Return of the King: AMD K7 and K8 Designer Jim Keller Back at AMD |author=Anton Shilov |date=1 August 2012 |work=X-bit Labs }}</ref><ref name=computing>{{cite news |url=http://www.computing.co.uk/ctg/news/2344223/amd-to-design-new-micro-architecture-for-2015-launch-under-chip-guru-jim-keller |title=AMD to design new micro-architecture for 2015 launch under chip guru Jim Keller |author=Graeme Burton |date=12 May 2014 |work=computing.co.uk }}</ref> (including the original [[Athlon 64]])<ref name=anandtech /><ref name=thenextweb>{{cite news |url=http://thenextweb.com/insider/2012/08/01/apples-cpu-architect-jim-keller-departs-to-head-up-chipmaker-amds-processor-group/ |title=Apple's CPU Architect Jim Keller Jumps To AMD |author=Robin Wauters |date=1 August 2012 |work=[[The Next Web]] }}</ref><ref name=cultofmac>{{cite news |url=http://www.cultofmac.com/182296/amd-hires-ax-series-architect-jim-keller-away-from-apple-to-report-to-mark-papermaster/ |title=AMD Hires Ax Series Architect Jim Keller Away From Apple To Report To Mark Papermaster |author=John Brownlee |date=1 August 2012 |work=Cult of Mac}}</ref> and was involved in designing the [[Athlon]] (K7)<ref name=computing /> and [[Apple A4]]/[[Apple A5|A5]] processors.<ref name=anandtech /><ref name=venturebeat>{{cite news |url=http://venturebeat.com/2012/08/01/apple-cpu-jim-keller-amd/ |title=Apple CPU lead Jim Keller heads back to AMD as chief architect |author=Devindra Hardawar |date=1 August 2012 |work=[[VentureBeat]] }}</ref><ref name=theverge>{{cite news |url=http://www.theverge.com/2012/8/1/3212406/jim-keller-joins-amd-vp-chief-architect |title=Former Apple chip designer Jim Keller joins AMD as chief architect and VP |author=Adi Robertson |date=1 August 2012 |publisher=Vox Media |work=[[The Verge]] }}</ref><ref name=allthingsd>{{cite news |url=http://allthingsd.com/20120801/amd-hires-apples-head-chip-designer/ |title=AMD Hires Apple's Head Chip Designer |author=Arik Hesseldahl |date=1 August 2012 |work=[[AllThingsD]] }}</ref> He was also the coauthor of the specifications for the [[x86-64]] instruction set<ref name=venturebeat /><ref name=itworld>{{cite news |url=http://www.itworld.com/article/2693371/is-amd-finally-ready-to-give-intel-a-real-fight.html |title=AMD roadmap: Is AMD finally ready to give Intel a real fight? |author=Andy Patrizio |date=16 May 2014 |work=ITworld}}</ref> and [[HyperTransport]] interconnect.<ref name=anandtech/><ref name=itworld /><ref name=semiaccurate>{{cite news |url=http://semiaccurate.com/2012/08/01/apples-cpu-architect-jim-keller-moves-back-to-amd/ |title=Apple's CPU architect Jim Keller moves back to AMD |author=Charlie Demerjian |date=1 August 2012 |work=[[SemiAccurate]] }}</ref> In 2012, he returned to AMD to work on the [[AMD K12]]<ref name=decryptedtech>{{cite news |url=http://www.decryptedtech.com/news/amd-brings-k7-k8-creator-jim-keller-back-into-the-fold |title=AMD Brings K7/K8 Creator, Jim Keller, Back Into the Fold |author=Sean Kalinich |date=27 June 2014 |work=decryptedtech.com }}</ref> and [[AMD Zen|Zen]] microarchitectures,<ref name=kitguru>{{cite news |url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/ |title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be |author=Anton Shilov |date=11 September 2014 |work=kitguru.net }}</ref><ref name=wccftech>{{cite news |url=http://wccftech.com/amd-confirms-development-of-high-performance-x86-core-with-completely-new-architecture/ |title=AMD Confirms Development of High-Performance x86 Core With Completely New Architecture |author=Hassan Mujtaba |date=5 May 2014 |work=WCCFtech }}</ref> particularly on the low-power/embedded versions.<ref name=cultofmac /><ref name=allthingsd />

== Career ==
Jim Keller was working at [[Digital Equipment Corporation|DEC]] until 1998, where he was involved in designing the [[Alpha 21164]] and [[Alpha 21264|21264]] processors.<ref name=anandtech /><ref name=xbitlabs /> In 1998 he moved to AMD, where he worked to launch the AMD [[Athlon]] (K7) processor and was the lead architect of the [[AMD K8]] microarchitecture,<ref name=9to5mac>{{cite news |url=http://9to5mac.com/2012/08/01/apple-cpu-guru-jim-keller-who-came-with-pa-semi-deal-departs-back-to-amd-to-lead-group-under-mark-papermaster/ |title=Apple CPU guru Jim Keller, who came with PA Semi deal, departs back to AMD to lead group under Mark Papermaster |author=Seth Weintraub |date=1 August 2012 |work=9to5Mac }}</ref> which also included designing the x86-64 instruction set and HyperTransport interconnect mainly used for [[multiprocessor]] communications.<ref name=anandtech />

In 1999, he left AMD to work at SiByte to design [[MIPS instruction set|MIPS]]-based processors for 1 Gbit/s network interfaces and other devices.<ref name=xbitlabs /><ref name=semiaccurate /><ref>http://www.techspot.com/news/49611-apple-chip-designer-jim-keller-heads-back-to-amd.html</ref> In November 2000, SiByte was acquired by [[Broadcom]],<ref>{{cite news |url=http://www.wsj.com/articles/SB973519053768422247 |title=Broadcom Agrees to Acquire SiByte for $2 Billion in Stock |author=Molly Williams |date=7 November 2000 |work=[[Wall Street Journal]] }}</ref> where he continued as chief architect<ref name=theverge /> until 2004.<ref name=anandtech />

In 2004 he moved to serve as the Vice President of Engineering at [[P.A. Semi]],<ref name=anandtech /><ref name=itworld /> a company specializing in low-power mobile processors.<ref name=xbitlabs /> P.A. Semi was acquired by Apple in 2008, and Keller followed,<ref name=thenextweb /><ref name=9to5mac /> becoming part of a team to design the Apple A4 and A5 [[system-on-a-chip]] mobile processors. These processors were used in several Apple products, including [[iPhone 4]], [[iPhone 4S|4S]], [[iPad]] and [[iPad 2]].

In August 2012, Jim Keller returned to AMD, where his primary task is to design a new generation [[microarchitecture]]<ref name=computing /><ref name=itworld /><ref name=wccftech /> called [[AMD Zen]].<ref name=kitguru /> After years disappointing processors from AMD, the Zen is hoped to restore AMD's position in the high-end [[x86]] processor market.<ref name=anandtech /><ref name=decryptedtech />

== References ==
{{Reflist}}

[[Category:Living people]]
[[Category:Advanced Micro Devices people]]
[[Category:American engineers]]
[[Category:Computer hardware engineers]]
[[Category:Apple Inc. ex-employees]]

{{engineer-stub}}

Jim Keller

2015-05-15T08:06:51Z

Intgr: /* References */ New category Category:Apple Inc. ex-employees

{{Infobox person
| name = Jim Keller
| image = 
| alt =
| caption =
| birth_name = 
| birth_date = 
| birth_place =
| death_date = 
| death_place =
| nationality =
| other_names =
| occupation = Chief Architect of Microprocessor Cores and Corporate Vice President, Advanced Micro Devices<ref>{{cite web |url=http://www.bloomberg.com/research/stocks/people/person.asp?personId=215060089&ticker=AMD&previousCapId=168864&previousTitle=ADVANCED%20MICRO%20DEVICES |title=Jim Keller: Executive Profile & Biography |work=[[Bloomberg Business]] |accessdate={{date|2015-05-14}} }}</ref><ref name=bit-tech>{{cite web |url=http://www.bit-tech.net/news/hardware/2012/08/02/amd-jim-keller/1 |title=AMD re-hires Athlon 64 K8 designer Jim Keller |author=Gareth Halfacree |date=2 August 2012 |work=bit-tech }}</ref>
| years_active =
| known_for = {{Plainlist|
* AMD K7
* AMD K8 (lead architect)
* Apple A4, A5
* x86-64 (coauthor)
* HyperTransport (coauthor)
}}
| notable_works =
}}

'''Jim Keller''' is a [[microprocessor]] [[engineer]] most well known for his work at [[AMD]] and [[Apple Inc.|Apple]]. He was the lead architect of [[AMD K8]] microarchitecture<ref name=anandtech>{{cite news |url=http://www.anandtech.com/show/6129/apple-a4a5-designer-k8-lead-architect-jim-keller-returns-to-amd |title=Apple A4/A5 Designer & K8 Lead Architect, Jim Keller, Returns to AMD |author=[[Anand Lal Shimpi]] |date=1 August 2012 |work=[[AnandTech]] }}</ref><ref name=xbitlabs>{{cite news |url=http://www.xbitlabs.com/news/cpu/display/20120801190422_Return_of_the_King_AMD_K7_and_K8_Designer_Jim_Keller_Back_at_AMD.html |title=Return of the King: AMD K7 and K8 Designer Jim Keller Back at AMD |author=Anton Shilov |date=1 August 2012 |work=X-bit Labs }}</ref><ref name=computing>{{cite news |url=http://www.computing.co.uk/ctg/news/2344223/amd-to-design-new-micro-architecture-for-2015-launch-under-chip-guru-jim-keller |title=AMD to design new micro-architecture for 2015 launch under chip guru Jim Keller |author=Graeme Burton |date=12 May 2014 |work=computing.co.uk }}</ref> (including the original [[Athlon 64]])<ref name=anandtech /><ref name=thenextweb>{{cite news |url=http://thenextweb.com/insider/2012/08/01/apples-cpu-architect-jim-keller-departs-to-head-up-chipmaker-amds-processor-group/ |title=Apple's CPU Architect Jim Keller Jumps To AMD |author=Robin Wauters |date=1 August 2012 |work=[[The Next Web]] }}</ref><ref name=cultofmac>{{cite news |url=http://www.cultofmac.com/182296/amd-hires-ax-series-architect-jim-keller-away-from-apple-to-report-to-mark-papermaster/ |title=AMD Hires Ax Series Architect Jim Keller Away From Apple To Report To Mark Papermaster |author=John Brownlee |date=1 August 2012 |work=Cult of Mac}}</ref> and was involved in designing the [[Athlon]] (K7)<ref name=computing /> and [[Apple A4]]/[[Apple A5|A5]] processors.<ref name=anandtech /><ref name=venturebeat>{{cite news |url=http://venturebeat.com/2012/08/01/apple-cpu-jim-keller-amd/ |title=Apple CPU lead Jim Keller heads back to AMD as chief architect |author=Devindra Hardawar |date=1 August 2012 |work=[[VentureBeat]] }}</ref><ref name=theverge>{{cite news |url=http://www.theverge.com/2012/8/1/3212406/jim-keller-joins-amd-vp-chief-architect |title=Former Apple chip designer Jim Keller joins AMD as chief architect and VP |author=Adi Robertson |date=1 August 2012 |publisher=Vox Media |work=[[The Verge]] }}</ref><ref name=allthingsd>{{cite news |url=http://allthingsd.com/20120801/amd-hires-apples-head-chip-designer/ |title=AMD Hires Apple's Head Chip Designer |author=Arik Hesseldahl |date=1 August 2012 |work=[[AllThingsD]] }}</ref> He was also the coauthor of the specifications for the [[x86-64]] instruction set<ref name=venturebeat /><ref name=itworld>{{cite news |url=http://www.itworld.com/article/2693371/is-amd-finally-ready-to-give-intel-a-real-fight.html |title=AMD roadmap: Is AMD finally ready to give Intel a real fight? |author=Andy Patrizio |date=16 May 2014 |work=ITworld}}</ref> and [[HyperTransport]] interconnect.<ref name=anandtech/><ref name=itworld /><ref name=semiaccurate>{{cite news |url=http://semiaccurate.com/2012/08/01/apples-cpu-architect-jim-keller-moves-back-to-amd/ |title=Apple's CPU architect Jim Keller moves back to AMD |author=Charlie Demerjian |date=1 August 2012 |work=[[SemiAccurate]] }}</ref> In 2012, he returned to AMD to work on the [[AMD K12]]<ref name=decryptedtech>{{cite news |url=http://www.decryptedtech.com/news/amd-brings-k7-k8-creator-jim-keller-back-into-the-fold |title=AMD Brings K7/K8 Creator, Jim Keller, Back Into the Fold |author=Sean Kalinich |date=27 June 2014 |work=decryptedtech.com }}</ref> and [[AMD Zen|Zen]] microarchitectures,<ref name=kitguru>{{cite news |url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/ |title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be |author=Anton Shilov |date=11 September 2014 |work=kitguru.net }}</ref><ref name=wccftech>{{cite news |url=http://wccftech.com/amd-confirms-development-of-high-performance-x86-core-with-completely-new-architecture/ |title=AMD Confirms Development of High-Performance x86 Core With Completely New Architecture |author=Hassan Mujtaba |date=5 May 2014 |work=WCCFtech }}</ref> particularly on the low-power/embedded versions.<ref name=cultofmac /><ref name=allthingsd />

== Career ==
Jim Keller was working at [[Digital Equipment Corporation|DEC]] until 1998, where he was involved in designing the [[Alpha 21164]] and [[Alpha 21264|21264]] processors.<ref name=anandtech /><ref name=xbitlabs /> In 1998 he moved to AMD, where he worked to launch the AMD [[Athlon]] (K7) processor and was the lead architect of the [[AMD K8]] microarchitecture,<ref name=9to5mac>{{cite news |url=http://9to5mac.com/2012/08/01/apple-cpu-guru-jim-keller-who-came-with-pa-semi-deal-departs-back-to-amd-to-lead-group-under-mark-papermaster/ |title=Apple CPU guru Jim Keller, who came with PA Semi deal, departs back to AMD to lead group under Mark Papermaster |author=Seth Weintraub |date=1 August 2012 |work=9to5Mac }}</ref> which also included designing the x86-64 instruction set and HyperTransport interconnect mainly used for [[multiprocessor]] communications.<ref name=anandtech />

In 1999, he left AMD to work at SiByte to design [[MIPS instruction set|MIPS]]-based processors for 1 Gbit/s network interfaces and other devices.<ref name=xbitlabs /><ref name=semiaccurate /> In November 2000, SiByte was acquired by [[Broadcom]],<ref>{{cite news |url=http://www.wsj.com/articles/SB973519053768422247 |title=Broadcom Agrees to Acquire SiByte for $2 Billion in Stock |author=Molly Williams |date=7 November 2000 |work=[[Wall Street Journal]] }}</ref> where he continued as chief architect<ref name=theverge /> until 2004.<ref name=anandtech />

In 2004 he moved to serve as the Vice President of Engineering at [[P.A. Semi]],<ref name=anandtech /><ref name=itworld /> a company specializing in low-power mobile processors.<ref name=xbitlabs /> P.A. Semi was acquired by Apple in 2008, and Keller followed,<ref name=thenextweb /><ref name=9to5mac /> becoming part of a team to design the Apple A4 and A5 [[system-on-a-chip]] mobile processors. These processors were used in several Apple products, including [[iPhone 4]], [[iPhone 4S|4S]], [[iPad]] and [[iPad 2]].

In August 2012, Jim Keller returned to AMD, where his primary task is to design a new generation [[microarchitecture]]<ref name=computing /><ref name=itworld /><ref name=wccftech /> called [[AMD Zen]].<ref name=kitguru /> After years disappointing processors from AMD, the Zen is hoped to restore AMD's position in the high-end [[x86]] processor market.<ref name=anandtech /><ref name=decryptedtech />

== References ==
{{Reflist}}

[[Category:Living people]]
[[Category:Advanced Micro Devices people]]
[[Category:American engineers]]
[[Category:Computer hardware engineers]]
[[Category:Apple Inc. ex-employees]]

{{engineer-stub}}

Zen (Mikroarchitektur)

2015-05-15T07:22:39Z

Intgr: Propose merge into AMD Zen

{{Merge to|AMD Zen}}

'''Zen''' is an upcoming chip microarchitecture created by [[AMD]]. The team in charge of the Zen microarchitecture is being led by [[Jim Keller (engineer)|Jim Keller]], the engineer also responsible for the [[Athlon 64]].<ref name="techspot">{{cite web|url=http://www.techspot.com/news/60626-tech-reading-amd-zen-comeback.html|title=Weekend tech reading: AMD 'Zen' and their return to high-end CPUs, tracking Windows pirates - TechSpot|publisher=techspot.com|accessdate=2015-05-12}}</ref><ref name="techreport">{{cite web|url=http://techreport.com/review/28228/amd-zen-chips-headed-to-desktops-servers-in-2016|title=AMD: Zen chips headed to desktops, servers in 2016 - The Tech Report - Page 1|publisher=techreport.com|accessdate=2015-05-12}}</ref>

==Architecture==

* According to [[AMD]], Zen's main focus will be on increasing per-core performance rather than core count or multi-threading performance.<ref name="kitguru">{{cite web|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/|title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be | KitGuru|publisher=kitguru.net|accessdate=2015-05-12}}</ref>
* Zen will be created on the more efficient 14 nm node, rather than 32 nm.
* Zen will have a unified AM4 socket with its GPU-equipped APU counterparts.<ref name="pcgamer">{{cite web|url=http://www.pcgamer.com/amds-next-gen-zen-cpu-due-in-2016/|title=AMD's next-gen Zen CPU due in 2016 - PC Gamer|publisher=pcgamer.com|accessdate=2015-05-12}}</ref>

==Release date==

Zen is said to be released some time in 2016.<ref name="pcgamer"/>

==See also==

* [[Bulldozer (microarchitecture)]]
* [[Steamroller (microarchitecture)]]
* [[Jim Keller (engineer)]]

==References==
{{reflist}}

[[Category:Advanced Micro Devices microarchitectures]]

Zen (Mikroarchitektur)

2015-05-15T07:21:40Z

Intgr: /* See also */ Avoid redirect

'''Zen''' is an upcoming chip microarchitecture created by [[AMD]]. The team in charge of the Zen microarchitecture is being led by [[Jim Keller (engineer)|Jim Keller]], the engineer also responsible for the [[Athlon 64]].<ref name="techspot">{{cite web|url=http://www.techspot.com/news/60626-tech-reading-amd-zen-comeback.html|title=Weekend tech reading: AMD 'Zen' and their return to high-end CPUs, tracking Windows pirates - TechSpot|publisher=techspot.com|accessdate=2015-05-12}}</ref><ref name="techreport">{{cite web|url=http://techreport.com/review/28228/amd-zen-chips-headed-to-desktops-servers-in-2016|title=AMD: Zen chips headed to desktops, servers in 2016 - The Tech Report - Page 1|publisher=techreport.com|accessdate=2015-05-12}}</ref>

==Architecture==

* According to [[AMD]], Zen's main focus will be on increasing per-core performance rather than core count or multi-threading performance.<ref name="kitguru">{{cite web|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/|title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be | KitGuru|publisher=kitguru.net|accessdate=2015-05-12}}</ref>
* Zen will be created on the more efficient 14 nm node, rather than 32 nm.
* Zen will have a unified AM4 socket with its GPU-equipped APU counterparts.<ref name="pcgamer">{{cite web|url=http://www.pcgamer.com/amds-next-gen-zen-cpu-due-in-2016/|title=AMD's next-gen Zen CPU due in 2016 - PC Gamer|publisher=pcgamer.com|accessdate=2015-05-12}}</ref>

==Release date==

Zen is said to be released some time in 2016.<ref name="pcgamer"/>

==See also==

* [[Bulldozer (microarchitecture)]]
* [[Steamroller (microarchitecture)]]
* [[Jim Keller (engineer)]]

==References==
{{reflist}}

[[Category:Advanced Micro Devices microarchitectures]]

Zen (Mikroarchitektur)

2015-05-15T07:21:12Z

Intgr: Avoid redirect

'''Zen''' is an upcoming chip microarchitecture created by [[AMD]]. The team in charge of the Zen microarchitecture is being led by [[Jim Keller (engineer)|Jim Keller]], the engineer also responsible for the [[Athlon 64]].<ref name="techspot">{{cite web|url=http://www.techspot.com/news/60626-tech-reading-amd-zen-comeback.html|title=Weekend tech reading: AMD 'Zen' and their return to high-end CPUs, tracking Windows pirates - TechSpot|publisher=techspot.com|accessdate=2015-05-12}}</ref><ref name="techreport">{{cite web|url=http://techreport.com/review/28228/amd-zen-chips-headed-to-desktops-servers-in-2016|title=AMD: Zen chips headed to desktops, servers in 2016 - The Tech Report - Page 1|publisher=techreport.com|accessdate=2015-05-12}}</ref>

==Architecture==

* According to [[AMD]], Zen's main focus will be on increasing per-core performance rather than core count or multi-threading performance.<ref name="kitguru">{{cite web|url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/|title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be | KitGuru|publisher=kitguru.net|accessdate=2015-05-12}}</ref>
* Zen will be created on the more efficient 14 nm node, rather than 32 nm.
* Zen will have a unified AM4 socket with its GPU-equipped APU counterparts.<ref name="pcgamer">{{cite web|url=http://www.pcgamer.com/amds-next-gen-zen-cpu-due-in-2016/|title=AMD's next-gen Zen CPU due in 2016 - PC Gamer|publisher=pcgamer.com|accessdate=2015-05-12}}</ref>

==Release date==

Zen is said to be released some time in 2016.<ref name="pcgamer"/>

==See also==

* [[Bulldozer (microarchitecture)]]
* [[Steamroller (microarchitecture)]]
* [[Jim Keller (chip architect)]]

==References==
{{reflist}}

[[Category:Advanced Micro Devices microarchitectures]]

Jim Keller

2015-05-15T07:14:44Z

Intgr: +citation

{{Infobox person
| name = Jim Keller
| image = 
| alt =
| caption =
| birth_name = 
| birth_date = 
| birth_place =
| death_date = 
| death_place =
| nationality =
| other_names =
| occupation = Chief Architect of Microprocessor Cores and Corporate Vice President, Advanced Micro Devices<ref>{{cite web |url=http://www.bloomberg.com/research/stocks/people/person.asp?personId=215060089&ticker=AMD&previousCapId=168864&previousTitle=ADVANCED%20MICRO%20DEVICES |title=Jim Keller: Executive Profile & Biography |work=[[Bloomberg Business]] |accessdate={{date|2015-05-14}} }}</ref><ref name=bit-tech>{{cite web |url=http://www.bit-tech.net/news/hardware/2012/08/02/amd-jim-keller/1 |title=AMD re-hires Athlon 64 K8 designer Jim Keller |author=Gareth Halfacree |date=2 August 2012 |work=bit-tech }}</ref>
| years_active =
| known_for = {{Plainlist|
* AMD K7
* AMD K8 (lead architect)
* Apple A4, A5
* x86-64 (coauthor)
* HyperTransport (coauthor)
}}
| notable_works =
}}

'''Jim Keller''' is a [[microprocessor]] [[engineer]] most well known for his work at [[AMD]] and [[Apple Inc.|Apple]]. He was the lead architect of [[AMD K8]] microarchitecture<ref name=anandtech>{{cite news |url=http://www.anandtech.com/show/6129/apple-a4a5-designer-k8-lead-architect-jim-keller-returns-to-amd |title=Apple A4/A5 Designer & K8 Lead Architect, Jim Keller, Returns to AMD |author=[[Anand Lal Shimpi]] |date=1 August 2012 |work=[[AnandTech]] }}</ref><ref name=xbitlabs>{{cite news |url=http://www.xbitlabs.com/news/cpu/display/20120801190422_Return_of_the_King_AMD_K7_and_K8_Designer_Jim_Keller_Back_at_AMD.html |title=Return of the King: AMD K7 and K8 Designer Jim Keller Back at AMD |author=Anton Shilov |date=1 August 2012 |work=X-bit Labs }}</ref><ref name=computing>{{cite news |url=http://www.computing.co.uk/ctg/news/2344223/amd-to-design-new-micro-architecture-for-2015-launch-under-chip-guru-jim-keller |title=AMD to design new micro-architecture for 2015 launch under chip guru Jim Keller |author=Graeme Burton |date=12 May 2014 |work=computing.co.uk }}</ref> (including the original [[Athlon 64]])<ref name=anandtech /><ref name=thenextweb>{{cite news |url=http://thenextweb.com/insider/2012/08/01/apples-cpu-architect-jim-keller-departs-to-head-up-chipmaker-amds-processor-group/ |title=Apple's CPU Architect Jim Keller Jumps To AMD |author=Robin Wauters |date=1 August 2012 |work=[[The Next Web]] }}</ref><ref name=cultofmac>{{cite news |url=http://www.cultofmac.com/182296/amd-hires-ax-series-architect-jim-keller-away-from-apple-to-report-to-mark-papermaster/ |title=AMD Hires Ax Series Architect Jim Keller Away From Apple To Report To Mark Papermaster |author=John Brownlee |date=1 August 2012 |work=Cult of Mac}}</ref> and was involved in designing the [[Athlon]] (K7)<ref name=computing /> and [[Apple A4]]/[[Apple A5|A5]] processors.<ref name=anandtech /><ref name=venturebeat>{{cite news |url=http://venturebeat.com/2012/08/01/apple-cpu-jim-keller-amd/ |title=Apple CPU lead Jim Keller heads back to AMD as chief architect |author=Devindra Hardawar |date=1 August 2012 |work=[[VentureBeat]] }}</ref><ref name=theverge>{{cite news |url=http://www.theverge.com/2012/8/1/3212406/jim-keller-joins-amd-vp-chief-architect |title=Former Apple chip designer Jim Keller joins AMD as chief architect and VP |author=Adi Robertson |date=1 August 2012 |publisher=Vox Media |work=[[The Verge]] }}</ref><ref name=allthingsd>{{cite news |url=http://allthingsd.com/20120801/amd-hires-apples-head-chip-designer/ |title=AMD Hires Apple's Head Chip Designer |author=Arik Hesseldahl |date=1 August 2012 |work=[[AllThingsD]] }}</ref> He was also the coauthor of the specifications for the [[x86-64]] instruction set<ref name=venturebeat /><ref name=itworld>{{cite news |url=http://www.itworld.com/article/2693371/is-amd-finally-ready-to-give-intel-a-real-fight.html |title=AMD roadmap: Is AMD finally ready to give Intel a real fight? |author=Andy Patrizio |date=16 May 2014 |work=ITworld}}</ref> and [[HyperTransport]] interconnect.<ref name=anandtech/><ref name=itworld /><ref name=semiaccurate>{{cite news |url=http://semiaccurate.com/2012/08/01/apples-cpu-architect-jim-keller-moves-back-to-amd/ |title=Apple's CPU architect Jim Keller moves back to AMD |author=Charlie Demerjian |date=1 August 2012 |work=[[SemiAccurate]] }}</ref> In 2012, he returned to AMD to work on the [[AMD K12]]<ref name=decryptedtech>{{cite news |url=http://www.decryptedtech.com/news/amd-brings-k7-k8-creator-jim-keller-back-into-the-fold |title=AMD Brings K7/K8 Creator, Jim Keller, Back Into the Fold |author=Sean Kalinich |date=27 June 2014 |work=decryptedtech.com }}</ref> and [[AMD Zen|Zen]] microarchitectures,<ref name=kitguru>{{cite news |url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/ |title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be |author=Anton Shilov |date=11 September 2014 |work=kitguru.net }}</ref><ref name=wccftech>{{cite news |url=http://wccftech.com/amd-confirms-development-of-high-performance-x86-core-with-completely-new-architecture/ |title=AMD Confirms Development of High-Performance x86 Core With Completely New Architecture |author=Hassan Mujtaba |date=5 May 2014 |work=WCCFtech }}</ref> particularly on the low-power/embedded versions.<ref name=cultofmac /><ref name=allthingsd />

== Career ==
Jim Keller was working at [[Digital Equipment Corporation|DEC]] until 1998, where he was involved in designing the [[Alpha 21164]] and [[Alpha 21264|21264]] processors.<ref name=anandtech /><ref name=xbitlabs /> In 1998 he moved to AMD, where he worked to launch the AMD [[Athlon]] (K7) processor and was the lead architect of the [[AMD K8]] microarchitecture,<ref name=9to5mac>{{cite news |url=http://9to5mac.com/2012/08/01/apple-cpu-guru-jim-keller-who-came-with-pa-semi-deal-departs-back-to-amd-to-lead-group-under-mark-papermaster/ |title=Apple CPU guru Jim Keller, who came with PA Semi deal, departs back to AMD to lead group under Mark Papermaster |author=Seth Weintraub |date=1 August 2012 |work=9to5Mac }}</ref> which also included designing the x86-64 instruction set and HyperTransport interconnect mainly used for [[multiprocessor]] communications.<ref name=anandtech />

In 1999, he left AMD to work at SiByte to design [[MIPS instruction set|MIPS]]-based processors for 1 Gbit/s network interfaces and other devices.<ref name=xbitlabs /><ref name=semiaccurate /> In November 2000, SiByte was acquired by [[Broadcom]],<ref>{{cite news |url=http://www.wsj.com/articles/SB973519053768422247 |title=Broadcom Agrees to Acquire SiByte for $2 Billion in Stock |author=Molly Williams |date=7 November 2000 |work=[[Wall Street Journal]] }}</ref> where he continued as chief architect<ref name=theverge /> until 2004.<ref name=anandtech />

In 2004 he moved to serve as the Vice President of Engineering at [[P.A. Semi]],<ref name=anandtech /><ref name=itworld /> a company specializing in low-power mobile processors.<ref name=xbitlabs /> P.A. Semi was acquired by Apple in 2008, and Keller followed,<ref name=thenextweb /><ref name=9to5mac /> becoming part of a team to design the Apple A4 and A5 [[system-on-a-chip]] mobile processors. These processors were used in several Apple products, including [[iPhone 4]], [[iPhone 4S|4S]], [[iPad]] and [[iPad 2]].

In August 2012, Jim Keller returned to AMD, where his primary task is to design a new generation [[microarchitecture]]<ref name=computing /><ref name=itworld /><ref name=wccftech /> called [[AMD Zen]].<ref name=kitguru /> After years disappointing processors from AMD, the Zen is hoped to restore AMD's position in the high-end [[x86]] processor market.<ref name=anandtech /><ref name=decryptedtech />

== References ==
{{Reflist}}

[[Category:Living people]]
[[Category:Advanced Micro Devices people]]
[[Category:American engineers]]
[[Category:Computer hardware engineers]]
[[Category:Apple Inc. employees]]

{{engineer-stub}}

Jim Keller

2015-05-13T21:33:06Z

Intgr: /* top */ Add infobox

{{Infobox person
| name = Jim Keller
| image = 
| alt =
| caption =
| birth_name = 
| birth_date = 
| birth_place =
| death_date = 
| death_place =
| nationality =
| other_names =
| occupation = Chief Architect of Microprocessor Cores and Corporate Vice President, Advanced Micro Devices<ref>{{cite web |url=http://www.bloomberg.com/research/stocks/people/person.asp?personId=215060089&ticker=AMD&previousCapId=168864&previousTitle=ADVANCED%20MICRO%20DEVICES |title=Jim Keller: Executive Profile & Biography |work=[[Bloomberg Business]] |accessdate={{date|2015-05-14}} }}</ref>
| years_active =
| known_for = {{Plainlist|
* AMD K7
* AMD K8 (lead architect)
* Apple A4, A5
* x86-64 (coauthor)
* HyperTransport (coauthor)
}}
| notable_works =
}}

'''Jim Keller''' is a [[microprocessor]] [[engineer]] most well known for his work at [[AMD]] and [[Apple Inc.|Apple]]. He was the lead architect of [[AMD K8]] microarchitecture<ref name=anandtech>{{cite news |url=http://www.anandtech.com/show/6129/apple-a4a5-designer-k8-lead-architect-jim-keller-returns-to-amd |title=Apple A4/A5 Designer & K8 Lead Architect, Jim Keller, Returns to AMD |author=[[Anand Lal Shimpi]] |date=1 August 2012 |work=[[AnandTech]] }}</ref><ref name=xbitlabs>{{cite news |url=http://www.xbitlabs.com/news/cpu/display/20120801190422_Return_of_the_King_AMD_K7_and_K8_Designer_Jim_Keller_Back_at_AMD.html |title=Return of the King: AMD K7 and K8 Designer Jim Keller Back at AMD |author=Anton Shilov |date=1 August 2012 |work=X-bit Labs }}</ref><ref name=computing>{{cite news |url=http://www.computing.co.uk/ctg/news/2344223/amd-to-design-new-micro-architecture-for-2015-launch-under-chip-guru-jim-keller |title=AMD to design new micro-architecture for 2015 launch under chip guru Jim Keller |author=Graeme Burton |date=12 May 2014 |work=computing.co.uk }}</ref> (including the original [[Athlon 64]])<ref name=anandtech /><ref name=thenextweb>{{cite news |url=http://thenextweb.com/insider/2012/08/01/apples-cpu-architect-jim-keller-departs-to-head-up-chipmaker-amds-processor-group/ |title=Apple's CPU Architect Jim Keller Jumps To AMD |author=Robin Wauters |date=1 August 2012 |work=[[The Next Web]] }}</ref><ref name=cultofmac>{{cite news |url=http://www.cultofmac.com/182296/amd-hires-ax-series-architect-jim-keller-away-from-apple-to-report-to-mark-papermaster/ |title=AMD Hires Ax Series Architect Jim Keller Away From Apple To Report To Mark Papermaster |author=John Brownlee |date=1 August 2012 |work=Cult of Mac}}</ref> and was involved in designing the [[Athlon]] (K7)<ref name=computing /> and [[Apple A4]]/[[Apple A5|A5]] processors.<ref name=anandtech /><ref name=venturebeat>{{cite news |url=http://venturebeat.com/2012/08/01/apple-cpu-jim-keller-amd/ |title=Apple CPU lead Jim Keller heads back to AMD as chief architect |author=Devindra Hardawar |date=1 August 2012 |work=[[VentureBeat]] }}</ref><ref name=theverge>{{cite news |url=http://www.theverge.com/2012/8/1/3212406/jim-keller-joins-amd-vp-chief-architect |title=Former Apple chip designer Jim Keller joins AMD as chief architect and VP |author=Adi Robertson |date=1 August 2012 |publisher=Vox Media |work=[[The Verge]] }}</ref><ref name=allthingsd>{{cite news |url=http://allthingsd.com/20120801/amd-hires-apples-head-chip-designer/ |title=AMD Hires Apple's Head Chip Designer |author=Arik Hesseldahl |date=1 August 2012 |work=[[AllThingsD]] }}</ref> He was also the coauthor of the specifications for the [[x86-64]] instruction set<ref name=venturebeat /><ref name=itworld>{{cite news |url=http://www.itworld.com/article/2693371/is-amd-finally-ready-to-give-intel-a-real-fight.html |title=AMD roadmap: Is AMD finally ready to give Intel a real fight? |author=Andy Patrizio |date=16 May 2014 |work=ITworld}}</ref> and [[HyperTransport]] interconnect.<ref name=anandtech/><ref name=itworld /><ref name=semiaccurate>{{cite news |url=http://semiaccurate.com/2012/08/01/apples-cpu-architect-jim-keller-moves-back-to-amd/ |title=Apple's CPU architect Jim Keller moves back to AMD |author=Charlie Demerjian |date=1 August 2012 |work=[[SemiAccurate]] }}</ref> In 2012, he returned to AMD to work on the [[AMD K12]]<ref name=decryptedtech>{{cite news |url=http://www.decryptedtech.com/news/amd-brings-k7-k8-creator-jim-keller-back-into-the-fold |title=AMD Brings K7/K8 Creator, Jim Keller, Back Into the Fold |author=Sean Kalinich |date=27 June 2014 |work=decryptedtech.com }}</ref> and [[AMD Zen|Zen]] microarchitectures,<ref name=kitguru>{{cite news |url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/ |title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be |author=Anton Shilov |date=11 September 2014 |work=kitguru.net }}</ref><ref name=wccftech>{{cite news |url=http://wccftech.com/amd-confirms-development-of-high-performance-x86-core-with-completely-new-architecture/ |title=AMD Confirms Development of High-Performance x86 Core With Completely New Architecture |author=Hassan Mujtaba |date=5 May 2014 |work=WCCFtech }}</ref> particularly on the low-power/embedded versions.<ref name=cultofmac /><ref name=allthingsd />

== Career ==
Jim Keller was working at [[Digital Equipment Corporation|DEC]] until 1998, where he was involved in designing the [[Alpha 21164]] and [[Alpha 21264|21264]] processors.<ref name=anandtech /><ref name=xbitlabs /> In 1998 he moved to AMD, where he worked to launch the AMD [[Athlon]] (K7) processor and was the lead architect of the [[AMD K8]] microarchitecture,<ref name=9to5mac>{{cite news |url=http://9to5mac.com/2012/08/01/apple-cpu-guru-jim-keller-who-came-with-pa-semi-deal-departs-back-to-amd-to-lead-group-under-mark-papermaster/ |title=Apple CPU guru Jim Keller, who came with PA Semi deal, departs back to AMD to lead group under Mark Papermaster |author=Seth Weintraub |date=1 August 2012 |work=9to5Mac }}</ref> which also included designing the x86-64 instruction set and HyperTransport interconnect mainly used for [[multiprocessor]] communications.<ref name=anandtech />

In 1999, he left AMD to work at SiByte to design [[MIPS instruction set|MIPS]]-based processors for 1 Gbps network interfaces and other devices.<ref name=xbitlabs /><ref name=semiaccurate /> In November 2000, SiByte was acquired by [[Broadcom]],<ref>{{cite news |url=http://www.wsj.com/articles/SB973519053768422247 |title=Broadcom Agrees to Acquire SiByte for $2 Billion in Stock |author=Molly Williams |date=7 November 2000 |work=[[Wall Street Journal]] }}</ref> where he continued as chief architect<ref name=theverge /> until 2004.<ref name=anandtech />

In 2004 he moved to serve as the Vice President of Engineering at [[P.A. Semi]],<ref name=anandtech /><ref name=itworld /> a company specializing in low-power mobile processors.<ref name=xbitlabs /> P.A. Semi was acquired by Apple in 2008, and Keller followed,<ref name=9to5mac /><ref name=thenextweb /> becoming part of a team to design the Apple A4 and A5 [[system-on-a-chip]] mobile processors. These processors were used in several Apple products, including [[iPhone 4]], [[iPhone 4S|4S]], [[iPad]] and [[iPad 2]].

In August 2012, Jim Keller returned to AMD, where his primary task is to design a new generation [[microarchitecture]]<ref name=itworld /><ref name=wccftech /><ref name=computing /> called [[AMD Zen]].<ref name=kitguru /> After years disappointing processors from AMD, the Zen is hoped to restore AMD's position in the high-end [[x86]] processor market.<ref name=anandtech /><ref name=decryptedtech />

== References ==
{{Reflist}}

{{engineer-stub}}

[[Category:Living people]]
[[Category:Advanced Micro Devices people]]
[[Category:American engineers]]
[[Category:Computer hardware engineers]]
[[Category:Apple Inc. employees]]

Jim Keller

2015-05-13T21:23:11Z

Intgr: /* Career */ Another source

'''Jim Keller''' is a [[microprocessor]] [[engineer]] most well known for his work at [[AMD]] and [[Apple Inc.|Apple]]. He was the lead architect of [[AMD K8]] microarchitecture<ref name=anandtech>{{cite news |url=http://www.anandtech.com/show/6129/apple-a4a5-designer-k8-lead-architect-jim-keller-returns-to-amd |title=Apple A4/A5 Designer & K8 Lead Architect, Jim Keller, Returns to AMD |author=[[Anand Lal Shimpi]] |date=1 August 2012 |work=[[AnandTech]] }}</ref><ref name=xbitlabs>{{cite news |url=http://www.xbitlabs.com/news/cpu/display/20120801190422_Return_of_the_King_AMD_K7_and_K8_Designer_Jim_Keller_Back_at_AMD.html |title=Return of the King: AMD K7 and K8 Designer Jim Keller Back at AMD |author=Anton Shilov |date=1 August 2012 |work=X-bit Labs }}</ref><ref name=computing>{{cite news |url=http://www.computing.co.uk/ctg/news/2344223/amd-to-design-new-micro-architecture-for-2015-launch-under-chip-guru-jim-keller |title=AMD to design new micro-architecture for 2015 launch under chip guru Jim Keller |author=Graeme Burton |date=12 May 2014 |work=computing.co.uk }}</ref> (including the original [[Athlon 64]])<ref name=anandtech /><ref name=thenextweb>{{cite news |url=http://thenextweb.com/insider/2012/08/01/apples-cpu-architect-jim-keller-departs-to-head-up-chipmaker-amds-processor-group/ |title=Apple's CPU Architect Jim Keller Jumps To AMD |author=Robin Wauters |date=1 August 2012 |work=[[The Next Web]] }}</ref><ref name=cultofmac>{{cite news |url=http://www.cultofmac.com/182296/amd-hires-ax-series-architect-jim-keller-away-from-apple-to-report-to-mark-papermaster/ |title=AMD Hires Ax Series Architect Jim Keller Away From Apple To Report To Mark Papermaster |author=John Brownlee |date=1 August 2012 |work=Cult of Mac}}</ref> and was involved in designing the [[Athlon]] (K7)<ref name=computing /> and [[Apple A4]]/[[Apple A5|A5]] processors.<ref name=anandtech /><ref name=venturebeat>{{cite news |url=http://venturebeat.com/2012/08/01/apple-cpu-jim-keller-amd/ |title=Apple CPU lead Jim Keller heads back to AMD as chief architect |author=Devindra Hardawar |date=1 August 2012 |work=[[VentureBeat]] }}</ref><ref name=theverge>{{cite news |url=http://www.theverge.com/2012/8/1/3212406/jim-keller-joins-amd-vp-chief-architect |title=Former Apple chip designer Jim Keller joins AMD as chief architect and VP |author=Adi Robertson |date=1 August 2012 |publisher=Vox Media |work=[[The Verge]] }}</ref><ref name=allthingsd>{{cite news |url=http://allthingsd.com/20120801/amd-hires-apples-head-chip-designer/ |title=AMD Hires Apple's Head Chip Designer |author=Arik Hesseldahl |date=1 August 2012 |work=[[AllThingsD]] }}</ref> He was also the coauthor of the specifications for the [[x86-64]] instruction set<ref name=venturebeat /><ref name=itworld>{{cite news |url=http://www.itworld.com/article/2693371/is-amd-finally-ready-to-give-intel-a-real-fight.html |title=AMD roadmap: Is AMD finally ready to give Intel a real fight? |author=Andy Patrizio |date=16 May 2014 |work=ITworld}}</ref> and [[HyperTransport]] interconnect.<ref name=anandtech/><ref name=itworld /><ref name=semiaccurate>{{cite news |url=http://semiaccurate.com/2012/08/01/apples-cpu-architect-jim-keller-moves-back-to-amd/ |title=Apple's CPU architect Jim Keller moves back to AMD |author=Charlie Demerjian |date=1 August 2012 |work=[[SemiAccurate]] }}</ref> In 2012, he returned to AMD to work on the [[AMD K12]]<ref name=decryptedtech>{{cite news |url=http://www.decryptedtech.com/news/amd-brings-k7-k8-creator-jim-keller-back-into-the-fold |title=AMD Brings K7/K8 Creator, Jim Keller, Back Into the Fold |author=Sean Kalinich |date=27 June 2014 |work=decryptedtech.com }}</ref> and [[AMD Zen|Zen]] microarchitectures,<ref name=kitguru>{{cite news |url=http://www.kitguru.net/components/cpu/anton-shilov/amd-bulldozer-was-not-a-game-changer-but-next-gen-zen-x86-core-will-be/ |title=AMD: ‘Bulldozer’ was not a game-changer, but next-gen ‘Zen’ will be |author=Anton Shilov |date=11 September 2014 |work=kitguru.net }}</ref><ref name=wccftech>{{cite news |url=http://wccftech.com/amd-confirms-development-of-high-performance-x86-core-with-completely-new-architecture/ |title=AMD Confirms Development of High-Performance x86 Core With Completely New Architecture |author=Hassan Mujtaba |date=5 May 2014 |work=WCCFtech }}</ref> particularly on the low-power/embedded versions.<ref name=cultofmac /><ref name=allthingsd />

== Career ==
Jim Keller was working at [[Digital Equipment Corporation|DEC]] until 1998, where he was involved in designing the [[Alpha 21164]] and [[Alpha 21264|21264]] processors.<ref name=anandtech /><ref name=xbitlabs /> In 1998 he moved to AMD, where he worked to launch the AMD [[Athlon]] (K7) processor and was the lead architect of the [[AMD K8]] microarchitecture,<ref name=9to5mac>{{cite news |url=http://9to5mac.com/2012/08/01/apple-cpu-guru-jim-keller-who-came-with-pa-semi-deal-departs-back-to-amd-to-lead-group-under-mark-papermaster/ |title=Apple CPU guru Jim Keller, who came with PA Semi deal, departs back to AMD to lead group under Mark Papermaster |author=Seth Weintraub |date=1 August 2012 |work=9to5Mac }}</ref> which also included designing the x86-64 instruction set and HyperTransport interconnect mainly used for [[multiprocessor]] communications.<ref name=anandtech />

In 1999, he left AMD to work at SiByte to design [[MIPS instruction set|MIPS]]-based processors for 1 Gbps network interfaces and other devices.<ref name=xbitlabs /><ref name=semiaccurate /> In November 2000, SiByte was acquired by [[Broadcom]],<ref>{{cite news |url=http://www.wsj.com/articles/SB973519053768422247 |title=Broadcom Agrees to Acquire SiByte for $2 Billion in Stock |author=Molly Williams |date=7 November 2000 |work=[[Wall Street Journal]] }}</ref> where he continued as chief architect<ref name=theverge /> until 2004.<ref name=anandtech />

In 2004 he moved to serve as the Vice President of Engineering at [[P.A. Semi]],<ref name=anandtech /><ref name=itworld /> a company specializing in low-power mobile processors.<ref name=xbitlabs /> P.A. Semi was acquired by Apple in 2008, and Keller followed,<ref name=9to5mac /><ref name=thenextweb /> becoming part of a team to design the Apple A4 and A5 [[system-on-a-chip]] mobile processors. These processors were used in several Apple products, including [[iPhone 4]], [[iPhone 4S|4S]], [[iPad]] and [[iPad 2]].

In August 2012, Jim Keller returned to AMD, where his primary task is to design a new generation [[microarchitecture]]<ref name=itworld /><ref name=wccftech /><ref name=computing /> called [[AMD Zen]].<ref name=kitguru /> After years disappointing processors from AMD, the Zen is hoped to restore AMD's position in the high-end [[x86]] processor market.<ref name=anandtech /><ref name=decryptedtech />

== References ==
{{Reflist}}

{{engineer-stub}}

[[Category:Living people]]
[[Category:Advanced Micro Devices people]]
[[Category:American engineers]]
[[Category:Computer hardware engineers]]
[[Category:Apple Inc. employees]]