All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: dipankar@in.ibm.com
Cc: "Paul E. McKenney" <paulmck@us.ibm.com>,
	Arjan van de Ven <arjanv@redhat.com>,
	Robert Love <rml@ximian.com>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RCU for low latency (experimental)
Date: Sun, 28 Mar 2004 19:28:41 +0200	[thread overview]
Message-ID: <s5hu10898za.wl@alsa2.suse.de> (raw)
In-Reply-To: <20040328172036.GH5648@in.ibm.com>

At Sun, 28 Mar 2004 22:50:36 +0530,
Dipankar Sarma wrote:
> 
> On Sun, Mar 28, 2004 at 06:53:47PM +0200, Takashi Iwai wrote:
>
> > it seems count is never incremented in your patch...
> > or am i missing something?
> 
> I messed it up when I forward ported the throttle-rcu.patch
> from 2.6.0+lots-of-instrumentation to 2.6.4-vanilla in order
> to publish in lkml. The original patch did this -

thans for the patch.  i expected the similar fix :)

> > anyway, i confirmed that with the original krcud patch the latency
> > with dcache flood can be eliminated.
> 
> Does the throttle-rcu patch also help eliminate dcache flood ? You
> can try by just changing count >= rcumaxbatch to ++count > rcumaxbatch.

i'll try it later.

> > for the non-preemptive case, rcu_bh_callback_limit() should return
> > bhlimit always, though.  otherwise cond_resched() isn't called in the
> > callback loop properly.
>  
> Yes, I think we should consider using  limiting even in the non-preemptive
> case.

you mean preemptive case?


Takashi

  reply	other threads:[~2004-03-28 17:28 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-23 10:17 [PATCH] RCU for low latency (experimental) Dipankar Sarma
2004-03-23 10:25 ` Andrew Morton
2004-03-23 10:41   ` Dipankar Sarma
2004-03-23 10:35 ` Arjan van de Ven
2004-03-23 10:45   ` Dipankar Sarma
2004-03-23 12:31   ` Andrea Arcangeli
2004-03-23 12:40     ` Dipankar Sarma
2004-03-23 12:50       ` Andrea Arcangeli
2004-03-24 17:26         ` Paul E. McKenney
2004-03-24 17:51           ` Andrea Arcangeli
2004-03-24 20:02             ` Paul E. McKenney
2004-03-24 23:36               ` Andrea Arcangeli
2004-03-25  0:43                 ` Paul E. McKenney
2004-03-24 21:39             ` Dipankar Sarma
2004-03-24 22:53               ` Andrea Arcangeli
2004-03-24 23:11                 ` Dipankar Sarma
2004-03-24 23:34                   ` Andrea Arcangeli
2004-03-24 23:46                     ` Dipankar Sarma
2004-03-24 23:51                       ` Andrea Arcangeli
2004-03-28 16:53                       ` Takashi Iwai
2004-03-28 17:20                         ` Dipankar Sarma
2004-03-28 17:28                           ` Takashi Iwai [this message]
2004-03-29 10:43                             ` Takashi Iwai
2004-03-29 12:20                               ` Dipankar Sarma
2004-03-23 12:40     ` Arjan van de Ven
2004-03-23 12:29 ` Andrea Arcangeli
2004-03-23 12:34   ` Dipankar Sarma
2004-03-23 12:46     ` Andrea Arcangeli

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=s5hu10898za.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=akpm@osdl.org \
    --cc=arjanv@redhat.com \
    --cc=dipankar@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@us.ibm.com \
    --cc=rml@ximian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.