{"id":3688,"date":"2019-07-27T00:01:51","date_gmt":"2019-07-27T07:01:51","guid":{"rendered":"https:\/\/c-for-dummies.com\/blog\/?p=3688"},"modified":"2019-07-20T11:20:24","modified_gmt":"2019-07-20T18:20:24","slug":"take-it-to-the-limit","status":"publish","type":"post","link":"https:\/\/c-for-dummies.com\/blog\/?p=3688","title":{"rendered":"Take it to the Limit"},"content":{"rendered":"

It’s been a while since I’ve been seriously concerned about wasting system resources. Back when I programmed a TRS-80 Model III with only 48K of RAM, keeping an eye on memory usage was vital. Today, not so much. In fact, if you desire to write code that consumes a lot of memory, CPU time, or other system resources, more power to you!
\n
\nThe only time I’m concerned about system resources is when processing humongous graphics files. Even then, the size is only a few megabytes, which shouldn’t be an issue for a modern system. And if the malloc()<\/em> or realloc()<\/em> function can’t find more memory, NULL<\/code> is returned and the program reacts to the situation accordingly.<\/p>\n

When you really want to know the limits, however, you can use the getrlimit()<\/em> function, defined in the sys\/resource.h<\/code> header file. Here’s the man page format:<\/p>\n

int getrlimit(int resource, struct rlimit *rlp);<\/code><\/p>\n

The first argument is one of several defined constants, which are listed on the man page. Here are two choices:<\/p>\n

RLIMIT_DATA<\/code>, which directs the function to return the maximum number of bytes the process (your program) can access.<\/p>\n

RLIMIT_FSIZE<\/code>, which directs the function to return the largest file size (in bytes) that can be created.<\/p>\n

Other options are available return other maximum values, depending on which resources you’re trying to pinch.<\/p>\n

The second argument is a pointer to an rlimit<\/em> structure. This structure has two members:<\/p>\n

rlim_t rlim_cur<\/em>, which represents the current limit.<\/p>\n

rlim_t rlim_max<\/em>, which represents the maximum limit.<\/p>\n

The rlim_t<\/em> typecast is either a long unsigned<\/em> or double-long unsigned<\/em> integer value.<\/p>\n

The getrlimit()<\/em> function returns zero upon success, -1 otherwise. The global errno<\/em> variable<\/a> is set accordingly and can be examined for further details.<\/p>\n

In this sample code, the limit on how much data the program can access is output:<\/p>\n

\r\n#include <stdio.h>\r\n#include <sys\/resource.h>\r\n\r\nint main()\r\n{\r\n    struct rlimit limit;\r\n    int r;\r\n\r\n    r = getrlimit( RLIMIT_DATA, &limit );\r\n    if( r==-1 )\r\n    {\r\n        fprintf(stderr,\"Some kinda error\\n\");\r\n        return(1);\r\n    }\r\n\r\n    printf(\"Current soft limit on data is %llu\\n\",\r\n            limit.rlim_cur\r\n          );\r\n    printf(\"Current hard limit on data is %llu\\n\",\r\n            limit.rlim_max\r\n          );\r\n    \r\n    return(0);\r\n}<\/pre>\n
Line 6 declares the rlimit<\/em> structure variable limit<\/code> as a regular variable, not a pointer. For some reason, accessing the members proved difficult when I declared it as a pointer.<\/p>\n
The getrlimit()<\/em> function is called at Line 9. The two structure members limit.rlim_cur<\/code> and limit.rlim_max<\/code> are output from Lines 16 onward. (Your compiler may balk at the %llu<\/code> placeholder. If so, use %lu<\/code> instead.)<\/p>\n
Here’s the output on my machine:<\/p>\n
Current soft limit on data is 9223372036854775807
\nCurrent hard limit on data is 9223372036854775807<\/code><\/p>\n
That’s one huge number, effectively 9 quintillion bytes, which is surprising given this machine has 16GB of RAM installed. This result leads me to believe the function erred, but -1 wasn’t returned so go figure.<\/p>\n
Curious, I test-ran the code on Ubuntu Linux and the output was twice as much, or around 18 quintillion bytes. So I’m not feeling good about the results, but at least the function is available, should you ever consider having your code access and use such humongous quantities of system resources.<\/p>\n","protected":false},"excerpt":{"rendered":"
The getrlimit()<\/em> function discloses details on programming resources. Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-3688","post","type-post","status-publish","format-standard","hentry","category-main"],"_links":{"self":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/3688","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3688"}],"version-history":[{"count":3,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/3688\/revisions"}],"predecessor-version":[{"id":3694,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/3688\/revisions\/3694"}],"wp:attachment":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3688"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3688"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3688"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}