Re: Low level C interaction (Specifically OpenGL)
- From: "Brad Might" <mightb@xxxxxxxxx>
- Date: 29 Sep 2005 13:21:08 -0700
I was referring to structure handling. This was a while ago so I don't
remember the details but I think it was kevent structures. When I
hammered my app hard with network requests, the bottleneck seemed to be
in the foreign structure accesses.
Looking at the code now, i see a static buffer allocated with malloc
that uses sys:sap-ref-32 to pull the values out of memory and into lisp
before/after my kevent calls.
The speed difference was an order (or several) of magnitude, otherwise
I would have left the cleaner code in place if it was only a minimal
hit.
.
- References:
- Low level C interaction (Specifically OpenGL)
- From: bradb
- Re: Low level C interaction (Specifically OpenGL)
- From: Brad Might
- Re: Low level C interaction (Specifically OpenGL)
- From: bradb
- Re: Low level C interaction (Specifically OpenGL)
- From: Brad Might
- Re: Low level C interaction (Specifically OpenGL)
- From: bradb
- Low level C interaction (Specifically OpenGL)
- Prev by Date: Where to look for the API documentation?
- Next by Date: Re: C++ and lisp and Games
- Previous by thread: Re: Low level C interaction (Specifically OpenGL)
- Next by thread: Re: Low level C interaction (Specifically OpenGL)
- Index(es):