Re: [PATCH 1/11] Fix CONFIG_COMPAT_VDSO

Roland McGrath wrote:
>
> I wouldn't mind if CONFIG_COMPAT_VDSO went away entirely.
> But if it's there, it should work properly.  Currently
> it's quite haphazard: both real vma and fixmap are
> mapped, both are put in the two different AT_* slots,
> sysenter returns to the vma address rather than the
> fixmap address, and core dumps yet are another story.
>
> This patch makes CONFIG_COMPAT_VDSO disable the real vma
> and use the fixmap area consistently.  This makes it
> actually compatible with what the old vdso implementation did.

I just tried your patch, but your changes seem to revert performance 
improvements achieved with 2.6.19, when vdso_enabled=1 and 
randomize_va_space=0.


Thanks!

--
Al

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

---

• Prev by Date: Re: [PATCH] Provide an interface to limit total page cache.
• Next by Date: Re: prioritize PCI traffic ?
• Previous by thread: Re: [PATCH 1/11] Fix CONFIG_COMPAT_VDSO
• Next by thread: [patch 0/3] Scheduled removal of SA_xxx interrupt flags
• 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]