From: David Miller <davem@davemloft.net>
To: shemminger@vyatta.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 2/2] pktgen: better scheduler friendliness
Date: Thu, 24 Sep 2009 15:44:53 -0700 (PDT) [thread overview]
Message-ID: <20090924.154453.230710626.davem@davemloft.net> (raw)
In-Reply-To: <20090923054201.520300835@vyatta.com>
From: Stephen Hemminger <shemminger@vyatta.com>
Date: Tue, 22 Sep 2009 22:41:43 -0700
> Previous update did not resched in inner loop causing watchdogs.
> Rewrite inner loop to:
> * account for delays better with less clock calls
> * more accurate timing of delay:
> - only delay if packet was successfully sent
> - if delay is 100ns and it takes 10ns to build packet then
> account for that
> * use wait_event_interruptible_timeout rather than open coding it.
>
> Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
Applied.
prev parent reply other threads:[~2009-09-24 22:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090923054141.932043798@vyatta.com>
2009-09-23 5:41 ` [PATCH 1/2] pktgen: T_TERMINATE flag is unused Stephen Hemminger
2009-09-24 22:44 ` David Miller
2009-09-23 5:41 ` [PATCH 2/2] pktgen: better scheduler friendliness Stephen Hemminger
2009-09-24 22:44 ` David Miller [this message]
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=20090924.154453.230710626.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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).