From: Jes Sorensen <jes@wildopensource.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] limiting dentries on Linux
Date: Wed, 12 Mar 2003 18:24:11 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709806066@msgid-missing> (raw)
>>>>> "Mario" = Mario Smarduch <cms063@email.mot.com> writes:
Mario> I apologize in advance for floating a general Linux question on
Mario> IA-64 group.
Mario> What can be used to limit space allocated for dentries? For
Mario> example catting non-existing files eats up 30M of memory.
Actually that just goes into the buffer/page caches and will be
released again once someone tries to allocate the memory back using
the appropriate kmalloc() flags, ie. anything but GFP_ATOMIC.
Mario> What group is more relevant to these types of questions.
Possibly linux-kernel, however I doubt you will find much support for
limiting the buffer/page caches.
Cheers,
Jes
next reply other threads:[~2003-03-12 18:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 18:24 Jes Sorensen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-05 17:49 [Linux-ia64] limiting dentries on Linux Mario Smarduch
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=marc-linux-ia64-105590709806066@msgid-missing \
--to=jes@wildopensource.com \
--cc=linux-ia64@vger.kernel.org \
/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