From: Ingo Molnar <mingo@elte.hu>
To: BlaisorBlade <blaisorblade_spam@yahoo.it>
Cc: Jeff Dike <jdike@addtoit.com>,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] 2.6-specific UML patches (modules, modversions, various other stuff)
Date: Sun, 11 Jan 2004 13:10:17 +0100 [thread overview]
Message-ID: <20040111121017.GA17405@elte.hu> (raw)
In-Reply-To: <200401061921.00054.blaisorblade_spam@yahoo.it>
* BlaisorBlade <blaisorblade_spam@yahoo.it> wrote:
> There you will find a number of patches for UML 2.6. Some are mine and
> some come from Ingo and M A Young; I've included everything Ingo
> posted minus the speedup - breakage for 2.4 host. That is,
> MM_COPY_SEGMENTS is still called by UML but if the host is a 2.6 that
> is a no-op.
i'd suggest to skip my speedup altogether, skas4 ought to make it
obsolete.
i think it still makes sense to keep host-skas3 working in the 2.6 combo
patch until Jeff releases skas4 - the positive performance impact from
the host-skas concept is significant and the difference between skas3
and skas4 should not affect performance much, it's 'just' a (much)
cleaner interface.
Ingo
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2004-01-11 12:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-06 18:20 [uml-devel] 2.6-specific UML patches (modules, modversions, various other stuff) BlaisorBlade
2004-01-06 19:09 ` [uml-devel] " Jeff Dike
2004-01-06 19:24 ` BlaisorBlade
2004-01-11 12:10 ` Ingo Molnar [this message]
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=20040111121017.GA17405@elte.hu \
--to=mingo@elte.hu \
--cc=blaisorblade_spam@yahoo.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox