search for: 108mb

Hello, I sent the following message to the Debian folks. They don't think that the Debian packaging could be responsible for the issue described there. > Well, I'm not completely convinced that we will have very useful input > for you. I don't really see any reason for this to be caused by the > Debian packaging. To check this, why not compile samba from sources,

...quot;. Started domain p-virtvip9 Linux version 2.6.18-1.2798.fc6xen (brewbuilder@hs20-bc2-4.build.redhat.com) (gcc version 4.1.1 20061011 (Red Hat 4.1.1-30)) #1 SMP Mon Oct 16 15:11:19 EDT 2006 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000006c00000 (usable) 0MB HIGHMEM available. 108MB LOWMEM available. Using x86 segment limits to approximate NX protection ACPI in unprivileged domain disabled Built 1 zonelists. Total pages: 27648 Kernel command line: root=/dev/sda1 ro Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing...

Hi, I'm running samba server on board and client is windows 7. I did below steps for performance tests. + format /dev/sda1 with ext4 + mount the drive in server as mentioned in [media] path of /etc/samba/smb.conf + created a root password $ smbpasswd -a root + 1Gb ethernet interface from board. + map the driver in windows + did a 4gb robocopy + read got 13MBps and write got 105MBps

...EventNotifier *e) Could you help to explain what "match_data" and "data" mean? I use a real NVMe device as backend. -drive file=/dev/nvme0n1,format=raw,if=none,id=D22 \ -device nvme,drive=D22,serial=1234 Here is the test results: local NVMe: 860MB/s qemu-nvme: 108MB/s qemu-nvme+google-ext: 140MB/s qemu-nvme-google-ext+eventfd: 190MB/s root at wheezy:~# cat test.job [global] bs=4k ioengine=libaio iodepth=64 direct=1 runtime=60 time_based norandommap group_reporting gtod_reduce=1 numjobs=8 [job1] filename=/dev/nvme0n1 rw=read

On 20/11/2015 09:11, Ming Lin wrote: > On Thu, 2015-11-19 at 11:37 +0100, Paolo Bonzini wrote: >> >> On 18/11/2015 06:47, Ming Lin wrote: >>> @@ -726,7 +798,11 @@ static void nvme_process_db(NvmeCtrl *n, hwaddr addr, int val) >>> } >>> >>> start_sqs = nvme_cq_full(cq) ? 1 : 0; >>> - cq->head = new_head;

On 20/11/2015 09:11, Ming Lin wrote: > On Thu, 2015-11-19 at 11:37 +0100, Paolo Bonzini wrote: >> >> On 18/11/2015 06:47, Ming Lin wrote: >>> @@ -726,7 +798,11 @@ static void nvme_process_db(NvmeCtrl *n, hwaddr addr, int val) >>> } >>> >>> start_sqs = nvme_cq_full(cq) ? 1 : 0; >>> - cq->head = new_head;

Hi, I am aware that it is impossible to netboot ISO files through pxelinux/memdisk and that there are multiple reasons for not even attempting it (like the operating system which will try to access a physical optical drive through its own drivers anyway, BIOS issues etc.). When people ask questions regarding ISO support in pxelinux/memdisk, they're mostly told to convert the ISO into a

Hi all, I''m putting together a OpenSolaris ZFS-based system and need help picking hardware. I''m thinking about using this 26-disk case: [FYI: 2-disk RAID1 for the OS & 4*(4+2) RAIDZ2 for SAN] http://rackmountpro.com/productpage.php?prodid=2418 Regarding the mobo, cpus, and memory - I searched goggle and the ZFS site and all I came up with so far is that, for a

Hi all, I''m putting together a OpenSolaris ZFS-based system and need help picking hardware. I''m thinking about using this 26-disk case: [FYI: 2-disk RAID1 for the OS & 4*(4+2) RAIDZ2 for SAN] http://rackmountpro.com/productpage.php?prodid=2418 Regarding the mobo, cpus, and memory - I searched goggle and the ZFS site and all I came up with so far is that, for a