netdev - Re: [PATCH -mm] [RFC] I/OAT: Handle incoming udp through ioatdma

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1196379815.4450.2.camel@localhost>
Date:	Thu, 29 Nov 2007 18:43:35 -0500
From:	jamal <hadi@...erus.ca>
To:	"Nelson, Shannon" <shannon.nelson@...el.com>
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH -mm] [RFC] I/OAT: Handle incoming udp through ioatdma

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@...el.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

-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html