search for: 174mb

...irectory, which was using about 600mb hd space. For example, advapi32.dll.so was 1155k, while advapi.c was only 8518 bytes and advapi.o was 149k. I tried bzipping advapi32.dll.so, and its size went down to 279k. Then I tried making the wine-20050930 directory into one big bzipped tar, and it became 174mb. Is it just me that finds this to be strange? 850mb is a lot of hd space, and I don't remember that building older versions of wine used that much hd space. And the files were very compressible. Regards, Alexander Toresson PS. Please CC me, I'm not subscribed.

Hi, netvirt-src-20080310.tar.bz2 appears to the last beta release. Is this synced against Build 81 ? Also when is the next beta expected ? Regards, Moinak.

...: nouveau at lists.freedesktop.org Created attachment 118102 --> https://bugs.freedesktop.org/attachment.cgi?id=118102&action=edit Shadow Warrior on Nouveau Screenshots comparing intel and nouveau attached. Apitrace: http://people.freedesktop.org/~mslusarz/ShadowWarrior.bin.x86.trace.xz (174MB) This is on mesa-git (3c6c4d4f298ec81fe57992790a68aaab2e573519) with the patch from bug#91890. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://...

...bottleneck is in mmio. Your nvme vendor extension patches reduces greatly the number of MMIO writes. So I'd like to push it upstream. I port these 2 patches to newer kernel and qemu. I use ram disk as backend to compare performance. qemu-nvme: 29MB/s qemu-nvme+google-ext: 100MB/s virtio-blk: 174MB/s virtio-scsi: 118MB/s I'll show you qemu-vhost-nvme+google-ext number later. root at guest:~# cat test.job [global] bs=4k ioengine=libaio iodepth=64 direct=1 runtime=120 time_based rw=randread norandommap group_reporting gtod_reduce=1 numjobs=2 [job1] filename=/dev/nvme0n1 #filename=/dev/v...

...bottleneck is in mmio. Your nvme vendor extension patches reduces greatly the number of MMIO writes. So I'd like to push it upstream. I port these 2 patches to newer kernel and qemu. I use ram disk as backend to compare performance. qemu-nvme: 29MB/s qemu-nvme+google-ext: 100MB/s virtio-blk: 174MB/s virtio-scsi: 118MB/s I'll show you qemu-vhost-nvme+google-ext number later. root at guest:~# cat test.job [global] bs=4k ioengine=libaio iodepth=64 direct=1 runtime=120 time_based rw=randread norandommap group_reporting gtod_reduce=1 numjobs=2 [job1] filename=/dev/nvme0n1 #filename=/dev/v...