[<<] [<] Page 1 of 1 [>] [>>] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: [linuxce-devel] Re: Microwindows/Nano-X version 0.87pre1 rele
From: Alan Cox ####@####.#### Date: 2 Dec 1999 17:12:35 -0000 Message-Id: <E11tZgE-00015z-00@the-village.bc.nu> > a 24 bit malloc (I know, huge) in the case that everything is running > on Linux for speed. One trick, used by Xlib, is to split any Copy/Read/Area > large rectangle into smaller rectangles and make smaller requests for > each. Perhaps we should go that route. How big should nanogui think > a large buffer is? Whatever is sent by the server handshake? For some stuff - embedded boxes, linux 8086 then yes using smaller chunks might be a good idea. On Linux8086 512 bytes is a lot of data, on embedded boxes 32K might be a 'lot' Alan | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[<<] [<] Page 1 of 1 [>] [>>] |