Thus spake Rick Jones ([email protected]): > Past performance is no guarantee of current correctness :) And over an > Ethernet, there will be a very different set of both timings and TCP > segment sizes compared to loopback. > My guess is that you will find setting the lo mtu to 1500 a very > interesting experiment. Setting the MTU on lo to 1500 eliminates the problem and gives me double digit MB/sec throughput. 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]>
- Re: bizarre network timing problem
- References:
- bizarre network timing problem
- From: Felix von Leitner <[email protected]>
- Re: bizarre network timing problem
- From: Chuck Ebbert <[email protected]>
- Re: bizarre network timing problem
- From: Felix von Leitner <[email protected]>
- Re: bizarre network timing problem
- From: Rick Jones <[email protected]>
- Re: bizarre network timing problem
- From: Felix von Leitner <[email protected]>
- Re: bizarre network timing problem
- From: Rick Jones <[email protected]>
- Re: bizarre network timing problem
- From: Felix von Leitner <[email protected]>
- Re: bizarre network timing problem
- From: Rick Jones <[email protected]>
- Re: bizarre network timing problem
- From: Felix von Leitner <[email protected]>
- Re: bizarre network timing problem
- From: Rick Jones <[email protected]>
- bizarre network timing problem
- Prev by Date: Re: 2.6.24-rc1-54866f032307063776b4eff7eadb131d47f9f9b4 fails to boot: kernel BUG at include/linux/scatterlist.h:49!
- Next by Date: Re: Suspend to ram regression (2.6.24-rc1-git)
- Previous by thread: Re: bizarre network timing problem
- Next by thread: Re: bizarre network timing problem
- Index(es):
 |