Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

natural_t and 'large' systems

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

natural_t and 'large' systems

Subject: natural_t and 'large' systems
From: Graham J Lee <email@hidden>
Date: Tue, 25 Oct 2005 17:24:50 +0100

Hi,

I've been writing some code which uses host_statistics() to grab the VM usage - each of the fields in a "struct vm_statistics" is of type natural_t, which is a typedef unsigned int (eventually). So that's OK, because each of field represents a number of (usually 4kb) pages, so I've got about 16PB (2**32*4k) of RAM before I overflow that. But some other kernel fields, such as memory_size are also natural_t. How do those behave when you go past 4GB on a system? The kernel on this G5 system is single-architecture ppc, so the answer isn't that the fields are wider on ppc64 AFAICT.

Thanks,

Graham.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden



Prev by Date:
mount(..) example?

Next by Date:
Re: mount(..) example?

Previous by thread:
Re: mount(..) example?

Next by thread:
Before dlfcn.h?

Index(es):

Date
Thread