From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: sparclinux@vger.kernel.org
Subject: Re: ixgbe/linux/sparc perf issues
Date: Fri, 12 Dec 2014 16:16:33 +0000 [thread overview]
Message-ID: <20141212161633.GA16340@oracle.com> (raw)
In-Reply-To: <20141211194542.GA5536@oracle.com>
On (12/11/14 15:27), David Miller wrote:
>
> BTW, Solaris also does things which are remotely exploitable, so
> these optimizations that get them "line rate" have a serious cost.
>
> In their NIU driver, the recycle all buffers in an RX queue rather
> than allocating new buffers.
>
> This means that a maliciously running TCP application can read a lot
> of data from a bulk sender, then simply stop reading completely.
Just to set the record straight, without digressing too much into
Solaris internals..
Solaris follows the common practice used in such algorithms
of having thresholds on the number of loaned ("recycled") buffers for
this sort of thing, to avoid DoS attacks from malicious applications.
When that threshold is crossed, the driver falls back to the slower
"allocate new buffers" path, so there is no stalling.
But getting back to linux, 3 Gbps is a far cry from 10 Gbps.
I need to spend some time collecting data to convince myself that
this is purely because of HV/IOMMU inefficiency.
Thanks,
--Sowmini
next prev parent reply other threads:[~2014-12-12 16:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 19:45 ixgbe/linux/sparc perf issues Sowmini Varadhan
2014-12-11 20:09 ` David Miller
2014-12-11 20:21 ` Sowmini Varadhan
2014-12-11 20:24 ` David Miller
2014-12-11 20:27 ` David Miller
2014-12-12 16:16 ` Sowmini Varadhan [this message]
2014-12-19 15:11 ` Sowmini Varadhan
2014-12-19 17:10 ` David Miller
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=20141212161633.GA16340@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=sparclinux@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.