From: Raymond Jennings <shentino@gmail.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: Silly question about dethrottling
Date: Mon, 5 Dec 2016 01:15:39 -0800 [thread overview]
Message-ID: <CAGDaZ_oXcWVVAugGetVV2qBR9kJ-=VKKn8A0ErT-0vXOAZ6NTg@mail.gmail.com> (raw)
In-Reply-To: <20161205070519.GA30765@dhcp22.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]
On Sun, Dec 4, 2016 at 11:05 PM, Michal Hocko <mhocko@kernel.org> wrote:
> On Sun 04-12-16 13:56:54, Raymond Jennings wrote:
> > I have an application that is generating HUGE amounts of dirty data.
> > Multiple GiB worth, and I'd like to allow it to fill at least half of my
> > RAM.
>
> Could you be more specific why and what kind of problem you are trying
> to solve?
>
> > I already have /proc/sys/vm/dirty_ratio pegged at 80 and the background
> one
> > pegged at 50. RAM is 32GiB.
>
> There is also dirty_bytes alternative which is an absolute numer.
>
How does this compare to setting dirty_ratio to a high percentage?
>
> > it appears to be butting heads with clean memory. How do I tell my
> system
> > to prefer using RAM to soak up writes instead of caching?
>
> I am not sure I understand. Could you be more specific about what is the
> actual problem? Is it possible that your dirty data is already being
> flushed and that is wy you see a clean cache?
>
What I'm wanting is for my writing process not to get throttled, even when
the dirty memory it starts creating starts hogging memory the system would
rather use for cache.
[-- Attachment #2: Type: text/html, Size: 1760 bytes --]
next prev parent reply other threads:[~2016-12-05 9:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-04 21:56 Raymond Jennings
2016-12-05 7:05 ` Michal Hocko
2016-12-05 9:15 ` Raymond Jennings [this message]
2016-12-05 9:25 ` Michal Hocko
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='CAGDaZ_oXcWVVAugGetVV2qBR9kJ-=VKKn8A0ErT-0vXOAZ6NTg@mail.gmail.com' \
--to=shentino@gmail.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@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