| To: | Stephen Hemminger <shemminger@xxxxxxxx> |
|---|---|
| Subject: | Re: [RFC] TCP Vegas for 2.6 |
| From: | Andi Kleen <ak@xxxxxxx> |
| Date: | Mon, 8 Mar 2004 22:36:46 +0100 |
| Cc: | Andi Kleen <ak@xxxxxxx>, linux-net <linux-net@xxxxxxxxxxxxxxx>, netdev@xxxxxxxxxxx |
| In-reply-to: | <20040308133009.1e068199@dell_ss3.pdx.osdl.net> |
| References: | <20040308130454.0442c04d@dell_ss3.pdx.osdl.net> <20040308212156.GE26401@wotan.suse.de> <20040308133009.1e068199@dell_ss3.pdx.osdl.net> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
> CONFIG options are of no use vendors who need to ship binary kernels. I can well see a vendor trading scalability for experimental non standard TCP algorithms that tend to be disabled anyways. Or allocating separately if you prefer that. In theory it may be even possible to change the slab cache size at runtime, but that could get tricky. -Andi |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [RFC] TCP Vegas for 2.6, Stephen Hemminger |
|---|---|
| Next by Date: | Re: [RFC] TCP Vegas for 2.6, Stephen Hemminger |
| Previous by Thread: | Re: [RFC] TCP Vegas for 2.6, Stephen Hemminger |
| Next by Thread: | Re: [RFC] TCP Vegas for 2.6, Stephen Hemminger |
| Indexes: | [Date] [Thread] [Top] [All Lists] |