From: george anzinger <george@mvista.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@transmeta.com>,
Russell King <rmk@arm.linux.org.uk>,
"David S. Miller" <davem@redhat.com>
Subject: Re: [announce, patch, RFC] "big IRQ lock" removal, IRQ cleanups.
Date: Fri, 19 Jul 2002 14:49:25 -0700 [thread overview]
Message-ID: <3D388965.59690A44@mvista.com> (raw)
In-Reply-To: Pine.LNX.4.44.0207202235400.23137-100000@localhost.localdomain
Ingo Molnar wrote:
>
> the following patch, against 2.5.26:
>
> http://redhat.com/~mingo/remove-irqlock-patches/remove-irqlock-2.5.26-A2
I haven't applied the patch, but just looking at it, it
appears that you have removed the conditional call to
softirq on local_bh_enable(). Isn't this needed?
-g
>
> is a work-in-progress massive cleanup of the IRQ subsystem. It's losely
> based on Linus' original idea and DaveM's original implementation, to fold
> our various irq, softirq and bh counters into the preemption counter.
>
> with this approach it was possible:
>
> - to remove the 'big IRQ lock' on SMP - on which sti() and cli() relied.
>
> - to streamline/simplify arch/i386/kernel/irq.c significantly.
>
> - to simplify the softirq code.
>
> - to remove the preemption count increase/decrease code from the lowlevel
> IRQ assembly code.
>
> - to speed up schedule() a bit.
>
> sti() and cli() is gone forever, there is no more globally synchronizing
> irq-disabling capability. All code that relied on sti() and cli() and
> restore_flags() must use other locking mechanisms from now on (spinlocks
> and __cli()/__sti()).
>
> obviously this patch breaks massive amounts of code, so only limited
> .configs are working at the moment, such as:
>
> http://redhat.com/~mingo/remove-irqlock-patches/config
>
> otherwise the patch was developed and tested on SMP systems, and while the
> code is still a bit rough in places, the base IRQ code appears to be
> pretty robust and clean.
>
> while it boots already so the worst is over, there is lots of work left:
> eg. to fix the serial layer to not use cli()/sti() and bhs ...
>
> RMK, is there any chance to get your new serial layer into 2.5 sometime
> soon? ['soon' as in 'tomorrow' :-) ] That is perhaps one of the biggest
> kernel subsystems that make use of cli()/sti() currently. The rest is
> drivers mostly, which is still not unsignificant, but perhaps a bit easier
> to manage.
>
> Ingo
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
George Anzinger george@mvista.com
High-res-timers:
http://sourceforge.net/projects/high-res-timers/
Real time sched: http://sourceforge.net/projects/rtsched/
Preemption patch:
http://www.kernel.org/pub/linux/kernel/people/rml
next prev parent reply other threads:[~2002-07-19 21:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-20 20:54 [announce, patch, RFC] "big IRQ lock" removal, IRQ cleanups Ingo Molnar
2002-07-19 21:49 ` george anzinger [this message]
2002-07-20 14:25 ` Marcin Dalecki
2002-07-21 21:17 ` Ingo Molnar
2002-07-20 20:57 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2002-07-22 14:45 Oleg Nesterov
2002-07-22 18:03 ` george anzinger
2002-07-22 18:04 ` Ingo Molnar
2002-07-20 17:57 Oleg Nesterov
2002-07-21 23:43 ` george anzinger
2002-07-21 23:50 ` Ingo Molnar
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=3D388965.59690A44@mvista.com \
--to=george@mvista.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rmk@arm.linux.org.uk \
--cc=torvalds@transmeta.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