RE: Re: Referencing a row in a two dimensional array

Thanks for the superb writeup!

At 01:00 AM 3/4/03 -0800, Roger Corman wrote:
>For now, the best way to get good performance in reading large blocks of
>data is to allocate a foreign block of sufficient size and read into
>that via foreign calls.
>
>A better solution would be for me to implement pinned arrays i.e. blocks
>of memory which do not move during GC.

You'd still need efficient READ-SEQUENCE code, yes?

>You could probably
>implement a memcpy() type function which would copy from a foreign block
>to a lisp byte array, or vice-versa, wrapped in an atomic block, using
>assembler. I may write one of these and I will forward it if so.
>

That's what I was thinking of with my psuedocode as the inner-inner
loop of an efficient READ-SEQUENCE.

Also, I don't know if this makes sense, but it might help to increase
the buffer size,  or make it adjustable?  I think it is 2048 or 4096 bytes?


>I very much understand the need for a fast READ-SEQUENCE that is
>optimized for bytes. It doesn't exist yet (unless Pavel or someone has
>written it already). I will try to prioritize working on this, as it
>would be extremely useful to me as well.


To do numeric processing, code often wants READ-SEQUENCE functionality
for 32 bit (int and single-float) and 64 bit (double float) values as well.
So if it's not much extra effort, I'd recommend looking at that as well.


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Get 128 Bit SSL Encryption!
http://us.click.yahoo.com/LIgTpC/vN2EAA/xGHJAA/SyjtlB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
[email protected]

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/