From: Arjan van de Ven <arjanv@redhat.com>
To: christophe.varoqui@free.fr
Cc: dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [Q] don't allow tmpfs to page out
Date: Thu, 15 Jul 2004 10:00:17 +0200 [thread overview]
Message-ID: <20040715080017.GB20889@devserv.devel.redhat.com> (raw)
In-Reply-To: <1089878317.40f6392d7e365@imp5-q.free.fr>
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
On Thu, Jul 15, 2004 at 09:58:37AM +0200, christophe.varoqui@free.fr wrote:
> >
> > 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) ?
somewhat, as long as ALL requirements are there, including all libraries ;)
> If so, is it possible and/or correct for the daemon to do a private ramfs mount
> for this purpose ?
sure; namespaces can do a LOT
>
> 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 ?
mlockall does not guarantee that syscalls you do don't cause memory
allocations, nor does the ramfs approach.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-07-15 8:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-15 7:58 [Q] don't allow tmpfs to page out christophe.varoqui
2004-07-15 8:00 ` Arjan van de Ven [this message]
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=20040715080017.GB20889@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=christophe.varoqui@free.fr \
--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