search for: 164m

Displaying 9 results from an estimated 9 matches for "164m".

Did you mean: 164
2007 Apr 02
1
Out of memory in make_file
...MP Mon Nov 6 12:35:31 EST 2006 x86_64 GNU/Linux It is Debian testing/unstable. We can reproduce this problem on the packaged debian version (2.6.7) and the current CVS checkout (2007-04-02, around 11am Pacific time.) There is another current rsync process running on the server using 171m VIRT, 164m RES, and 728 SHR. It is the sender and receiver. I was wondering if anyone could shed some light on this? Is it still an issue of "break it up into smaller hunks?" Any insight is appreciated. I can provide any debugging information you need on the system, tuning, kernel build informa...
2005 Aug 08
7
Loadbalancing and failover using TC and Iptables
Hi all iam trying to deploy loadbalance and failover My setup description --Fedora Core 4 --Linux 2.6.12.3 #1 SMP Mon Jul 25 22:37:34 IST 2005 i686 i686 i386 GNU/Linux --tc utility, iproute2-ss050314 --ip utility, iproute2-ss050314 --iptables v1.3.0 And i had deployed Following configuration #table main with priority 50, the highest one ip rule add prio 50 table main #table 201 ip rule add
2012 Jul 13
1
[Bug 9041] New: Feature request: Better handling of btrfs based sources
...oot root 62060544 Jul 13 17:12 rsync/old/ChangeMe.mp3 262 -rw-r----- 1 root root 46897152 Jul 13 17:12 rsync/old/NoTouching.mp3 # Disk space usage is increased accordingly: > df -hT /test/*/ Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/vg-test_btrfs btrfs 1.0G 164M 219M 43% /test/btrfs /dev/mapper/vg-test_rsync btrfs 1.0G 209M 174M 55% /test/rsync Note that I am not asking for rsync to duplicate the subvolume or snapshot functionality. Just recognize that the same file exists in multiple locations kind of like a hard link but not. It seems to me the...
2013 Oct 19
6
[Bug 866] New: Missing newline with --list-rules
...ed in the OUTPUT chain and somehow migrated. Chain INPUT (policy ACCEPT 273K packets, 85M bytes) pkts bytes target prot opt in out source destination 35912 47M all -- !lo+ any anywhere anywhere UNKNOWN match `quota2' 139K 164M all -- !lo+ any anywhere anywhere UNKNOWN match `quota2' This causes iptables to exit abruptly in the first line of the filter table. It would be better to display the entire table with an error after each line that can't be completely interpreted...
2009 Oct 15
8
sub-optimal ZFS performance
Hello, ZFS is behaving strange on a OSOL laptop, your thoughts are welcome. I am running OSOL on my laptop, currently b124 and i found that the performance of ZFS is not optimal in all situations. If i check the how much space the package cache for pkg(1) uses, it takes a bit longer on this host than on comparable machine to which i transferred all the data. user at host:/var/pkg$ time
2017 Jun 16
7
[RFC] virtio-mem: paravirtualized memory
...numa info numa 2 nodes node 0 cpus: 0 1 node 0 size: 10240 MB node 1 cpus: 2 3 node 1 size: 5120 MB 5. Resize a virtio-mem device: Try to unplug all memory. Setting reg0 to 0G (removing 8G from NUMA node 0) will not work. The guest will not be able to unplug all memory. In my example, 164M cannot be unplugged (out of memory). --> (qemu) virtio-mem reg0 0 virtio-mem reg0 0 --> (qemu) info numa info numa 2 nodes node 0 cpus: 0 1 node 0 size: 2212 MB node 1 cpus: 2 3 node 1 size: 5120 MB --> (qemu) info virtio-mem reg0 info virtio-mem reg0 Status: ready Request st...
2017 Jun 16
7
[RFC] virtio-mem: paravirtualized memory
...numa info numa 2 nodes node 0 cpus: 0 1 node 0 size: 10240 MB node 1 cpus: 2 3 node 1 size: 5120 MB 5. Resize a virtio-mem device: Try to unplug all memory. Setting reg0 to 0G (removing 8G from NUMA node 0) will not work. The guest will not be able to unplug all memory. In my example, 164M cannot be unplugged (out of memory). --> (qemu) virtio-mem reg0 0 virtio-mem reg0 0 --> (qemu) info numa info numa 2 nodes node 0 cpus: 0 1 node 0 size: 2212 MB node 1 cpus: 2 3 node 1 size: 5120 MB --> (qemu) info virtio-mem reg0 info virtio-mem reg0 Status: ready Request st...
2017 Jul 28
0
[RFC] virtio-mem: paravirtualized memory
...pus: 0 1 > node 0 size: 10240 MB > node 1 cpus: 2 3 > node 1 size: 5120 MB > > 5. Resize a virtio-mem device: Try to unplug all memory. > Setting reg0 to 0G (removing 8G from NUMA node 0) will not work. The > guest will not be able to unplug all memory. In my example, 164M > cannot be unplugged (out of memory). > > --> (qemu) virtio-mem reg0 0 > virtio-mem reg0 0 > --> (qemu) info numa > info numa > 2 nodes > node 0 cpus: 0 1 > node 0 size: 2212 MB > node 1 cpus: 2 3 > node 1 size: 5120 MB > --> (qemu) info virt...
2015 Sep 05
5
RFC: Reducing Instr PGO size overhead
On Fri, Sep 4, 2015 at 9:11 PM, Sean Silva <chisophugis at gmail.com> wrote: > > > On Fri, Sep 4, 2015 at 5:42 PM, Xinliang David Li <davidxl at google.com> > wrote: >> >> On Fri, Sep 4, 2015 at 5:21 PM, Sean Silva <chisophugis at gmail.com> wrote: >> > >> > >> > On Fri, Sep 4, 2015 at 3:57 PM, Xinliang David Li <davidxl at