From: jamal <hadi@cyberus.ca>
To: "Nelson, Shannon" <shannon.nelson@intel.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH -mm] [RFC] I/OAT: Handle incoming udp through ioatdma
Date: Thu, 29 Nov 2007 18:43:35 -0500 [thread overview]
Message-ID: <1196379815.4450.2.camel@localhost> (raw)
In-Reply-To: <BAE9DCEF64577A439B3A37F36F9B691C03853146@orsmsx418.amr.corp.intel.com>
On Thu, 2007-29-11 at 12:08 -0800, Nelson, Shannon wrote:
> [RFC] I/OAT: Handle incoming udp through ioatdma
>
> From: Shannon Nelson <shannon.nelson@intel.com>
>
> If the incoming udp packet is larger than sysctl_udp_dma_copybreak, try
> pushing it through the ioatdma asynchronous memcpy. This is very much
> the
> same as the tcp copy offload. This is an RFC because we know there are
> stability problems under high traffic.
What stability problems?
Is there some magic sysctl_udp_dma_copybreak threshold value where you
start seeing the benefit of IOAT-ing? Since you mentioned
"students"<evil grin here>, it would be interesting to see data where
udp starts benefitting.
cheers,
jamal
next prev parent reply other threads:[~2007-11-29 23:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 20:08 [PATCH -mm] [RFC] I/OAT: Handle incoming udp through ioatdma Nelson, Shannon
2007-11-29 20:17 ` Shannon Nelson
2007-11-29 23:43 ` jamal [this message]
2007-11-30 1:27 ` Nelson, Shannon
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=1196379815.4450.2.camel@localhost \
--to=hadi@cyberus.ca \
--cc=netdev@vger.kernel.org \
--cc=shannon.nelson@intel.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.