Custom Query (204 matches)
Results (22 - 24 of 204)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#32 | fixed | mmap: Add support for MAP_SHARED | ||
Description |
Currently, mmap lacks support for MAP_SHARED. This flag is basically ignored and an attempt to use it in another process will cause an error message from WPSTK that this memory doesn't belong to it (this usually is followed by a crash due to access to invalid memory). MAP_SHARED is often used in Linux software together with MAP_ANONYMOUS (and with fd = -1) to create shared memory for inter-process communication. We need to support that scenario. |
|||
#33 | fixed | OpenSSL team considers dropping OS/2 code from 1.0.2+ | ||
Description |
Hi, One of my friends subscribed to the OpenSSL mailing list for users forwarded me an e-mail proposing dropping of OS/2 support code from their codebase (apparently related to their planned cleanup of source code). I'm afraid that they would ask for someone taking care for the OS/2 port in order to stop this unfavourable action (someone who knows the code and can resolve incompatibilities, etc.)... Thanks Tomas |
|||
#34 | fixed | git: Support USE_CURL_MULTI | ||
Description |
After fixing #19 I found out that our git is very slow when cloning over HTTPS with USE_CURL_MULTI defined. This define is automatically enabled for all recent versions of CURL and causes git to use several HTTP streams for talking to the server (which in theory should improve the overall performance). While working on #19 I disabled USE_CURL_MULTI to simplify debugging HTTP transfers. However, now, when I enabled it back, I noticed that the clone speed significantly decreased. For instance, cloning https://github.com/psmedley/gcc with *no* USE_CURL_MULTI gives us around 200 KiB/s second. When USE_CURL_MULTI is enabled, the speed drops to 25 KiB/s (i.e. almost 10 times slower). This is not acceptable. I'm not 100% sure if it's a git or curl problem. At least, when I try to use CURL.EXE to directly download a ZIP from github it is as fast as it should be (around 200 KiB/s) but I'm not sure if CURL.EXE uses multiple streams internally or not (and there are no command line options to control this). Note that this applies to git 2.0.0 (built from the dmik branch ATM). |