Maximum size that can be allocated

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








0















Can I allocate more memory than VmallocTotal given in /proc/meminfo ?










share|improve this question




























    0















    Can I allocate more memory than VmallocTotal given in /proc/meminfo ?










    share|improve this question
























      0












      0








      0








      Can I allocate more memory than VmallocTotal given in /proc/meminfo ?










      share|improve this question














      Can I allocate more memory than VmallocTotal given in /proc/meminfo ?







      linux memory






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Mar 13 at 9:32









      camscams

      1




      1




















          1 Answer
          1






          active

          oldest

          votes


















          1














          vmalloc() is an internal kernel function. It is not available to user programs. It has no effect on allocations of memory for user programs. VmallocTotal limits the allocations of kernel code which calls vmalloc() (and VmallocTotal does not change, either automatically or manually).



          Maximum size of memory that can be "allocated" by user programs depends on overcommit settings. I write "allocated" in scare quotes, because "overcommit" somewhat contradicts the idea of "allocating memory". One explanation is here, you can search on the keywords it uses for other explanations: https://serverfault.com/questions/606185/how-does-vm-overcommit-memory-work



          As the kernel doc puts it, system calls like mmap() or the old sbrk() do not allocate memory by default. They return "address space". Real memory will be mapped on-demand if/when it is written to. Memory is mapped in terms of pages (usually 4096 bytes).






          share|improve this answer

























            Your Answer








            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "106"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













            draft saved

            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f506042%2fmaximum-size-that-can-be-allocated%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            1














            vmalloc() is an internal kernel function. It is not available to user programs. It has no effect on allocations of memory for user programs. VmallocTotal limits the allocations of kernel code which calls vmalloc() (and VmallocTotal does not change, either automatically or manually).



            Maximum size of memory that can be "allocated" by user programs depends on overcommit settings. I write "allocated" in scare quotes, because "overcommit" somewhat contradicts the idea of "allocating memory". One explanation is here, you can search on the keywords it uses for other explanations: https://serverfault.com/questions/606185/how-does-vm-overcommit-memory-work



            As the kernel doc puts it, system calls like mmap() or the old sbrk() do not allocate memory by default. They return "address space". Real memory will be mapped on-demand if/when it is written to. Memory is mapped in terms of pages (usually 4096 bytes).






            share|improve this answer





























              1














              vmalloc() is an internal kernel function. It is not available to user programs. It has no effect on allocations of memory for user programs. VmallocTotal limits the allocations of kernel code which calls vmalloc() (and VmallocTotal does not change, either automatically or manually).



              Maximum size of memory that can be "allocated" by user programs depends on overcommit settings. I write "allocated" in scare quotes, because "overcommit" somewhat contradicts the idea of "allocating memory". One explanation is here, you can search on the keywords it uses for other explanations: https://serverfault.com/questions/606185/how-does-vm-overcommit-memory-work



              As the kernel doc puts it, system calls like mmap() or the old sbrk() do not allocate memory by default. They return "address space". Real memory will be mapped on-demand if/when it is written to. Memory is mapped in terms of pages (usually 4096 bytes).






              share|improve this answer



























                1












                1








                1







                vmalloc() is an internal kernel function. It is not available to user programs. It has no effect on allocations of memory for user programs. VmallocTotal limits the allocations of kernel code which calls vmalloc() (and VmallocTotal does not change, either automatically or manually).



                Maximum size of memory that can be "allocated" by user programs depends on overcommit settings. I write "allocated" in scare quotes, because "overcommit" somewhat contradicts the idea of "allocating memory". One explanation is here, you can search on the keywords it uses for other explanations: https://serverfault.com/questions/606185/how-does-vm-overcommit-memory-work



                As the kernel doc puts it, system calls like mmap() or the old sbrk() do not allocate memory by default. They return "address space". Real memory will be mapped on-demand if/when it is written to. Memory is mapped in terms of pages (usually 4096 bytes).






                share|improve this answer















                vmalloc() is an internal kernel function. It is not available to user programs. It has no effect on allocations of memory for user programs. VmallocTotal limits the allocations of kernel code which calls vmalloc() (and VmallocTotal does not change, either automatically or manually).



                Maximum size of memory that can be "allocated" by user programs depends on overcommit settings. I write "allocated" in scare quotes, because "overcommit" somewhat contradicts the idea of "allocating memory". One explanation is here, you can search on the keywords it uses for other explanations: https://serverfault.com/questions/606185/how-does-vm-overcommit-memory-work



                As the kernel doc puts it, system calls like mmap() or the old sbrk() do not allocate memory by default. They return "address space". Real memory will be mapped on-demand if/when it is written to. Memory is mapped in terms of pages (usually 4096 bytes).







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Mar 13 at 11:55

























                answered Mar 13 at 11:11









                sourcejedisourcejedi

                25.9k445113




                25.9k445113



























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Unix & Linux Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f506042%2fmaximum-size-that-can-be-allocated%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown






                    Popular posts from this blog

                    How to check contact read email or not when send email to Individual?

                    Displaying single band from multi-band raster using QGIS

                    How many registers does an x86_64 CPU actually have?