From: Ingo Molnar <mingo@elte.hu>
To: Marin Mitov <mitov@issp.bas.bg>
Cc: linux-kernel@vger.kernel.org
Subject: Re: some thoughts about TSC based delay_tsc()
Date: Wed, 21 Nov 2007 21:09:58 +0100 [thread overview]
Message-ID: <20071121200958.GA30663@elte.hu> (raw)
In-Reply-To: <200711212206.34339.mitov@issp.bas.bg>
* Marin Mitov <mitov@issp.bas.bg> wrote:
> On Wednesday 21 November 2007 09:27:54 pm you wrote:
> > * Marin Mitov <mitov@issp.bas.bg> wrote:
> > > Hi Ingo,
> > >
> > > The patch is quite good ;-) but we forget when it is needed :-( In
> > > fact we need it only for PREEMPT SMP kernels - it could hurt
> > > PREEMPT UP kernels (no migration possible), so no need for
> > > preempt_disable()/preempt_enable().
> > >
> > > In short the old version of delay_tsc() is good for UP kernels and
> > > NON PREEMPT SMP kernels too.
> >
> > please reply to the public list, so that discussions do not get lost.
> >
> > i dont think there's any problem: udelay() is about _wasting_ cycles -
> > it's what drivers use for short delays.
>
> Sure for the thread executing udelay(), but not for the other ready
> threads which should also wait till preempt_enable() to grab the same
> cpu even for PREEMPT (UP or SMP) kernels (or I misunderstand
> something?).
on non-PREEMPT kernels there's no real difference between old and and
new code because the kernel is not preemptible. So we can use the new
code unconditionally.
Ingo
prev parent reply other threads:[~2007-11-21 20:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200711212057.10465.mitov@issp.bas.bg>
[not found] ` <20071121192754.GA22769@elte.hu>
2007-11-21 20:06 ` Marin Mitov
2007-11-21 20:09 ` 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=20071121200958.GA30663@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=mitov@issp.bas.bg \
/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
all inboxes | Powered by JetHome®