From: David Nicol <phuqytol@davidnicol.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: OO swap interface
Date: Thu, 11 Oct 2001 06:30:47 -0500 [thread overview]
Message-ID: <3BC582E7.C2C4FCC7@davidnicol.com> (raw)
In-Reply-To: <1355693A51C0D211B55A00105ACCFE6402B9E013@ATL_MS1> <20011010095536.C10443@turbolinux.com>
Here's an idea that has been mulling under my mullet for
the last few weeks:
the nbd can be used for a swap device, but since swap has no reason
to inform the drive about what parts of it are free, it is not possible
to have a central nbd server overcommit for multiple client swapping
nodes.
Therefore I wonder how tricky it would be to create a swap interface
that is ignorant of disk geometries. the swap interface language
would accept requests for space, with unique handles, and would
return the swapped-out data on representation of the handle. Like
a virtual memory hat check.
--
David Nicol 816.235.1187
1,3,7-trimethylxanthine
next prev parent reply other threads:[~2001-10-11 11:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 15:23 dynamic swap prioritizing Venkatesh Ramamurthy
2001-10-10 15:55 ` 'adilger@turbolabs.com'
2001-10-10 17:14 ` Richard B. Johnson
2001-10-11 11:30 ` David Nicol [this message]
2001-10-12 0:45 ` Xuan Baldauf
2001-10-12 3:32 ` 'adilger@turbolabs.com'
2001-10-12 15:22 ` Xuan Baldauf
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=3BC582E7.C2C4FCC7@davidnicol.com \
--to=phuqytol@davidnicol.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