Question for keeping pages in the RAM?

08/02/2004 - 11:49 por Frank | Informe spam

Hi,folks

I am a beginner, I wanna allocate a number of pages of space for some
operations, and I need keeping those pages stay in the RAM at all for
operating faster.Is there WIN32 API can do it? Any reply is appreciated :p

Thanx very very ... much!

Frank F.Han

+--+
| winsays@:-)hotmail:-).com |
+--+

Siga el debate

12 respuestas

Tengo una respuesta

Preguntas similare

Mostrar todos los temas similares

Leer las respuestas

#11 Kirk Ferdmann

11/02/2004 - 07:52 | Informe spam

"Alexander Grigoriev" wrote in message
news:%

Only a few related problems has been corrected. Such as CopyFile(Ex) now
seems to open a big file in FILE_FLAG_NO_BUFFERING mode.

Sparse index array support is for working with sparse files. I am talking
about non-sparse files, such as big AVI or WAV.

Let's first establish understaing of what you mean by the uncontrollable
growth. AFAIK cache size (amount of entries) is fixed after it's calculated
at boot time. So I assume you meant the overhead of control structures
allocated from nonpaged pool.

Now back to index arrays: no it's not for sparse files only. Index arrays
are sequential in the sense that entry 0 points to a VACB for the fisrt 256K
(or NULL if it's not cached), entry 1 points to the second 256K etc. So if
there is a 128M file and just the last 256K are in the cache, on the system
without sparse index arrays the index array would contain 512 entries.
Sparse index arrays are allocated in multilevel fashion as 128-entry chunks.
So there will be 256 indices.

-Kirk

Responder a este mensaje

#12 Frank

12/02/2004 - 13:20 | Informe spam

Hi, Alexander

I saw your thread below, and I observed WAV you mentioned. You know, I am a
beginner, so I have question wanna consult you about WAV format file. You
know, the WAV's header structure defined by microsoft supports 32bit length
of PCM Wave data storage, Could you tell me how to treat it when it grow up
to greater than 32bit length(4Gb) of PCM data? very thanx :p

"Alexander Grigoriev"
:#

Only a few related problems has been corrected. Such as CopyFile(Ex) now
seems to open a big file in FILE_FLAG_NO_BUFFERING mode.

Sparse index array support is for working with sparse files. I am talking
about non-sparse files, such as big AVI or WAV.

"Kirk Ferdmann" wrote in message
news:
> "Alexander Grigoriev" wrote in message
> news:
> > When working with huge files, Windows cache tends to grow

uncontrollably

> at
> > the cost of application memory. It's definitely not suited for such a
> case.
> > And there is no way to limit such cache bloat (there was in Windows

9x).