Re: [13/17] Virtual compound page freeing in interrupt context

On Wed, 19 Sep 2007, Nick Piggin wrote:

> > Removing a virtual mappping *must* be done with interrupts enabled
> > since tlb_xx functions are called that rely on interrupts for
> > processor to processor communications.
> 
> These things will clash drastically with my lazy TLB flushing and scalability
> work. Actually the lazy TLB flushing will provide a natural way to defer
> unmapping at interrupt time, and the scalability work should make it
> easier to vmap from interrupt context too, if you really need that.

Both would be good to have.

-
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/

---

• References:
  • [00/17] [RFC] Virtual Compound Page Support
    • From: Christoph Lameter <[email protected]>
  • [13/17] Virtual compound page freeing in interrupt context
    • From: Christoph Lameter <[email protected]>
  • Re: [13/17] Virtual compound page freeing in interrupt context
    • From: Nick Piggin <[email protected]>

• Prev by Date: Re: [PATCH 2/3] CRED: Split the task security data and move part of it into struct cred
• Next by Date: Re: [PATCH -mm] sb16: Shut up uninitialized var build warning
• Previous by thread: Re: [13/17] Virtual compound page freeing in interrupt context
• Next by thread: [14/17] Allow bit_waitqueue to wait on a bit in a vmalloc area
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]