From: stevegt@TerraLuna.Org
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] SKAS: Why pass mm vs. current?
Date: Fri, 5 Sep 2003 14:08:19 -0700 [thread overview]
Message-ID: <20030905210818.GE1601@pathfinder> (raw)
In-Reply-To: <200309052012.h85KCojh001348@ccure.karaya.com>
On Fri, Sep 05, 2003 at 04:12:50PM -0400, Jeff Dike wrote:
> stevegt@TerraLuna.Org said:
> > I have a question about why the skas patch passes mm down through the
> > do_mmap* call tree. Why not just use current->mm when needed, the way
> > the original kernel does? Or, if there's a context issue, then why
> > not pass all of current as a task_struct pointer, instead of just
> > current->mm?
>
> Because the only thing needed is the mm. I don't like passing a lot of
> information through an interface when only one piece of it is actually needed.
Makes sense.
But why not get mm from current when needed deeper down, rather than
pass it in the first place? That would avoid having to change the
interface. I'm happy to put that patch together, if you don't see
anything wrong with the idea.
Steve
--
Steve Traugott (KG6HDQ)
Speaker Coordinator, Silicon Valley Linux Users Group
http://www.svlug.org
--
UNIX/Linux Infrastructure Architect, TerraLuna LLC
stevegt@TerraLuna.Org
http://www.stevegt.com
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2003-09-05 21:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 2:06 [uml-devel] SKAS: Why pass mm vs. current? stevegt
2003-09-05 20:12 ` Jeff Dike
2003-09-05 21:08 ` stevegt [this message]
2003-09-05 21:28 ` Bryan O'Sullivan
2003-09-05 21:47 ` stevegt
2003-09-05 21:53 ` Bryan O'Sullivan
2003-09-08 22:51 ` Adam Heath
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=20030905210818.GE1601@pathfinder \
--to=stevegt@terraluna.org \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.