search for: 4gbyte

...se positive to me. So const uint64_t size = count * vm->subblock_size; is it unreasonable for count to be 4K with subblock_size being 1M? > > > > It ripples through UAPI which is an ABI change, but it's not too late to > > make it, and it will allow supporting >4Gbyte blocks while might > > become necessary down the road. > > > > This might break cloud-hypervisor, who's already implementing this > protocol upstream (ccing Hui). > https://github.com/cloud-hypervisor/cloud-hypervisor/blob/master/vm-virtio/src/mem.rs > > (blocks...

...se positive to me. So const uint64_t size = count * vm->subblock_size; is it unreasonable for count to be 4K with subblock_size being 1M? > > > > It ripples through UAPI which is an ABI change, but it's not too late to > > make it, and it will allow supporting >4Gbyte blocks while might > > become necessary down the road. > > > > This might break cloud-hypervisor, who's already implementing this > protocol upstream (ccing Hui). > https://github.com/cloud-hypervisor/cloud-hypervisor/blob/master/vm-virtio/src/mem.rs > > (blocks...

...ance troubles I've been having. I'm doing some tests with gluster 3.2.0, and I can't understand some of the behavior I'm getting with gluster. The test is using a volume with 12 stripped bricks (each brick is an HD), with no replication, via RDMA. I'm doing random readings of 4GByte files with the FIO tool. Gluster reading speed is of 150-160MByte/s and 110-120MByte/s per client if I connect with two clients. However, on the same machine, I have a similar lustre setup with a constant 400MByte/s throughput, for the same tests, with the same amount of disks going through the...

If subblock size is large (e.g. 1G) 32 bit math involving it can overflow. Rather than try to catch all instances of that, let's tweak block size to 64 bit. It ripples through UAPI which is an ABI change, but it's not too late to make it, and it will allow supporting >4Gbyte blocks while might become necessary down the road. Fixes: 5f1f79bbc9e26 ("virtio-mem: Paravirtualized memory hotplug") Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/virtio/virtio_mem.c | 14 +++++++------- include/uapi/linux/virtio_mem.h | 4 ++-- 2 files...

If subblock size is large (e.g. 1G) 32 bit math involving it can overflow. Rather than try to catch all instances of that, let's tweak block size to 64 bit. It ripples through UAPI which is an ABI change, but it's not too late to make it, and it will allow supporting >4Gbyte blocks while might become necessary down the road. Fixes: 5f1f79bbc9e26 ("virtio-mem: Paravirtualized memory hotplug") Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/virtio/virtio_mem.c | 14 +++++++------- include/uapi/linux/virtio_mem.h | 4 ++-- 2 files...

...ecause i’m running it on a linux cluster with R version R 2.1.0. which operates on a 32 bit processor. But I could not find a solution for this problem. The cluster is a really fast one and should be able to cope with these large amounts of data the systems configuration are Speed: 3.4 GHz, memory 4GByte. Is there a way to change the settings or processor under R? I want to run the function Random Forest on my large data set it should be able to cope with that amount. Perhaps someone has tried this before in R or is Fortram a better choice? I added my R script down below. Best regards, Iris Kol...

...there tech support on this. >My new server motherboard is socket 939 and supports DDR 400. It was a bargin off ebay but appears to work fine. Would I be better off getting a socket AM2 that supports DDR2 or will that make much difference in performance? The 939 motherboard supports a max of 4Gbyte DDR too. >I also purchased a Seagate SATA 500Gbyte drive. The 300G PATA drive is just under half full. I imagine mostly email. Mailboxes for the most part have 50M cap but there alot of them and still adding more. Is there anyway to copy the OS installed on the PATA to a larger and faster SA...

...gt;> I fail to see where we could actually trigger an overflow. The reported >> warning looked like a false positive to me. >> >>> >>> It ripples through UAPI which is an ABI change, but it's not too late to >>> make it, and it will allow supporting >4Gbyte blocks while might >>> become necessary down the road. >>> >> >> This might break cloud-hypervisor, who's already implementing this >> protocol upstream (ccing Hui). >> https://github.com/cloud-hypervisor/cloud-hypervisor/blob/master/vm-virtio/src/mem.r...

...4MB. So "count * vm->subblock_size" can currently not exceed the Linux memory block size (in practice, it is max 128MB). > >>> >>> It ripples through UAPI which is an ABI change, but it's not too late to >>> make it, and it will allow supporting >4Gbyte blocks while might >>> become necessary down the road. >>> >> >> This might break cloud-hypervisor, who's already implementing this >> protocol upstream (ccing Hui). >> https://github.com/cloud-hypervisor/cloud-hypervisor/blob/master/vm-virtio/src/mem.r...

...10BA1701B409CD21CD19 in Hexeditor (Winhex12.25 is very good) and call it boot.com ) to that Dos partition. After testing, that boot.com works which means that reboot to Dos lasts 5 seconds, I enlarged this partition with Partition Magic to <2GByte FAT16 because I need a large ramdisk and I have 4Gbyte ram. Then I make with the Hexeditor an image of the whole <2GB partition including the first 63 sectors with mbr and call it dos.img . I copied this image to another harddisk. Then I set up Syslinux 3.09 with memdisk on a >=2GB hardisk as described in syslinux.doc and memdisk.doc and copied...

...at, > let's tweak block size to 64 bit. I fail to see where we could actually trigger an overflow. The reported warning looked like a false positive to me. > > It ripples through UAPI which is an ABI change, but it's not too late to > make it, and it will allow supporting >4Gbyte blocks while might > become necessary down the road. > This might break cloud-hypervisor, who's already implementing this protocol upstream (ccing Hui). https://github.com/cloud-hypervisor/cloud-hypervisor/blob/master/vm-virtio/src/mem.rs (blocks in the gigabyte range were never the or...

...sion R 2.1.0. which operates on a 32 bit > processor. > > But I could not find a solution for this problem. The cluster is a > > really fast one and should be able to cope with these large > amounts of > > data the systems configuration are Speed: 3.4 GHz, memory > 4GByte. Is > > there a way to change the settings or processor under R? I > want to run > > the function Random Forest on my large data set it should > be able to > > cope with that amount. Perhaps someone has tried this > before in R or > > is Fortram a better choi...

...sion R 2.1.0. which operates on a 32 bit > processor. > > But I could not find a solution for this problem. The cluster is a > > really fast one and should be able to cope with these large > amounts of > > data the systems configuration are Speed: 3.4 GHz, memory > 4GByte. Is > > there a way to change the settings or processor under R? I > want to run > > the function Random Forest on my large data set it should > be able to > > cope with that amount. Perhaps someone has tried this > before in R or > > is Fortram a better choi...

...> >> My new server motherboard is socket 939 and supports DDR 400. It was > a bargin off ebay but appears to work fine. Would I be better off > getting a socket AM2 that supports DDR2 or will that make much > difference in performance? The 939 motherboard supports a max of > 4Gbyte DDR too. > >> I also purchased a Seagate SATA 500Gbyte drive. The 300G PATA drive > is just under half full. I imagine mostly email. Mailboxes for the > most part have 50M cap but there alot of them and still adding more. > Is there anyway to copy the OS installed on the PATA t...