2005
DOI: 10.1002/cpe.961
|View full text |Cite
|
Sign up to set email alerts
|

Transparent access to Grid resources for user software

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2006
2006
2017
2017

Publication Types

Select...
4
2

Relationship

0
6

Authors

Journals

citations
Cited by 8 publications
(3 citation statements)
references
References 6 publications
0
3
0
Order By: Relevance
“…Running such codes in a grid environment requires a level of virtualization that emulates the machine for which the codes once had been written, including processor architecture, operating system, and file system layouts. Different approaches have been proposed to achieve this goal [5,17].…”
Section: Types Of Grid Programs and Their Programming Environmentsmentioning
confidence: 99%
“…Running such codes in a grid environment requires a level of virtualization that emulates the machine for which the codes once had been written, including processor architecture, operating system, and file system layouts. Different approaches have been proposed to achieve this goal [5,17].…”
Section: Types Of Grid Programs and Their Programming Environmentsmentioning
confidence: 99%
“…Front-ends may employ Filesystem in USEr space (FUSE) and/or Parrot [18,28]. Both allow the datastore to leverage iRODS and/or filesystems.…”
Section: Posix-like Filesystem Accessmentioning
confidence: 99%
“…For now, we implement the Grid Engine as a stub. We will need to add a mechanism into the Grid Engine to access HPC technology transparently in a way reported by Klous, et al 10) . Also, our implemented system is command-line based only.…”
Section: Fig 10mentioning
confidence: 99%