Displaying 4 results from an estimated 4 matches for "8388604".
Did you mean:
8388608
2016 Oct 11
5
Asterisk 13.11.2, 13.11.1, 13.10.0 and certified-13.8-cert3 : freeze on 'sip reload'
..._listener_start()
94 threads listed.
sip5*CLI> core show sysinfo
System Statistics
-----------------
System Uptime: 0 hours
Total RAM: 8009136 KiB
Free RAM: 6969004 KiB
Buffer RAM: 162556 KiB
Total Swap Space: 8388604 KiB
Free Swap Space: 8388604 KiB
Number of Processes: 266
After some time nothing is possible any more and I need to restart Asterisk.
Is this an known issue ? I don't understand how the latest versions of
Asterisk are workable for anyone ?!
Kind regards.
------...
2013 Feb 12
10
[PATCH] Btrfs-progs: check out if the swap device
Currently, the following commands succeed.
# cat /proc/swaps
Filename Type Size Used Priority
/dev/sda3 partition 8388604 0 -1
/dev/sdc8 partition 9765884 0 -2
# mkfs.btrfs /dev/sdc8
WARNING! - Btrfs v0.20-rc1-165-g82ac345 IS EXPERIMENTAL
WARNING! - see http://btrfs.wiki.kernel.org before using
fs created label (null) on /dev/sdc8
nodesize 4096 leafsize...
2011 Nov 29
4
[RFC] virtio: use mandatory barriers for remote processor vdevs
Virtio is using memory barriers to control the ordering of
references to the vrings on SMP systems. When the guest is compiled
with SMP support, virtio is only using SMP barriers in order to
avoid incurring the overhead involved with mandatory barriers.
Lately, though, virtio is being increasingly used with inter-processor
communication scenarios too, which involve running two (separate)
2011 Nov 29
4
[RFC] virtio: use mandatory barriers for remote processor vdevs
Virtio is using memory barriers to control the ordering of
references to the vrings on SMP systems. When the guest is compiled
with SMP support, virtio is only using SMP barriers in order to
avoid incurring the overhead involved with mandatory barriers.
Lately, though, virtio is being increasingly used with inter-processor
communication scenarios too, which involve running two (separate)