Bug 166491

Summary:	TCP_NODELAY/TCP_CORK regression since 2.4
Product:	Red Hat Enterprise Linux 4	Reporter:	Joe Orton <jorton>
Component:	kernel	Assignee:	David Miller <davem>
Status:	CLOSED WONTFIX	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0	CC:	jbaron, wtc
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-20 13:18:39 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Joe Orton 2005-08-22 14:34:13 UTC

Description of problem:
If TCP_NODELAY was previously set to 1 on the socket, setting TCP_CORK does not
inhibit the kernel from sending partial frames; even if TCP_NODELAY was actually
set to 0 at the time TCP_CORK was enabled.  This is a regression since 2.4 and
impacts httpd network performance.

Version-Release number of selected component (if applicable):
2.6.9-16.ELsmp

How reproducible:
I'll attach the test case.

Comment 3 Jiri Pallich 2012-06-20 13:18:39 UTC

Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.