From: Dipankar Sarma <dipankar@in.ibm.com>
To: "David S. Miller" <davem@redhat.com>
Cc: mingo@elte.hu, torvalds@transmeta.com,
linux-kernel@vger.kernel.org, wli@holomorphy.com,
kuznet@ms2.inr.ac.ru
Subject: Re: [patch] smptimers, old BH removal, tq-cleanup, 2.5.39
Date: Mon, 30 Sep 2002 10:03:17 +0530 [thread overview]
Message-ID: <20020930100317.A21939@in.ibm.com> (raw)
In-Reply-To: <20020929.172022.23984844.davem@redhat.com>; from davem@redhat.com on Sun, Sep 29, 2002 at 05:20:22PM -0700
On Sun, Sep 29, 2002 at 05:20:22PM -0700, David S. Miller wrote:
> From: Dipankar Sarma <dipankar@in.ibm.com>
> Date: Mon, 30 Sep 2002 00:45:59 +0530
>
> > net_bh_lock: i have removed it, since it would synchronize to nothing. The
> > old protocol handlers should still run on UP, and on SMP the kernel prints
> > a warning upon use. Alexey, is this approach fine with you?
>
> The cache line bouncing of global_bh_lock and net_bh_lock in
> run_timer_tasklet() show up in our profiles, so getting rid of
> them is a good thing (TM).
>
> What ancient protocols are you running that make use of this?
I wasn't running any old protocols. It was a problem I faced
with my port of smptimers - I serialized
wrt BHs and old protocols using global_bh_lock and net_bh_lock (exported
it globally) respectively in the per-cpu tasklet that runs timers.
So, the spin_trylock() in run_timer_tasklet() would modify the
lock cache line and hence the bouncing. Getting rid of BHs and
old protocol serialization avoids this as in Ingo's latest patch.
>
> IPv4 and IPv6 both do not use it at all. Even IPX, Appletalk, and
> DecNET layers do not use it
This is the list, I think, by looking at packet_types -
802/psnap.c
appletalk/ddp.c
ax25/af_ax25.c
core/ext8022.c
econet/af_econet.c
irda/irsyms.c
x25/af_x25.c
Thanks
--
Dipankar Sarma <dipankar@in.ibm.com> http://lse.sourceforge.net
Linux Technology Center, IBM Software Lab, Bangalore, India.
next prev parent reply other threads:[~2002-09-30 4:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 17:52 [patch] smptimers, old BH removal, tq-cleanup, 2.5.39 Ingo Molnar
2002-09-29 18:38 ` Jeff Garzik
2002-09-29 18:50 ` Jeff Garzik
2002-09-29 19:27 ` Ingo Molnar
2002-09-29 19:48 ` Jeff Garzik
2002-09-29 18:54 ` Dave Jones
2002-09-29 19:15 ` Dipankar Sarma
2002-09-30 0:20 ` David S. Miller
2002-09-30 4:33 ` Dipankar Sarma [this message]
2002-09-30 4:28 ` David S. Miller
2002-09-30 4:38 ` Arnaldo Carvalho de Melo
2002-09-30 12:55 ` Alan Cox
2002-09-30 14:50 ` Arnaldo Carvalho de Melo
2002-09-29 19:16 ` Ingo Molnar
2002-09-30 0:39 ` David S. Miller
2002-09-30 6:06 ` Ingo Molnar
2002-09-30 21:45 ` george anzinger
2002-10-01 3:51 ` Ingo Molnar
2002-10-01 4:18 ` David S. Miller
2002-10-01 5:24 ` Ingo Molnar
2002-10-01 8:00 ` george anzinger
2002-10-01 5:33 ` Dipankar Sarma
2002-10-03 7:10 ` Dipankar Sarma
2002-09-30 23:37 ` Christoph Hellwig
2002-09-30 16:38 ` Ingo Molnar
2002-09-30 23:45 ` Christoph Hellwig
2002-09-30 17:12 ` Ingo Molnar
2002-10-01 0:43 ` Christoph Hellwig
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=20020930100317.A21939@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@transmeta.com \
--cc=wli@holomorphy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox