From: Stefan Hajnoczi <stefanha@gmail.com>
To: Vincenzo Maffione <v.maffione@gmail.com>
Cc: aliguori@us.ibm.com, mst@redhat.com, lersek@redhat.com,
jasowang@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com,
pbonzini@redhat.com, g.lettieri@iet.unipi.it, rizzo@iet.unipi.it,
afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH v6] e1000: add interrupt mitigation support
Date: Tue, 6 Aug 2013 10:21:55 +0200 [thread overview]
Message-ID: <20130806082155.GA32024@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1375461052-2476-1-git-send-email-v.maffione@gmail.com>
On Fri, Aug 02, 2013 at 06:30:52PM +0200, Vincenzo Maffione wrote:
> This patch partially implements the e1000 interrupt mitigation mechanisms.
> Using a single QEMUTimer, it emulates the ITR register (which is the newer
> mitigation register, recommended by Intel) and approximately emulates
> RADV and TADV registers. TIDV and RDTR register functionalities are not
> emulated (RDTR is only used to validate RADV, according to the e1000 specs).
>
> RADV, TADV, TIDV and RDTR registers make up the older e1000 mitigation
> mechanism and would need a timer each to be completely emulated. However,
> a single timer has been used in order to reach a good compromise between
> emulation accuracy and simplicity/efficiency.
>
> The implemented mechanism can be enabled/disabled specifying the command
> line e1000-specific boolean parameter "mitigation", e.g.
>
> qemu-system-x86_64 -device e1000,mitigation=on,... ...
>
> For more information, see the Software developer's manual at
> http://download.intel.com/design/network/manuals/8254x_GBe_SDM.pdf.
>
> Interrupt mitigation boosts performance when the guest suffers from
> an high interrupt rate (i.e. receiving short UDP packets at high packet
> rate). For some numerical results see the following link
> http://info.iet.unipi.it/~luigi/papers/20130520-rizzo-vm.pdf
>
> Signed-off-by: Vincenzo Maffione <v.maffione@gmail.com>
> ---
> Added pc-*-1.7 machines (default machine moved to pc-i440fx-1.7).
>
> hw/i386/pc_piix.c | 18 ++++++-
> hw/i386/pc_q35.c | 16 ++++++-
> hw/net/e1000.c | 131 +++++++++++++++++++++++++++++++++++++++++++++++++--
> include/hw/i386/pc.h | 8 ++++
> 4 files changed, 167 insertions(+), 6 deletions(-)
Great, thanks for working with us on the migration details, Vincenzo!
Thanks, applied to my net-next tree:
https://github.com/stefanha/qemu/commits/net-next
Stefan
next prev parent reply other threads:[~2013-08-06 8:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 16:30 [Qemu-devel] [PATCH v6] e1000: add interrupt mitigation support Vincenzo Maffione
2013-08-05 9:25 ` Stefan Hajnoczi
2013-08-05 9:27 ` Stefan Hajnoczi
2013-08-05 9:39 ` Andreas Färber
2013-08-06 8:21 ` Stefan Hajnoczi [this message]
2013-08-06 10:11 ` Vincenzo Maffione
2014-03-31 7:52 ` Alexey Kardashevskiy
2014-04-01 6:21 ` Alexey Kardashevskiy
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=20130806082155.GA32024@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=g.lettieri@iet.unipi.it \
--cc=jasowang@redhat.com \
--cc=lersek@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rizzo@iet.unipi.it \
--cc=stefanha@redhat.com \
--cc=v.maffione@gmail.com \
/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).