From: Avi Kivity <avi@argo.co.il>
To: Jeff Dike <jdike@addtoit.com>
Cc: Renzo Davoli <renzo@cs.unibo.it>,
Alan Cox <alan@lxorguk.ukuu.org.uk>, Andi Kleen <ak@suse.de>,
Daniel Jacobowitz <dan@debian.org>,
Ulrich Drepper <drepper@gmail.com>,
osd@cs.unibo.it, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2-ptrace_multi
Date: Sun, 21 May 2006 15:38:16 +0300 [thread overview]
Message-ID: <44705F38.10905@argo.co.il> (raw)
In-Reply-To: <20060520213959.GA4229@ccure.user-mode-linux.org>
Jeff Dike wrote:
>> PTRACE_MULTI can be also used to optimize many other virtualized calls,
>> e.g. to read/write all the buffers for a readv/writev/recvmsg/sendmsg
>> call at once.
>>
>
> Here, I bet the data copying cost dominates the system call, and the
> syscall overhead is minimal.
In addition, the aio API allows you to do that in two calls for an iovec
of any size.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2006-05-21 12:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 15:53 ptrace enhancements for VM support (patch proposals follow in sep.msgs) Renzo Davoli
2006-05-18 15:56 ` [PATCH] 1-access_process_vm_user Renzo Davoli
2006-05-18 15:58 ` [PATCH] 2-ptrace_multi Renzo Davoli
2006-05-18 20:17 ` Andi Kleen
2006-05-18 21:13 ` Renzo Davoli
2006-05-19 2:23 ` Ulrich Drepper
2006-05-19 9:07 ` Renzo Davoli
2006-05-19 13:09 ` Daniel Jacobowitz
2006-05-19 17:45 ` Renzo Davoli
2006-05-19 19:15 ` Renzo Davoli
2006-05-19 20:15 ` Daniel Jacobowitz
2006-05-19 20:17 ` Andi Kleen
2006-05-20 6:44 ` Ulrich Drepper
2006-05-20 14:37 ` Alan Cox
2006-05-20 18:30 ` Renzo Davoli
2006-05-20 20:23 ` Ulrich Drepper
2006-05-20 21:39 ` Jeff Dike
2006-05-21 12:38 ` Avi Kivity [this message]
2006-05-21 15:28 ` Renzo Davoli
2006-05-22 13:02 ` Daniel Jacobowitz
2006-05-22 15:05 ` Renzo Davoli
2006-05-22 15:26 ` Daniel Jacobowitz
2006-05-18 16:07 ` [PATCH] 3-ptrace_vm Renzo Davoli
2006-05-21 8:03 ` ptrace enhancements for VM support (patch proposals follow in sep.msgs) Peter Chubb
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=44705F38.10905@argo.co.il \
--to=avi@argo.co.il \
--cc=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dan@debian.org \
--cc=drepper@gmail.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=osd@cs.unibo.it \
--cc=renzo@cs.unibo.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.