Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 619001

Summary:	It sometimes takes 3 seconds to connect to a TCP server [rhel-6.0]
Product:	Red Hat Enterprise Linux 6	Reporter:	Eryu Guan <eguan>
Component:	kernel	Assignee:	Thomas Graf <tgraf>
Status:	CLOSED NOTABUG	QA Contact:	Network QE <network-qe>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	6.0	CC:	bzeranski, dhoward, fskola, jwest, kzhang, mgoodwin, mmilgram, pep, plyons, rkhan, spoyarek, syeghiay, tao
Target Milestone:	rc	Keywords:	RHELNAK, TestOnly
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	518651	Environment:
Last Closed:	2011-03-09 08:44:58 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:
Bug Depends On:	518651
Bug Blocks:	525215, 645454

Comment 3 RHEL Program Management 2010-07-28 10:57:55 UTC

This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

Comment 22 Thomas Graf 2011-03-09 08:44:58 UTC

The difference in behaviour of RHEL5 and RHEL6 was caused by commit:

commit 2bba22c50b06abe9fd0d23933b1e64d35b419262
Author: Mike Galbraith <efault>
Date:   Wed Sep 9 15:41:37 2009 +0200

    sched: Turn off child_runs_first

    Set child_runs_first default to off.

    It hurts 'optimal' make -j<NR_CPUS> workloads as make jobs
    get preempted by child tasks, reducing parallelism.
    [...]

With child_runs_first it takes longer for the backlog of the listening socket to fill.

Still, this is an application bug. The reason for some packets being dropped is that the backlog limit is reached. Applications increasing their backlog limit from the traditional limit of 128 to something that fits modern architectures will no longer be affected by this issue.