Mike Lankamp

Name: dblp XML data dump
Creator: Schloss Dagstuhl - Leibniz Center for Informatics
Published: 1993
License: https://creativecommons.org/publicdomain/zero/1.0/
Keywords: dblp, XML, computer science, scholarly publications, metadata

◀ ▶ joint publications with Michiel W. van Tol

> Home > Persons > Mike Lankamp

Publications

2013
[j4]
- view
  authority control:
- export record
  dblp key:
  - journals/mam/PossLYFTUJ13
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/journals/mam/PossLYFTUJ13
Raphael Poss, Mike Lankamp, Qiang Yang, Jian Fu, Michiel W. van Tol, Muhammad Irfan Uddin, Chris R. Jesshope:
Apple-CORE: Harnessing general-purpose many-cores with hardware concurrency management. Microprocess. Microsystems 37(8-C): 1090-1101 (2013)
2012
[c5]
- view
  authority control:
- export record
  dblp key:
  - conf/dsd/PossLYFTJ12
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/conf/dsd/PossLYFTJ12
Raphael Poss, Mike Lankamp, Qiang Yang, Jian Fu, Michiel W. van Tol, Chris R. Jesshope:
Apple-CORE: Microgrids of SVP Cores - Flexible, General-Purpose, Fine-Grained Hardware Concurrency Management. DSD 2012: 501-508
2009
[j2]
- view
  authority control:
- export record
  dblp key:
  - journals/jsa/TolJLP09
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/journals/jsa/TolJLP09
Michiel W. van Tol, Chris R. Jesshope, Mike Lankamp, Simon Polstra:
An implementation of the SANE Virtual Processor using POSIX threads. J. Syst. Archit. 55(3): 162-169 (2009)
2008
[c1]
- view
  authority control:
- export record
  dblp key:
  - conf/samos/BernardBGJLTZ08
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/conf/samos/BernardBGJLTZ08
Thomas A. M. Bernard, Kostas Bousias, Liang Guang, Chris R. Jesshope, Mike Lankamp, Michiel W. van Tol, Li Zhang:
A general model of concurrency and its implementation as many-core dynamic RISC processors. ICSAMOS 2008: 1-9

manage site settings

To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.