Hi Stefan, then you should probably describe this in a short mail to Jason Wang and ask him how to circumvent this commit with sysctl settings. I´m pretty sure my sysctl setting reverts the first part of the commit. So probably the second part is the evil one ?
Greetings Stefan On Thu, May 31, 2012 at 10:04 AM, Stefan Priebe - Profihost AG <s.pri...@profihost.ag> wrote: > > Am 31.05.2012 09:27, schrieb Stefan Majer: > > we have set them in /etc/sysctl.conf to: > > net.ipv4.tcp_mem = 10000000 10000000 10000000 > > This does not help ;-( > > > wow, this was fast ! > > if i understand this commit correct it simply skips a in-kernel > > configuration of network related sysctl parameters, especialy > > net.ipv4.tcp_mem > > I also tied this one: > net.ipv4.tcp_rmem = 4096 524287 16777216 > net.ipv4.tcp_wmem = 4096 524287 16777216 > # grabbed values from 3.0.X > net.ipv4.tcp_mem = 1162962 1550617 2325924 > > still - no help -. But if i use 3.4 and revert the commit it works fine. > But i wasn't able to find which other parts are influenced by this limit > while browsing through the source. > > I only found: > net.ipv4.tcp_mem > and > net.ipv4.tcp_rmem > and > net.ipv4.tcp_wmem > > Greets > Stefan -- Stefan Majer -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
