From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: ashwin.chaugule@celunite.com
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Rik van Riel <riel@redhat.com>
Subject: Re: [RFC][PATCH 0/2] Swap token re-tuned
Date: Mon, 02 Oct 2006 13:08:45 +0200 [thread overview]
Message-ID: <1159787325.28131.144.camel@taijtu> (raw)
In-Reply-To: <1159786807.5574.14.camel@localhost.localdomain>
On Mon, 2006-10-02 at 16:30 +0530, Ashwin Chaugule wrote:
> On Mon, 2006-10-02 at 09:35 +0200, Peter Zijlstra wrote:
> > So while I agree it would be nice to get rid of all magic variables
> > (holding time in the current impl) this proposed solution hasn't
> > convinced me (for one it introduces another).
> >
> > (for the interrested, the various attempts I tried are available here:
> > http://programming.kicks-ass.net/kernel-patches/swap_token/ )
>
> Cool!
>
> Had you applied these patches when you posted your test results ?
Only my test box ever ran them.
They are replacements for your 2nd patch, timings I got from them were
worse than with yours though, needs more attention.
A variation on 3 I have in mind is to reset the prio of the loosing mm
to 0 - this should avoid it regaining the token quickly.
next prev parent reply other threads:[~2006-10-02 11:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 18:41 [RFC][PATCH 0/2] Swap token re-tuned Ashwin Chaugule
2006-10-01 22:56 ` Andrew Morton
2006-10-02 7:35 ` Peter Zijlstra
2006-10-02 7:59 ` Andrew Morton
2006-10-02 8:14 ` Peter Zijlstra
2006-10-03 7:32 ` Peter Zijlstra
2006-10-08 20:23 ` [RFC][PATCH 1/2] grab swap token reordered Ashwin Chaugule
2006-10-08 20:28 ` [RFC][PATCH 2/2] new scheme to preempt swap token Ashwin Chaugule
2006-10-02 11:00 ` [RFC][PATCH 0/2] Swap token re-tuned Ashwin Chaugule
2006-10-02 11:08 ` Peter Zijlstra [this message]
2006-10-02 8:20 ` Ashwin Chaugule
2006-10-02 10:00 ` Ashwin Chaugule
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=1159787325.28131.144.camel@taijtu \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@osdl.org \
--cc=ashwin.chaugule@celunite.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.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