From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@osdl.org>
Cc: viro@parcelfarce.linux.theplanet.co.uk, linux-kernel@vger.kernel.org
Subject: Re: [patch] inode-lock-break.patch, 2.6.8-rc3-mm2
Date: Mon, 9 Aug 2004 12:45:33 +0200 [thread overview]
Message-ID: <20040809104533.GA13710@elte.hu> (raw)
In-Reply-To: <20040809032523.40250fe8.akpm@osdl.org>
* Andrew Morton <akpm@osdl.org> wrote:
> > tested on x86, the patch solves these particular latencies.
>
> On uniprocessor only. What are we going to do about SMP?
i believe we should 'ignore' SMP spinlock starvation for now: it will be
fixed in a natural way with the most-spinlocks-are-mutexes solution,
with that approach all preemption wishes of other CPUs are properly
expressed in terms of need_resched().
alternatively the 'release the lock every 128 iterations and do a
cpu_relax()' hack could be used - but i think that doesnt solve the SMP
issues in a sufficiant way.
Ingo
next prev parent reply other threads:[~2004-08-09 11:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 10:21 [patch] inode-lock-break.patch, 2.6.8-rc3-mm2 Ingo Molnar
2004-08-09 10:25 ` Andrew Morton
2004-08-09 10:45 ` Ingo Molnar [this message]
2004-08-09 14:01 ` [patch] preempt-smp.patch, 2.6.8-rc3-mm2 Ingo Molnar
2004-08-11 16:14 ` Peter Zijlstra
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=20040809104533.GA13710@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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