Re: bizarre network timing problem

Thus spake Chuck Ebbert ([email protected]):
> > Any ideas what could cause this?
> (cc: netdev)

Maybe I should mention this, too:

accept(5, {sa_family=AF_INET6, sin6_port=htons(59821), inet_pton(AF_INET6, "::ffff:127.0.0.1", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, [18446744069414584348]) = 8
setsockopt(8, SOL_TCP, TCP_NODELAY, [1], 4) = 0

And if it would be the Nagle algorithm, it should also impact the
ethernet case.

Felix
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: bizarre network timing problem
    • From: Rick Jones <[email protected]>

• References:
  • bizarre network timing problem
    • From: Felix von Leitner <[email protected]>
  • Re: bizarre network timing problem
    • From: Chuck Ebbert <[email protected]>

• Prev by Date: [PATCH] pfkey: sending an SADB_GET responds with an SADB_GET
• Next by Date: Re: [PATCH 0/4] Fix PCIe hotplug for non-ACPI ExpressCard slots (version 2)
• Previous by thread: Re: bizarre network timing problem
• Next by thread: Re: bizarre network timing problem
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]