From: Shmulik Ladkani <shmulik.ladkani@ravellosystems.com>
To: Sameeh Jubran <sameeh@daynix.com>
Cc: qemu-devel@nongnu.org, Jason Wang <jasowang@redhat.com>,
Dmitry Fleytman <dmitry@daynix.com>,
Yan Vugenfirer <yan@daynix.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] e1000: Fixing interrupts pace.
Date: Wed, 4 May 2016 14:34:59 +0300 [thread overview]
Message-ID: <20160504143459.69178f46@pixies> (raw)
In-Reply-To: <1458200278-11940-2-git-send-email-sameeh@daynix.com>
Hi Sameeh,
On Thu, 17 Mar 2016 09:37:57 +0200, sameeh@daynix.com wrote:
> @@ -357,6 +357,14 @@ set_interrupt_cause(E1000State *s, int index, uint32_t val)
> }
> mit_update_delay(&mit_delay, s->mac_reg[ITR]);
>
> + /*
> + * According to e1000 SPEC, the Ethernet controller guarantees
> + * a maximum observable interrupt rate of 7813 interrupts/sec.
> + * Thus if mit_delay < 500 then the delay should be set to the
> + * minimum delay possible which is 500.
> + */
> + mit_delay = (mit_delay < 500) ? 500 : mit_delay;
> +
> if (mit_delay) {
> s->mit_timer_on = 1;
> timer_mod(s->mit_timer, qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL) +
Sorry for late response.
Formerly, 'mit_delay' could possibly be 0 (as being not updated by
any of the mit_update_delay calls), thus 'mit_timer' wouldn't be
armed.
The new logic forces mit_delay to be set to 500, even if it was 0
("unset").
Which approach is correct:
- Either the 'if (mit_delay)' is now superflous,
- Or, do we need to keep the "unset" sematics (i.e. mit_delay==0 means
don't use the timer)
Regards,
Shmulik
next prev parent reply other threads:[~2016-05-04 11:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 7:37 [Qemu-devel] [PATCH 0/2] e1000: Introducing an upper bound of interrupts Sameeh Jubran
2016-03-17 7:37 ` [Qemu-devel] [PATCH 1/2] e1000: Fixing interrupts pace Sameeh Jubran
2016-05-04 11:34 ` Shmulik Ladkani [this message]
2016-05-16 5:58 ` Sameeh Jubran
2016-05-16 10:55 ` Shmulik Ladkani
2016-05-17 18:26 ` Sameeh Jubran
2016-03-17 7:37 ` [Qemu-devel] [PATCH 2/2] Revert "e1000: fix hang of win2k12 shutdown with flood ping" Sameeh Jubran
2016-03-17 19:51 ` [Qemu-devel] [PATCH 0/2] e1000: Introducing an upper bound of interrupts Denis V. Lunev
2016-03-18 1:34 ` Jason Wang
2016-03-21 8:25 ` Sameeh Jubran
2016-03-22 11:23 ` Michael S. Tsirkin
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=20160504143459.69178f46@pixies \
--to=shmulik.ladkani@ravellosystems.com \
--cc=dmitry@daynix.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sameeh@daynix.com \
--cc=yan@daynix.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 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.