linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Yosry Ahmed <yosryahmed@google.com>
To: "Jonas Schäfer" <jonas@wielicki.name>
Cc: linux-mm@kvack.org
Subject: Re: About swapaccount=
Date: Thu, 2 Mar 2023 11:12:43 -0800	[thread overview]
Message-ID: <CAJD7tka+B2AJKYxEWTpEU7CSUPUdA+gePtJE9rn6urAgOSEVsQ@mail.gmail.com> (raw)
In-Reply-To: <2593755.Xrv9ptJ69j@sinistra.local>

On Thu, Mar 2, 2023 at 11:01 AM Jonas Schäfer <jonas@wielicki.name> wrote:
>
> Hi there,
>
> By coincidence, I found this log message in my kernel logs:
>
> Mär 02 17:23:19 sinistra kernel: The swapaccount= commandline option is
> deprecated. Please report your usecase to linux-mm@kvack.org if you depend on
> this functionality.
>
> My usecase does depend on this in the following way:
>
> I use LXC extensively to isolate workloads from one another. Kind of like
> docker, but with full operating systems inside.
>
> Before I found out about swapaccount, I often ran into the issue that one
> misbehaving workload from one of those containers would bring the entire
> machine to a halt because it occupied lots of swap, and thus triggered
> significant slowdown.
>
> With swapaccount, I limit swap to about 10% of the RAM assigned to the
> containers. This allows them to swap out unused stuff, but invokes the OOM
> killer before any significant slowdown happens.
>
> The alternative would be to turn off swap for the system entirely, but it is
> running fairly efficiently thanks to swapping stuff out.
>
> I'd be interested to hear about alternatives.
>
> Thanks for hearing me, anyway.

If I understand correctly you were setting swapaccount=1, right?

IIRC, swapaccount= was deprecated in the sense that it is always on
now (i.e you cannot set swapaccount=0).

>
> kind regards,
> Jonas Schäfer


  reply	other threads:[~2023-03-02 19:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-02 19:01 Jonas Schäfer
2023-03-02 19:12 ` Yosry Ahmed [this message]
2023-03-03  9:46   ` Jonas Schäfer

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=CAJD7tka+B2AJKYxEWTpEU7CSUPUdA+gePtJE9rn6urAgOSEVsQ@mail.gmail.com \
    --to=yosryahmed@google.com \
    --cc=jonas@wielicki.name \
    --cc=linux-mm@kvack.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