From: Harry Kalogirou <harkal@gmx.net>
To: Javier Sedano <jsedano@dit.upm.es>
Cc: Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: Swap support
Date: 22 Apr 2002 19:29:43 +0300 [thread overview]
Message-ID: <1019492981.479.128.camel@cool> (raw)
In-Reply-To: <3CC4132C.3807ECC@dit.upm.es>
[-- Attachment #1: Type: text/plain, Size: 2054 bytes --]
Την Δευ, 22-04-2002 στις 16:42, ο/η Javier Sedano έγραψε:
> Harry Kalogirou wrote:
> >
> '> Yesterday I commited to the CVS some experimental swap support code,
> > based on Alan's work on the subject. Ofcourse this code is not included
> > in the default configuration and is not for _actual_ use, since as I
> > said is experimental. Apart from that if you set the swap partition in
> > malloc.c you and enable swapping you can enjoy an 8086 system use
> > _virtual_ memory!
> >
>
> Great!
>
> I've been looking for it in the code, and found nothing about it's
> configuration (setting the partition and the size, activating it...)...
> can someone (Harry, Alan) give us a few words about how to do so?
I will focus on making it easily configurable at run time later along
with documenting it a bit. Basicaly the code now is a 4 hour brain
storm. To configure it you basicaly change this part of the code :
holep = &swap_holes[0];
holep->flags = HOLE_FREE;
holep->page_base = 0;
holep->extent = 128;
holep->refcount = 0;
holep->next = NULL;
swap_dev = 0x0100;
The extent is the size in kilobytes and the swap_dev is the block device
to swap to. In the example 0x0100 is /dev/ram0
> And by the way... can you write a technical description about how is it
> done? The main problem with swap in minix was (is) that processes
It's on my TODO list...
> waiting for IO (waiting for a message from FS) can not be swapped in,
> because they would meet a deadlock when trying to swap out (for FS is
> needed again to do the swapping out, but it is frozen sending the
> message to the process, because FS is not reentrant/concurrent in
> minix)... and obviously processes waiting for IO are those best suited
> to be swapped in.
>
As you might already noticed we don't use the FS layer, we only support
swapping to a device at the momment. Once the think works we can add
swapping to file easily. For the minix matter now - our FS is reentrant
so we will have no problem...
Harry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-04-22 16:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 8:47 Swap support Harry Kalogirou
2002-04-22 13:42 ` Javier Sedano
2002-04-22 13:38 ` Dave Chavez
2002-04-22 16:29 ` Harry Kalogirou [this message]
2002-04-22 18:18 ` Riley Williams
2002-04-22 19:40 ` Harry Kalogirou
2002-04-22 20:19 ` Introduction and proposal: erich alfred heine
2002-04-22 20:58 ` Riley Williams
2002-04-22 21:04 ` Harry Kalogirou
2002-04-22 22:26 ` Riley Williams
2002-04-22 21:02 ` Harry Kalogirou
2002-04-23 7:32 ` Introduction and proposal:Documentation tom potts
2002-04-23 15:55 ` erich alfred heine
2002-04-22 20:35 ` Swap support Riley Williams
2002-04-22 20:58 ` Harry Kalogirou
2002-04-22 22:23 ` Riley Williams
2002-04-22 23:03 ` Dan Olson
2002-04-23 6:56 ` Harry Kalogirou
2002-04-23 20:03 ` Blaz Antonic
2002-04-23 19:36 ` Harry Kalogirou
2002-04-22 19:40 ` Harry Kalogirou
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=1019492981.479.128.camel@cool \
--to=harkal@gmx.net \
--cc=jsedano@dit.upm.es \
--cc=linux-8086@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