On Wed, Aug 23, 2017 at 1:08 AM, Akshat Kakkar wrote:
>
> On Tue, Aug 22, 2017 at 5:58 PM, Neal Cardwell wrote:
> > On Tue, Aug 22, 2017 at 1:42 AM, Akshat Kakkar
> > wrote:
> >> There are multiple hosts/clients. All are
On Tue, Aug 22, 2017 at 5:58 PM, Neal Cardwell wrote:
> On Tue, Aug 22, 2017 at 1:42 AM, Akshat Kakkar wrote:
>> There are multiple hosts/clients. All are mainly windows based.
>>
>> Timestamp is not used as my clients mainly are windows based and in
On Tue, 2017-08-22 at 10:46 -0700, David Ahern wrote:
> On 8/22/17 10:44 AM, Eric Dumazet wrote:
> > Willem wrote this doc in 2013, before we finally went back to 1000.
> >
> > We should update this doc.
>
>
> And these too:
>
> $ egrep -r netdev_max_backlog Documentation/networking/
>
On 8/22/17 10:44 AM, Eric Dumazet wrote:
> Willem wrote this doc in 2013, before we finally went back to 1000.
>
> We should update this doc.
And these too:
$ egrep -r netdev_max_backlog Documentation/networking/
Documentation/networking//cxgb.txt: sysctl -w
On Tue, 2017-08-22 at 09:43 -0700, David Ahern wrote:
> On 8/22/17 6:02 AM, Eric Dumazet wrote:
> >>
> >> net.core.netdev_max_backlog=1
> > This is an insane backlog.
> >
>
> https://www.kernel.org/doc/Documentation/networking/scaling.txt
>
> "== Suggested Configuration
>
> Flow limit is
On 8/22/17 6:02 AM, Eric Dumazet wrote:
>>
>> net.core.netdev_max_backlog=1
> This is an insane backlog.
>
https://www.kernel.org/doc/Documentation/networking/scaling.txt
"== Suggested Configuration
Flow limit is useful on systems with many concurrent connections,
where a single connection
On Tue, 2017-08-22 at 11:12 +0530, Akshat Kakkar wrote:
> There are multiple hosts/clients. All are mainly windows based.
>
> Timestamp is not used as my clients mainly are windows based and in
> that it tcp timestamp is by defauly disabled.
>
> sysctl is as follows:
>
> kernel.shmmax =
On Tue, Aug 22, 2017 at 1:42 AM, Akshat Kakkar wrote:
> There are multiple hosts/clients. All are mainly windows based.
>
> Timestamp is not used as my clients mainly are windows based and in
> that it tcp timestamp is by defauly disabled.
...
> net.ipv4.tcp_tw_reuse=1
>
On Tue, Aug 22, 2017 at 11:12 AM, Akshat Kakkar wrote:
> There are multiple hosts/clients. All are mainly windows based.
>
> Timestamp is not used as my clients mainly are windows based and in
> that it tcp timestamp is by defauly disabled.
>
> sysctl is as follows:
>
>
There are multiple hosts/clients. All are mainly windows based.
Timestamp is not used as my clients mainly are windows based and in
that it tcp timestamp is by defauly disabled.
sysctl is as follows:
kernel.shmmax = 68719476736
kernel.shmall = 4294967296
kernel.pid_max=4194303
On Mon, 2017-08-21 at 10:44 -0700, Eric Dumazet wrote:
> - Why is timewait not being used ?
>
s/timewait/timestamps/
On Mon, 2017-08-21 at 22:58 +0530, Akshat Kakkar wrote:
> As mentioned in my initial description, the server is not sending
> SYN-ACK. Thats what the main symptom. For completeness, its not
> sending any RST also.
> However, if I disable TCP timestamp ... the server starts giving SYN-ACK.
> The
On Monday, August 21, 2017, Eric Dumazet wrote:
>
> On Mon, 2017-08-21 at 15:26 +0530, Akshat Kakkar wrote:
> > On Mon, Aug 21, 2017 at 3:13 PM, David Laight
> > wrote:
> > > From: Akshat Kakkar
> > >> Sent: 18 August 2017 10:14
> > >> On Thu,
On Mon, 2017-08-21 at 15:26 +0530, Akshat Kakkar wrote:
> On Mon, Aug 21, 2017 at 3:13 PM, David Laight wrote:
> > From: Akshat Kakkar
> >> Sent: 18 August 2017 10:14
> >> On Thu, Aug 17, 2017 at 5:06 PM, Eric Dumazet
> >> wrote:
> >> > On Thu,
On Mon, Aug 21, 2017 at 5:56 AM, Akshat Kakkar wrote:
>
> The issue is with tcp timestamp. When I am disabling it, things are
> working fine but when I enable the issue re-occurs. However, I am not
> seeing tcp timestamps on packet, even when it is enabled simply
> because
On Mon, Aug 21, 2017 at 3:13 PM, David Laight wrote:
> From: Akshat Kakkar
>> Sent: 18 August 2017 10:14
>> On Thu, Aug 17, 2017 at 5:06 PM, Eric Dumazet wrote:
>> > On Thu, 2017-08-17 at 14:35 +0530, Akshat Kakkar wrote:
>> >
>> >> I upgraded to
From: Akshat Kakkar
> Sent: 18 August 2017 10:14
> On Thu, Aug 17, 2017 at 5:06 PM, Eric Dumazet wrote:
> > On Thu, 2017-08-17 at 14:35 +0530, Akshat Kakkar wrote:
> >
> >> I upgraded to 4.4 but still experiencing same issue.
> >> Please help.
> >
> > Still too old kernel,
On Fri, 2017-08-18 at 18:14 +0530, Akshat Kakkar wrote:
> On Fri, Aug 18, 2017 at 5:36 PM, Eric Dumazet wrote:
> > On Fri, 2017-08-18 at 14:44 +0530, Akshat Kakkar wrote:
> >> On Thu, Aug 17, 2017 at 5:06 PM, Eric Dumazet
> >> wrote:
> >> > On
On Fri, Aug 18, 2017 at 5:36 PM, Eric Dumazet wrote:
> On Fri, 2017-08-18 at 14:44 +0530, Akshat Kakkar wrote:
>> On Thu, Aug 17, 2017 at 5:06 PM, Eric Dumazet wrote:
>> > On Thu, 2017-08-17 at 14:35 +0530, Akshat Kakkar wrote:
>> >
>> >> I
On Fri, 2017-08-18 at 14:44 +0530, Akshat Kakkar wrote:
> On Thu, Aug 17, 2017 at 5:06 PM, Eric Dumazet wrote:
> > On Thu, 2017-08-17 at 14:35 +0530, Akshat Kakkar wrote:
> >
> >> I upgraded to 4.4 but still experiencing same issue.
> >> Please help.
> >
> > Still too old
On Thu, Aug 17, 2017 at 5:06 PM, Eric Dumazet wrote:
> On Thu, 2017-08-17 at 14:35 +0530, Akshat Kakkar wrote:
>
>> I upgraded to 4.4 but still experiencing same issue.
>> Please help.
>
> Still too old kernel, shoot again ;)
>
>
Sorry but that's the maximum I can try as
On Thu, 2017-08-17 at 14:35 +0530, Akshat Kakkar wrote:
> I upgraded to 4.4 but still experiencing same issue.
> Please help.
Still too old kernel, shoot again ;)
On Wed, Aug 16, 2017 at 4:04 PM, Eric Dumazet wrote:
> On Wed, 2017-08-16 at 10:18 +0530, Akshat Kakkar wrote:
>> On Mon, Aug 14, 2017 at 2:37 PM, Akshat Kakkar wrote:
>> > I have centos 7.3 (Kernel 3.10) running on a server with 128GB RAM and
>> >
On Wed, 2017-08-16 at 10:18 +0530, Akshat Kakkar wrote:
> On Mon, Aug 14, 2017 at 2:37 PM, Akshat Kakkar wrote:
> > I have centos 7.3 (Kernel 3.10) running on a server with 128GB RAM and
> > 2 x 10 Core Xeon Processor.
> > I have hosted a webserver on it and enabled ssh for
On Mon, Aug 14, 2017 at 2:37 PM, Akshat Kakkar wrote:
> I have centos 7.3 (Kernel 3.10) running on a server with 128GB RAM and
> 2 x 10 Core Xeon Processor.
> I have hosted a webserver on it and enabled ssh for remote maintenance.
> Previously it was running on Centos 6.3.
I have centos 7.3 (Kernel 3.10) running on a server with 128GB RAM and
2 x 10 Core Xeon Processor.
I have hosted a webserver on it and enabled ssh for remote maintenance.
Previously it was running on Centos 6.3.
After upgrading to CentOS 7.3, occasionally (probably when number of
hits are more on
26 matches
Mail list logo