From: "Maksim (Max) Krasnyanskiy" <maxk@qualcomm.com>
To: Ingo Molnar <mingo@elte.hu>, "David S. Miller" <davem@redhat.com>
Cc: <kuznet@ms2.inr.ac.ru>, <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Rename _bh to _softirq
Date: Tue, 15 Oct 2002 15:09:36 -0700 [thread overview]
Message-ID: <5.1.0.14.2.20021015150438.051d52d8@mail1.qualcomm.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0210152318150.26315-100000@localhost.localdo main>
> > "base handler" and "bottom half" all refer to an execution context,
> > and these days that means softirq.
>
>i think i agree with you.
>
>- we have 'top half' contexts, which are also called 'hardirqs'.
>
>- then we have 'bottom half' contexts, which are also called 'softirqs'.
>
>the fact that 'bottom halves' used to be an earlier concept that had a
>slightly different meaning from 'softirqs' for a limited amount of time
>does not remove from the meaningfulness of the naming itself. Today
>'bottom halves' and 'softirqs' are the same thing.
I still think we should rename _bh thing :). At least for consistent naming.
We have things like:
in_softirq()
do_softirq()
sofirq_pending()
and
local_bh_disable()
local_bh_enable()
Anyway, I'll go ahead and shut up :). Most people didn't seem to like that
proposal :(.
Max
next prev parent reply other threads:[~2002-10-15 22:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-14 19:02 [RFC] Rename _bh to _softirq Maksim (Max) Krasnyanskiy
2002-10-13 19:17 ` THIS_MODULE->name=""; Ron Henry
2002-10-14 19:12 ` [RFC] Rename _bh to _softirq Jeff Garzik
2002-10-14 20:05 ` Maksim (Max) Krasnyanskiy
2002-10-14 19:21 ` Ingo Molnar
2002-10-15 1:57 ` kuznet
2002-10-15 16:34 ` Maksim (Max) Krasnyanskiy
2002-10-15 17:44 ` David S. Miller
2002-10-15 19:24 ` Maksim (Max) Krasnyanskiy
2002-10-15 19:42 ` David S. Miller
2002-10-15 20:23 ` Maksim (Max) Krasnyanskiy
2002-10-15 20:19 ` David S. Miller
2002-10-15 21:02 ` Maksim (Max) Krasnyanskiy
2002-10-15 20:58 ` David S. Miller
2002-10-15 21:27 ` Brad Hards
2002-10-15 21:28 ` Ingo Molnar
2002-10-15 21:20 ` Ingo Molnar
[not found] ` <Pine.LNX.4.44.0210152318150.26315-100000@localhost.localdo main>
2002-10-15 22:09 ` Maksim (Max) Krasnyanskiy [this message]
2002-10-15 19:55 ` Oliver Xymoron
2002-10-15 20:30 ` Maksim (Max) Krasnyanskiy
2002-10-15 21:17 ` Ingo Molnar
[not found] ` <Pine.LNX.4.44.0210142119300.26635-100000@localhost.localdo main>
2002-10-14 19:58 ` Maksim (Max) Krasnyanskiy
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=5.1.0.14.2.20021015150438.051d52d8@mail1.qualcomm.com \
--to=maxk@qualcomm.com \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--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;
as well as URLs for NNTP newsgroup(s).