From: "J.A. Magallon" <jamagallon@able.es>
To: Anton Blanchard <anton@samba.org>
Cc: Dipankar Sarma <dipankar@in.ibm.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Dave Miller <davem@redhat.com>
Subject: Re: [RFC][PATCH] TIMER_BH-less smptimers
Date: Mon, 20 May 2002 23:21:09 +0200 [thread overview]
Message-ID: <20020520212109.GA5821@werewolf.able.es> (raw)
In-Reply-To: <20020516185448.A8069@in.ibm.com> <20020520085500.GB14488@krispykreme>
On 2002.05.20 Anton Blanchard wrote:
>
>Hi Dipankar,
>
>> I have been experimenting with Ingo's smptimers and I ended up
>> extending it a little bit. I would really appreciate comments
>> on whether these things make sense or not.
>
>I tried it out and found that we were context switching like crazy.
>It seems we were always running the timers out of a tasklet because
>we never unlocked the net_bh_lock.
>
The patch for 2.4 in
http://people.redhat.com/mingo/scalable-timers-patches/
does not acquire net_bh_lock. Then I suppose it does not apply to that ?
So this patch is a little outdated wrt the one for 2.5. Is there any
updated version available for 2.4 ?
Can I try your patch for 2.5 on 2.4 or is there any infrastructure
missing ?
TIA
--
J.A. Magallon # Let the source be with you...
mailto:jamagallon@able.es
Mandrake Linux release 8.3 (Cooker) for i586
Linux werewolf 2.4.19-pre8-jam3 #1 SMP dom may 19 21:07:40 CEST 2002 i686
next prev parent reply other threads:[~2002-05-20 21:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-16 13:24 [RFC][PATCH] TIMER_BH-less smptimers Dipankar Sarma
2002-05-20 8:55 ` Anton Blanchard
2002-05-20 10:29 ` Dipankar Sarma
2002-05-20 13:31 ` Anton Blanchard
2002-05-21 6:26 ` Dipankar Sarma
2002-05-20 12:38 ` Dipankar Sarma
2002-05-20 21:21 ` J.A. Magallon [this message]
2002-05-21 6:18 ` Dipankar Sarma
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=20020520212109.GA5821@werewolf.able.es \
--to=jamagallon@able.es \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=anton@samba.org \
--cc=davem@redhat.com \
--cc=dipankar@in.ibm.com \
--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