mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: christophe.varoqui@free.fr
To: arjanv@redhat.com, dm-devel@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Q] don't allow tmpfs to page out
Date: Thu, 15 Jul 2004 09:58:37 +0200	[thread overview]
Message-ID: <1089878317.40f6392d7e365@imp5-q.free.fr> (raw)

> 
> just do 
> mount -t ramfs none /mnt/point
> 
Would that be a suitable solution to store callout binaries for daemons like
multipathd that need to work in case of system-disk outage (/bin & swap on SAN
for example) ?

If so, is it possible and/or correct for the daemon to do a private ramfs mount
for this purpose ?

And while I'm at throwing all the questions I have on my mind :
* how can I disable on-demand loading for the daemon ?
* does mlockall() provides all the necessary garanties ?
* what explains the "offset-by-4" between VSZ and RSS I see when running
mlockall'ed daemon ?

Thanks for the educational work :)

regards,
cvaroqui

             reply	other threads:[~2004-07-15  7:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-15  7:58 christophe.varoqui [this message]
2004-07-15  8:00 ` Arjan van de Ven
2004-07-15 10:00   ` christophe.varoqui
2004-07-15 12:31   ` namespaces (was Re: [Q] don't allow tmpfs to page out) Paul Jakma
2004-07-15 12:31     ` Arjan van de Ven
2004-07-15 12:50       ` Paul Jakma
2004-07-15 22:35       ` [dm-devel] " christophe varoqui
2004-07-15 23:00         ` Chris Wedgwood
2004-07-15 17:19     ` Andries Brouwer
2004-07-15 21:52       ` Rutger Nijlunsing
  -- strict thread matches above, loose matches on Subject: below --
2004-07-14 14:54 [Q] don't allow tmpfs to page out Michael Buesch
2004-07-14 15:42 ` William Stearns
2004-07-14 15:51   ` Michael Buesch
2004-07-14 16:01     ` Arjan van de Ven
2004-07-14 16:03       ` Michael Buesch
2004-07-14 16:04         ` Arjan van de Ven
2004-07-14 16:07           ` Michael Buesch
2004-07-14 16:08             ` Arjan van de Ven
2004-07-14 16:11               ` Michael Buesch

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=1089878317.40f6392d7e365@imp5-q.free.fr \
    --to=christophe.varoqui@free.fr \
    --cc=arjanv@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-kernel@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
all inboxes | Powered by JetHome®