public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Stas Sergeev <stsp@list.ru>
To: solarflow99 <solarflow99@gmail.com>
Cc: Paul Crawford <psc@sat.dundee.ac.uk>,
	dosemu <linux-msdos@vger.kernel.org>,
	Bart Oldeman <bartoldeman@gmail.com>
Subject: Re: Warning about kernel 4.2 performance (revised)
Date: Fri, 16 Oct 2015 23:20:27 +0300	[thread overview]
Message-ID: <56215C0B.3050200@list.ru> (raw)
In-Reply-To: <CAO8i5OJKpT8RybtL_6xVs9tOQXoKMxJ=v0vKoQR1ULMe=XOphA@mail.gmail.com>

16.10.2015 05:07, solarflow99 пишет:
> this is great if this provides an easier way to make dos programs work
> in 64 bit mode.  In the thread it sounds like vm86 might still be
> used, so not sure which way it should go,
vm86 never worked in 64bit mode.
This is actually the reason I didn't rush re-implementing it
in the kernel: I don't even use it myself, so I felt very guilty
even defending it in lkml.
So I guess the kvm efforts that Bart started, will eventually
do the trick better than vm86 ever could. But this will require
some coding efforts to get right. Much less in dosemu2 than
in dosemu1, because dosemu2 was already freed from most
vm86 ugly dependencies (but not all, as it now appears).

> Switching to KVM would change things a lot, dosemu2 would make sense for that.
For some workloads (heavy games, gfx effects etc) dosemu2
without vm86 is faster than dosemu1 with vm86. Try
Destruction Derby, Settlers2, NFS-SE or even doom2 to
see the difference (vm86 is not in a big use for these games
though, that's why the difference will be serious).
--
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-10-16 20:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-03  7:56 Warning about kernel 4.2 performance Andrew Bird
2015-10-04  4:27 ` solarflow99
2015-10-04  7:16   ` Andrew Bird
2015-10-04  8:35     ` Felix Miata
2015-10-04  9:27       ` Andrew Bird
2015-10-04 10:32       ` Warning about kernel 4.2 performance (revised) Andrew Bird
2015-10-04 17:26         ` Felix Miata
2015-10-04 17:36           ` Stas Sergeev
2015-10-05  9:47             ` Andrew Bird
2015-10-05 11:20               ` Stas Sergeev
2015-10-05 12:03                 ` Andrew Bird
     [not found]                   ` <CABHtM7Wn44rMU11iKx8H2Z3gZMwWzLKfD7b+KZP8m+1RRmxQ3A@mail.gmail.com>
2015-10-14 18:46                     ` Fwd: " Bart Oldeman
2015-10-14 19:10                       ` Paul Crawford
2015-10-14 22:08                         ` Stas Sergeev
2015-10-16  2:07                           ` solarflow99
2015-10-16 20:20                             ` Stas Sergeev [this message]
2015-10-04 16:55     ` Warning about kernel 4.2 performance Stas Sergeev
2015-10-04 20:45       ` solarflow99
2015-10-05  9:33         ` Andrew Bird
2015-10-05 10:05           ` Stas Sergeev

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=56215C0B.3050200@list.ru \
    --to=stsp@list.ru \
    --cc=bartoldeman@gmail.com \
    --cc=linux-msdos@vger.kernel.org \
    --cc=psc@sat.dundee.ac.uk \
    --cc=solarflow99@gmail.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