From: David Woodhouse <dwmw2@infradead.org>
To: Arun Sharma <arun.sharma@intel.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Re: [PATCH] Support ia32 exec domains without CONFIG_IA32_SUPPORT
Date: Tue, 12 Oct 2004 22:50:24 +0100 [thread overview]
Message-ID: <1097617824.5178.20.camel@localhost.localdomain> (raw)
In-Reply-To: <416AF599.2060801@intel.com>
On Mon, 2004-10-11 at 14:05 -0700, Arun Sharma wrote:
> I've prototyped a generic userland solution that covers just open and
> stat system calls (for completeness, all path walk related syscalls
> need to be covered) using the LD_PRELOAD approach.
>
> I saw a 16% degradation in system time on this benchmark:
>
> find /usr/src/linux -name '*.[chS]' | xargs grep fsck
>
> mainly due to the doubling of the number of calls to open. Also, there
> was a slight increase in user time as well, due to malloc/free
> overhead.
The patch is entirely bogus. This isn't at all ia64-specific, and
doesn't live in arch/ia64. It's just as applicable on _all_ systems
where we may want to do CPU or OS emulation.
If you make it generic so that qemu can use it for emulating i386 even
on machines like ppc64, perhaps it would be saner.
--
dwmw2
next prev parent reply other threads:[~2004-10-12 21:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <41643EC0.1010505@intel.com>
[not found] ` <20041007142710.A12688@infradead.org>
[not found] ` <4165D4C9.2040804@intel.com>
[not found] ` <mailman.1097223239.25078@unix-os.sc.intel.com>
[not found] ` <41671696.1060706@intel.com>
[not found] ` <mailman.1097403036.11924@unix-os.sc.intel.com>
2004-10-11 21:05 ` [PATCH] Support ia32 exec domains without CONFIG_IA32_SUPPORT Arun Sharma
2004-10-12 21:50 ` David Woodhouse [this message]
2004-10-12 22:46 ` Arun Sharma
2004-10-13 22:27 ` Arun Sharma
2004-10-14 7:32 ` David Mosberger
2004-10-14 8:25 ` David Woodhouse
2004-10-14 8:50 ` Jakub Jelinek
2004-10-14 17:53 ` Arun Sharma
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=1097617824.5178.20.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=arun.sharma@intel.com \
--cc=hch@infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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