Displaying 6 results from an estimated 6 matches for "directmap1g".
2012 Jul 26
2
kernel parameters for improving gluster writes on millions of small writes (long)
...VmallocUsed: 1227732 kB
VmallocChunk: 33888774404 kB
HardwareCorrupted: 0 kB
AnonHugePages: 376832 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
DirectMap4k: 201088 kB
DirectMap2M: 15509504 kB
DirectMap1G: 521142272 kB
and the server's meminfo is:
$ cat /proc/meminfo
MemTotal: 32861400 kB
MemFree: 1232172 kB
Buffers: 29116 kB
Cached: 30017272 kB
SwapCached: 44 kB
Active: 18840852 kB
Inactive: 11772428 kB
Active(anon): 492928 kB
In...
2016 Mar 23
7
/proc/meminfo
...VmallocTotal: 34359738367 kB
VmallocUsed: 354796 kB
VmallocChunk: 34359380456 kAnonHugePages: 15630336 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
DirectMap4k: 81684 kB
DirectMap2M: 3031040 kB
DirectMap1G: 32505856 kB
2016 Mar 23
0
Re: /proc/meminfo
...354796 kB
> VmallocChunk: 34359380456 kAnonHugePages: 15630336 kB
> HugePages_Total: 0
> HugePages_Free: 0
> HugePages_Rsvd: 0
> HugePages_Surp: 0
> Hugepagesize: 2048 kB
> DirectMap4k: 81684 kB
> DirectMap2M: 3031040 kB
> DirectMap1G: 32505856 kB
>
> _______________________________________________
> libvirt-users mailing list
> libvirt-users@redhat.com
> https://www.redhat.com/mailman/listinfo/libvirt-users
2016 Apr 26
0
Re: /proc/meminfo
...354796 kB
> VmallocChunk: 34359380456 kAnonHugePages: 15630336 kB
> HugePages_Total: 0
> HugePages_Free: 0
> HugePages_Rsvd: 0
> HugePages_Surp: 0
> Hugepagesize: 2048 kB
> DirectMap4k: 81684 kB
> DirectMap2M: 3031040 kB
> DirectMap1G: 32505856 kB
>
> _______________________________________________
> libvirt-users mailing list
> libvirt-users@redhat.com
> https://www.redhat.com/mailman/listinfo/libvirt-users
>
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)