Re: Some interesting observations when trying to optimize vmstat handling

> There is an interrupt enable overhead of 48 cycles that would be good to
> be able to eliminate (Kernel code usually moves counter increments into
> a neighboring interrupt disable section so that __ function can be used).

Replace the push flags ; popf  with test $IFMASK,flags ; jz 1f; sti ; 1:
That will likely make it much faster (but also bigger) 

The only problem is that there might be some code who relies on 
restore_flags() restoring other flags that IF, but at least for interrupts
and local_irq_save/restore it should be fine to change.

-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: Some interesting observations when trying to optimize vmstat handling
    • From: Jeremy Fitzhardinge <[email protected]>
  • Re: Some interesting observations when trying to optimize vmstat handling
    • From: Christoph Lameter <[email protected]>

• References:
  • Some interesting observations when trying to optimize vmstat handling
    • From: Christoph Lameter <[email protected]>

• Prev by Date: Re: [PATCH RFC 3/7] x86: clean up asm-x86/page*.h
• Next by Date: Re: [PATCH] Align PCI memory regions to page size (4K) - Fix
• Previous by thread: Some interesting observations when trying to optimize vmstat handling
• Next by thread: Re: Some interesting observations when trying to optimize vmstat handling
• 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]