search for: 16mb

This patch adds a test that tries to create a domain with only 16MB of RAM. It verifies that the domain is created and that the console works. Right now this test fails for me: the domain just dies immediately with no indication of why, or with any useful console data. Should we put a sanity check on xm''s create and mem-set commands that prevent the use...

...an-Samba 3 file > server. It is running the 2.4 kernel on a ProLiant DL380 G3 server > (Full Specs below). For a windows client, we are running Windows 2003 > server on the exact same hardware. They are both running at Gigabit > speed. > > What we have found is that on files 16MB and smaller we can get better > performance Windows client to Linux Server through SMB than we can get > Windows to local disk. (Both servers have the same disk subsystem) > We get around 120,000KB/sec throughput. But after 16MB, the > performance drops until it flatlines from 32MB on...

Quite a while back we set the goal of running R in 16Mb RAM, as people (I think Kjetil) had teaching labs that small. Since then R has grown, and we has recently started to optimize R for speed rather than size. I recently tested R-devel on my ancient Win98 notebook with 64Mb RAM -- it ran but startup was rather slow on what I think is a 233MHz pr...

Hi all, As I understand it, LLVM's JIT memory manager works by allocating a 16Mb block of memory and generating native code into it. Once that block is exhausted no more functions can be JIT compiled. I'm trying to figure out ways to work around this limitation. One idea I had was to use that 16Mb block as a scratch area for generating code. Once a method has been compi...

...h a zero offset. LDS, LSDLK, STS, and STSCUL instructions access shared memory with a zero offset. LD, ST, RED, ATOM, and CCTL.D instructions access the generic thread address space, which is layered on top of the channel's virtual address space. In the generic thread address space, there are 16MB windows into local and shared memory; everything not in a Local or Shared address window accesses global virtual memory. The local window offset within the generic thread address space is determined by the SetShaderLocalMemoryWindow class method (offset 0x77c in classes *97 and *c0). The shared w...

Hi people, I am building a cheap remote rsync backup server using a software raid 5 array of 4 500GB disks. What I have available on the market is: 1. HITACHI GST Deskstar T7K500 500GB 7200rpm 16MB cache Serial ATA II-300 2. SEAGATE Barracuda 7200.10 with NCQ 500GB 7200rpm 16MB cache Serial ATA II-300 3. Western Digital 500GB SATAII RAID EDITION Caviar SE16 7200rpm 8.9ms 16MB cache I am tempted to use the Western Digital Raid Edition as it has 5 years of warranty. However I found out that t...

...isk (www.asterisk.org) box will be built with the following specs and I wanted to know if CENTOS has a built process/config/parameter/special distro to target the AMD Opteron Dual Core plataform: 2 amd opteron 265 dual core 1.8 Ghz 2mb l2 cache 2x1024 ocz c2-6400 dual channel gold GX XTC 2 Seagate 16mb cache 300 GB barracuda 7200 drives another 2 Seagate 500 GB 16mb cache baracuda ata 7200 drives lite on dual layer lightscribe 16x dvd+rw/rw x48 drive 4 port Sata Raid controller raid - 10 2 gigabit E broadcom 10/100/100 GBE lan controller Tyan Thunder K8WE (S2895) motherboard or Tyan motherboards...

http://bugs.freedesktop.org/show_bug.cgi?id=13796 Summary: tnt2 16Mb agp, corrupted image Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org...

Hi: I compiled and run tftp-hpa-0.33 on my Solaris 2.7 but it does not support file size larger than 16MB. The tftpd time out when 16MB of file is transfered. Can anyone offer a hint for how to enable tftp-hpa to support large file size ? Very appreciate Geefu Wang

...STS, and STSCUL instructions access shared memory with a zero > offset. > > LD, ST, RED, ATOM, and CCTL.D instructions access the generic thread address > space, which is layered on top of the channel's virtual address space. > > In the generic thread address space, there are 16MB windows into local and > shared memory; everything not in a Local or Shared address window accesses > global virtual memory. > > The local window offset within the generic thread address space is determined > by the SetShaderLocalMemoryWindow class method (offset 0x77c in classes *97...

Hi all. I'm working on a LLVM based compiler for the D programming language by Walter Bright. D allows static arrays up to 16MB in size. I'm initializing global static arrays with a constant initializer. But D requires that (per default) static arrays are initialized with the default initializer for the element type. For float this happens to be NaN, so I cannot use a 'zeroinitializer'. This is problematic as D...

On Thu, Aug 20, 2009 at 6:42 AM, Gary Benson<gbenson at redhat.com> wrote: > Hi all, > > As I understand it, LLVM's JIT memory manager works by allocating a > 16Mb block of memory and generating native code into it.  Once that > block is exhausted no more functions can be JIT compiled.  I'm trying > to figure out ways to work around this limitation. Nope, I actually fixed this bug in r76902. :) Now it allocates memory in 64K slabs, and when it ru...

...d volume. This is very attractive feature that could benefit tiered volume to let it handle larger files without hitting the "out of (hot)space problem". I decided to set test configuration on GlusterFS 3.12.3 when tiered volume has 2TB cold and 1GB hot segments. Shard size is set to be 16MB. For testing 100GB files are used. It seems writes and reads are going well. But I hit problem trying to delete files from the volume. One of GlusterFS processes hit segmentation fault. The problem is reproducible each time. It was submitted to Red Hat Bugzilla bug list and has ID 1521119. You can...

Thanks for Remko for his help to solve the fractional cylinder problem. But there is the second problem, the boot disk failure (see below << [B]) ... command line: initrd=disk.img harddisk c=2 h=256 s=63 BOOT_IMAGE=memdisk Disk is hard disk, 16128K CHS=2/256/63 <<<< [A] ... Loading boot sector... booting... SYSLINUX 2.04 welcome! boot: 1 [single dot]

Hi, on IA64 flushing the whole TLB is very expensive: this is a cpu tlb flush and clearing 16MB of memory (virtual tlb). However, flushing an address range is rather cheap. Flushing an address range on every processors is also cheap (no IPI). Unfortunatly Xen common code flushes the whole TLB after unmapping grant reference. Currently, this is not done on IA64 because domain_dirty_cpumas...

I have got an old pentium back. It is an Intel 66Mhz processor, 16MB RAM and a 2 gigabyte harddrive. Could it be used as a dedicated samba server and what Linux disto would work well? I was thinking of Debian 3 or Slackware. Can samba act as a 2000 PDC?

On Mon, 20 Aug 2007, Tomas Lindquist Olsen wrote: > I'm working on a LLVM based compiler for the D programming language by > Walter Bright. Nifty. > D allows static arrays up to 16MB in size. I'm initializing global > static arrays with a constant initializer. But D requires that (per > default) static arrays are initialized with the default initializer > for the element type. For float this happens to be NaN, so I cannot > use a 'zeroinitializer'. Wow,...

.... > > Thanks for any additional info Yes, 32-bit arm mach-o object files run into size limitations because of how relocations are encoded. Some information is encoded in bits of the instruction and some is encoded in bit fields in relocations. If you try to make an arm .o file larger than 16MB, you start hitting various limits. Not all the limits are enforced by the MC layer, resulting in bad .o files. You could try not having debug info, or moving the __DWARF sections to the end of the file, and you might last longer. But the only sure fix is to keep all .o file under 16MB. The fi...

...ry attractive > feature that could benefit tiered volume to let it handle larger files > without hitting the "out of (hot)space problem". > I decided to set test configuration on GlusterFS 3.12.3 when tiered volume > has 2TB cold and 1GB hot segments. Shard size is set to be 16MB. > For testing 100GB files are used. It seems writes and reads are going well. > But I hit problem trying to delete files from the volume. One of GlusterFS > processes hit segmentation fault. > The problem is reproducible each time. It was submitted to Red Hat Bugzilla > bug list an...

>I tried the commands that you have presented and I running into >problems. I tried the ideology that you presented with both 32 and 16mb >configurations with no luck. Is there something that I'm missing? > >The win98se boot disk boots (just downloaded it from bootdisk today) so >I used that as a based for the boot file. > >Item 8c works fine (1.44 image) but 8b fails. > >dd if=/dev/zero of=boot32mb.bin b...