> Hmmmm... The spinlock is its own flag. Yes, but it's not CPU local. Taking the spinlock from another CPU's interrupt handler is perfectly safe, just not from the local CPU. If you use the spinlock as flag you would need to lock out everybody. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [RFC 4/9] Atomic reclaim: Save irq flags in vmscan.c
- From: Christoph Lameter <[email protected]>
- Re: [RFC 4/9] Atomic reclaim: Save irq flags in vmscan.c
- References:
- [RFC 0/9] Reclaim during GFP_ATOMIC allocs
- From: Christoph Lameter <[email protected]>
- [RFC 4/9] Atomic reclaim: Save irq flags in vmscan.c
- From: Christoph Lameter <[email protected]>
- Re: [RFC 4/9] Atomic reclaim: Save irq flags in vmscan.c
- From: Andi Kleen <[email protected]>
- Re: [RFC 4/9] Atomic reclaim: Save irq flags in vmscan.c
- From: Christoph Lameter <[email protected]>
- Re: [RFC 4/9] Atomic reclaim: Save irq flags in vmscan.c
- From: Andi Kleen <[email protected]>
- Re: [RFC 4/9] Atomic reclaim: Save irq flags in vmscan.c
- From: Christoph Lameter <[email protected]>
- [RFC 0/9] Reclaim during GFP_ATOMIC allocs
- Prev by Date: Re: [RFC 4/9] Atomic reclaim: Save irq flags in vmscan.c
- Next by Date: Re: Regression in 2.6.23-rc2-mm2, mounting cpusets causes a hang
- Previous by thread: Re: [RFC 4/9] Atomic reclaim: Save irq flags in vmscan.c
- Next by thread: Re: [RFC 4/9] Atomic reclaim: Save irq flags in vmscan.c
- Index(es):
 |