From: Michal Hocko <mhocko@kernel.org>
To: Muni Sekhar <munisekharrms@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kmalloc size limit?
Date: Mon, 22 Aug 2016 14:12:33 +0200 [thread overview]
Message-ID: <20160822121233.GD14916@dhcp22.suse.cz> (raw)
In-Reply-To: <CAHhAz+hipwEp4_-0L5nMWSMWpd5szCdjk2UJTj_6grHu0X45Og@mail.gmail.com>
On Sat 20-08-16 00:09:53, Muni Sekhar wrote:
> Hi All,
>
> I would like to know what is the maximum size limit for kmalloc() API
> to return a valid memory?
KMALLOC_MAX_CACHE_SIZE
> Does the size limit varies based on the flags argument?
no but different flags can greatly influence how succesful such an
allocation can be.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2016-08-22 12:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 18:39 Muni Sekhar
2016-08-22 12:12 ` Michal Hocko [this message]
2016-08-22 13:04 ` Muni Sekhar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160822121233.GD14916@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=munisekharrms@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®