From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: Raghuram Kothakota <Raghuram.Kothakota@oracle.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 2/2] sunvnet: Re-check for a VIO_DESC_READY data descriptor after short udelay()
Date: Tue, 2 Sep 2014 12:56:59 -0400 [thread overview]
Message-ID: <20140902165659.GH31516@oracle.com> (raw)
In-Reply-To: <665366D4-384B-45E1-B371-239EA87F5A15@oracle.com>
On (09/02/14 09:43), Raghuram Kothakota wrote:
> We could optimize this a bit by not wait for normal traffic, I mean,
> non-burst traffic
> and apply the retry only when we detect a stream of packets?
How could you tell the difference efficiently? You'd need to
track some kind of history/state for inter-packet arrival time.
All seems like over-kill (more useful to go and optimize other
parts of the system, such as do less work in interrupt context).
> We could detect a stream based on how many packets are picked
> up in this function, picking up 3 or more could be considered as a stream,
> of course tune based on testing.
>
> You probably tried it already, but checking to see if you tried with
> less number
> of iterations, we could reduce the iterations if the numbers are equally good
> with less iterations.
yes, the 3 * 4 micro-seconds was arrived at heuristically.
--Sowmini
next prev parent reply other threads:[~2014-09-02 16:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 20:18 [PATCH net-next 2/2] sunvnet: Re-check for a VIO_DESC_READY data descriptor after short udelay() Sowmini Varadhan
2014-09-02 3:47 ` David Miller
2014-09-02 10:27 ` Sowmini Varadhan
2014-09-02 16:43 ` Raghuram Kothakota
2014-09-02 16:56 ` Sowmini Varadhan [this message]
2014-09-02 17:33 ` Raghuram Kothakota
2014-09-02 20:59 ` David Miller
2014-09-03 17:12 ` Sowmini Varadhan
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=20140902165659.GH31516@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=Raghuram.Kothakota@oracle.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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 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.