lkml.org 
[lkml]   [1998]   [Feb]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: GGI, EGCS/PGCC, Kernel source
Date
> protocol, it gets thousands of calls per second. The accelerator of most
> cards is a different beast though. It usually has a limited queue depth
> (8, 16, 32), where a command can take up 1-5 queue entries. So certain

Yes but you dont have to go back to user space each time you fill the hardware
queue.

> possibly millions of accelerated operations per second. Smallish
> accelerated operations finish within 10-100 cycles, this is why almost no
> GX card has IRQ-driven acceleration, they have an engine status/depth
> register that can be polled. If you let users access the framebuffer as
> well then 'delayed syncing' (a technique in XFree86 XAA that has almost
> doubled acceleration performance ...) can not be done safely.

Now that depends on two things

1. If you only allow one user to have the frame buffer a time and keep
context on switches.

2. If you dont pull MMU stunts to fault/block other tasks touching
the memory during such events. Also note most operations take so
few cycles a non scheduling spin is no big deal (SMP needs the mmu
stunt always alas).

Alan


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

\
 
 \ /
  Last update: 2005-03-22 13:41    [W:0.051 / U:0.152 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site