lkml.org 
[lkml]   [2008]   [Jun]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [patch 00/11] GRU Driver

* steiner@sgi.com <steiner@sgi.com> wrote:

> This series of patches adds a driver for the SGI UV GRU. The driver is
> still in development but it currently compiles for both x86_64 & IA64.
> All simple regression tests pass on IA64. Although features remain to
> be added, I'd like to start the process of getting the driver into the
> kernel. Additional kernel drivers will depend on services provide by
> the GRU driver.
>
> The GRU is a hardware resource located in the system chipset. The GRU
> contains memory that is mmaped into the user address space. This
> memory is used to communicate with the GRU to perform functions such
> as load/store, scatter/gather, bcopy, AMOs, etc. The GRU is directly
> accessed by user instructions using user virtual addresses. GRU
> instructions (ex., bcopy) use user virtual addresses for operands.

did i get it right that it's basically a fast, hardware based message
passing interface that allows two tasks to communicate via DMA and
interrupts, without holding up the CPU? If that is the case, wouldnt the
proper support model be a network driver, instead of these special
ioctls. (a network driver with no checksumming, with scatter-gather,
zero-copy and TSO support, etc.)

or a filesystem. Anything but special-purpose ioctls ...

Ingo


\
 
 \ /
  Last update: 2008-06-12 15:29    [W:0.166 / U:6.376 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site