| To: | Andi Kleen <ak@xxxxxxx> |
|---|---|
| Subject: | Re: [RFC] TCP Vegas for 2.6 |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Mon, 8 Mar 2004 15:31:22 -0800 |
| Cc: | shemminger@xxxxxxxx, ak@xxxxxxx, linux-net@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <20040308213646.GH26401@xxxxxxxxxxxxx> |
| References: | <20040308130454.0442c04d@xxxxxxxxxxxxxxxxxxxxx> <20040308212156.GE26401@xxxxxxxxxxxxx> <20040308133009.1e068199@xxxxxxxxxxxxxxxxxxxxx> <20040308213646.GH26401@xxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Mon, 8 Mar 2004 22:36:46 +0100 Andi Kleen <ak@xxxxxxx> wrote: > > 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. I explicitly removed the CONFIG_ options guarding the westwood stuff when I added it to the tree. I want people to use this stuff, and I don't want them to have to enable weird config options just to do so. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [RFC] TCP Vegas for 2.6, Andi Kleen |
|---|---|
| Next by Date: | Re: [RFC] TCP Vegas for 2.6, David S. Miller |
| Previous by Thread: | Re: [RFC] TCP Vegas for 2.6, Nivedita Singhvi |
| Next by Thread: | Cleaner way to conditionally disallow a CONFIG option as static, Sridhar Samudrala |
| Indexes: | [Date] [Thread] [Top] [All Lists] |