search for: 168mb

Hi I have a doubt regarding Mini-OS and Xen. If it is true that Xen reserves in the virtual address space the top 64MB on 32bit systems and 168MB in PAE systems, doesn''t it exist with a Mini-OS kernel which has only 32MB in size i.e. going by its default config file? Obviously I''m missing something. Regards, Bhaskar. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http:...

...uff out... I''ve just installed Instant Rails on a USB key, thinking it would be a great way of showing off Rails in general, giving a progress update to customers, trying out ideas, and generally all the other benefits that come from having a completely portable environment. However, the 168Mb of files that make up my Instant Rails (with extra gems) is consuming 750Mb of space on my USB key. The reason is simple enough; the USB is formatted as FAT32, and having lots of small files stored on a FAT32 partition is a great way to burn your disc space quickly. Unfortunately, I don''...

...lls are possible. I'm using the asterisk that comes with Fedora; before that, I used a self-compiled version on Centos. The hardware is still the same. Asterisk shows the following message when trying to make a call: WARNING[92530]: pbx.c:4644 increase_call_count: Available system memory (~168MB) is below the configured low watermark (1024MB) I was thinking that asterisk is leaking memory because the only way to get asterisk to work again was by restarting the server. Since this is very annoying and the Fedora bug report remains ignored, I finally started to investigate. The relevant s...

In a mdb table, I have a text field with values of 1, 2, .... When I use rodbc to read it into R, it becomes numeric. Is it a bug or something? Thanks.

Simon Burton <simon at arrowtheory.com> writes: >> There are several possibilities here: either add1 is assigned a NULL >> pointer, or LLVM was unable to use the JIT and generates bytecode >> instead of native code, or invalid native code was generated >> (unlikely). > > Well, it's not NULL: > > (gdb) print add1 > $1 = (int (*)(int)) 0x83e43b8 >

...are using > but I would try adding LLVMJIT.o to your link command the same way you > do with LLVMInterpreter.o Actually if I _remove_ those other library link arguments and just left the ones provided by "llvm-config --libs" it works fine (yay!). Except it's a huge executable: 168Mb. And the linker warns about some symbols: /usr/bin/ld: `.gnu.linkonce.t._ZNK4llvm14TargetLowering12getValueTypeEPKNS_4TypeE' referenced in section `.rodata' of /home//users//simonb//lib/LLVMPowerPC.o: defined in discarded section `.gnu.linkonce.t._ZNK4llvm14TargetLowering12getValueTypeEPKNS...

...ith Fedora; before that, I used a self-compiled version on > > Centos. The hardware is still the same. Asterisk shows the following > > message when trying to make a call: > > > > > > WARNING[92530]: pbx.c:4644 increase_call_count: Available system memory > > (~168MB) is below the configured low watermark (1024MB) > > > > > > I was thinking that asterisk is leaking memory because the only way to get > > asterisk to work again was by restarting the server. Since this is very > > annoying and the Fedora bug report remains ignored, I...

On Fri, 14 Apr 2006 03:25:39 +0200 Oscar Fuentes <oscarfv at telefonica.net> wrote: ... > Simon, > > With a fresh CVS checkout, I've tried your test case on Windows/VC++ > and it works ok. Too bad that I have not access to a Linux machine > right now. I'll like to see what's wrong with your test case. > > What you get from running the test case under gdb

...page at the top of memory (minus hole for hypervisor) and patched the ELF header at boot. Thoughts welcome, Rusty. Name: Move vsyscall page out of fixmap, above stack Author: Gerd Hoffmann <kraxel@suse.de> Hypervisors want to use memory at the top of the address space (eg. 64MB for Xen, or 168MB for Xen w/ PAE). Creating this hole means moving the vsyscall page away from 0xffffe000. If we create this hole statically with a config option, we give up, say, 256MB of lowmem for the case where a hypervisor-capable kernel is actually running on native hardware. If we create this hole dynamica...

...page at the top of memory (minus hole for hypervisor) and patched the ELF header at boot. Thoughts welcome, Rusty. Name: Move vsyscall page out of fixmap, above stack Author: Gerd Hoffmann <kraxel@suse.de> Hypervisors want to use memory at the top of the address space (eg. 64MB for Xen, or 168MB for Xen w/ PAE). Creating this hole means moving the vsyscall page away from 0xffffe000. If we create this hole statically with a config option, we give up, say, 256MB of lowmem for the case where a hypervisor-capable kernel is actually running on native hardware. If we create this hole dynamica...