RE: [patch 1/4] - Potential performance bottleneck for Linxu TCP

>The solution is really simple and needs no kernel change at all: if you
>want the TCP receiver to get a larger share of timeslices then either
>renice it to -20 or renice the other tasks to +19.

Simply give a larger share of timeslices to the TCP receiver won't solve the
problem.  No matter what the timeslice is, if the TCP receiving process has
packets within backlog, and the process is expired and moved to the expired
array, RTO might happen in the TCP sender.

The solution does not look like that simple.

wenji




-
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: [patch 1/4] - Potential performance bottleneck for Linxu TCP
    • From: Ingo Molnar <[email protected]>

• References:
  • Re: [patch 1/4] - Potential performance bottleneck for Linxu TCP
    • From: Ingo Molnar <[email protected]>

• Prev by Date: [PATCH] don't do orphan processing on readonly devices
• Next by Date: Re: [RFC, PATCH 1/2] qrcu: "quick" srcu implementation
• Previous by thread: Re: [patch 1/4] - Potential performance bottleneck for Linxu TCP
• Next by thread: Re: [patch 1/4] - Potential performance bottleneck for Linxu TCP
• 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]