linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kanoj@google.engr.sgi.com (Kanoj Sarcar)
To: Chuck Lever <cel@monkey.org>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-mm@kvack.org
Subject: Re: [PATCH] mincore for i386, against 2.3.51
Date: Mon, 13 Mar 2000 09:46:36 -0800 (PST)	[thread overview]
Message-ID: <200003131746.JAA90301@google.engr.sgi.com> (raw)
In-Reply-To: <Pine.BSO.4.10.10003121941460.5358-100000@funky.monkey.org> from "Chuck Lever" at Mar 12, 2000 07:45:53 PM

Couple of things:

#1
>  static struct vm_operations_struct shm_vm_ops = {
>  	open:	shm_open,	/* callback for a new vm-area open */
>  	close:	shm_close,	/* callback for when the vm-area is released */
> +	incore:	shm_incore,
>  	nopage:	shm_nopage,
>  	swapout:shm_swapout,
>  };

shmzero_vm_ops should also probably have a incore function. /dev/zero is
quite similar to shm, except the locking protocol is a little different
(look at shmzero_nopage and shm_nopage), you should be able to seperate
out the shm incore() function into a basic routine/#define that both shm
and /dev/zero can use. Let me know if you need help with this.

#2. It wasn't very clear to me how MAP_ANON pages are being handled. Maybe
I did not read the patch closely enough.

#3. If you have the time, it might make sense to pump out the #pages via
/proc/pid/maps too (although I don't know whether that will break some
apps that already know the output format).

Kanoj
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

  reply	other threads:[~2000-03-13 17:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-13  0:45 Chuck Lever
2000-03-13 17:46 ` Kanoj Sarcar [this message]
2000-03-13 18:16   ` Chuck Lever
2000-03-13 18:28     ` Kanoj Sarcar
2000-03-13 18:35       ` Linus Torvalds
2000-03-13 19:56         ` Chuck Lever
2000-03-13 20:31           ` Linus Torvalds
2000-03-13 21:32             ` Chuck Lever

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=200003131746.JAA90301@google.engr.sgi.com \
    --to=kanoj@google.engr.sgi.com \
    --cc=cel@monkey.org \
    --cc=linux-mm@kvack.org \
    --cc=torvalds@transmeta.com \
    /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