From: Dipankar Sarma <dipankar@in.ibm.com>
To: Christoph Hellwig <hch@ns.caldera.de>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] Ingo's smptimers patch experiment
Date: Thu, 7 Feb 2002 11:44:13 +0530 [thread overview]
Message-ID: <20020207114413.A10060@in.ibm.com> (raw)
In-Reply-To: <20020206211925.A8720@in.ibm.com> <200202061727.g16HRkG12893@ns.caldera.de>
In-Reply-To: <200202061727.g16HRkG12893@ns.caldera.de>; from hch@ns.caldera.de on Wed, Feb 06, 2002 at 06:27:46PM +0100
On Wed, Feb 06, 2002 at 06:27:46PM +0100, Christoph Hellwig wrote:
> In article <20020206211925.A8720@in.ibm.com> you wrote:
> > Hi Ingo,
> >
> > I ported your smptimers patch to 2.5.3 and experimented with
> > it a little bit. Basically I am curious about why we
> > we need to call run_all_timers() (which runs timers for all
> > CPUs) through the timer bh if locking fails in run_local_timers().
>
> Some driver do ugly things with TIMER_BH, and Ingo's 2.4 patched
> tried to stayed source compatible with 2.4 drivers.
>
> For 2.5 I'd really like to see TIMER_BH (all BH's in fact) to gone.
I can see that net driver relies on being able to disable all timers
by doing in net/core/dev.c -
tasklet_disable(bh_task_vec+TIMER_BH);
But this doesn't completely disable timers in Ingo's patch
since timers can also be fired through run_local_timers() if
locking succeeds, no TIMER_BH in that case.
There are only a few places where TIMER_BH is used. I will see if
I can make another smptimers patch that gets rid of them.
Thanks
Dipankar
--
Dipankar Sarma <dipankar@in.ibm.com> http://lse.sourceforge.net
Linux Technology Center, IBM Software Lab, Bangalore, India.
prev parent reply other threads:[~2002-02-07 6:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-06 15:49 [RFC][PATCH] Ingo's smptimers patch experiment Dipankar Sarma
2002-02-06 17:27 ` Christoph Hellwig
2002-02-07 6:14 ` Dipankar Sarma [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=20020207114413.A10060@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=hch@ns.caldera.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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