From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Anthony Liguori <aliguori@us.ibm.com>,
"Edgar E. Iglesias" <edgar.iglesias@axis.com>
Subject: Re: [Qemu-devel] [PATCH][RFT] Make DMA timer driven
Date: Fri, 24 Oct 2008 00:13:49 +0100 [thread overview]
Message-ID: <200810240013.50522.paul@codesourcery.com> (raw)
In-Reply-To: <20081023220453.GA15547@edgar.se.axis.com>
> You can find info regarding CRIS/ETRAX testing here:
> http://lists.gnu.org/archive/html/qemu-devel/2008-09/msg00279.html
>
> I tested the patch. It works but unfortunately DMA transfers to/from
> the ethernet block now seem to emulate very slowly.
Is there a reason you're deferring the DMA transfers, rather than completing
them immediately? In most cases you want to do the DMA as soon as both ends
are ready, and there's no benefit artificially delaying things. Any delay is
entirely arbitrary, and won't work reliably.
Paul
next prev parent reply other threads:[~2008-10-23 23:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 21:30 [Qemu-devel] [PATCH][RFT] Make DMA timer driven Anthony Liguori
2008-10-23 22:04 ` Edgar E. Iglesias
2008-10-23 23:13 ` Paul Brook [this message]
2008-10-24 9:22 ` Edgar E. Iglesias
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=200810240013.50522.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=aliguori@us.ibm.com \
--cc=edgar.iglesias@axis.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).