From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] Huge latency issue with 8.2.6
Date: Sat, 16 Aug 2008 18:55:18 +0200 [thread overview]
Message-ID: <20080816165518.GA15331@racke> (raw)
In-Reply-To: <DA0E7D869C862D4095C265233CD1D41EEE9B7D@EXNA.corp.stratus.com>
On Sat, Aug 16, 2008 at 12:44:33PM -0400, Graham, Simon wrote:
> > > Conclusion 2 -- the problem here has to do with the time is takes
> > > the secondary to send the TCP ACK.
> >
> > in git on the way to 8.2.7, we added the TCP_NODELAY socket option,
> >
>
> I saw that and it's goodness BUT this controls the Nagle algorithm and
> NOT the Ack Delay timer - you need (I believe) TCP_QUICKACK as well (or
> a global change on the connection to lower the ack delay but I think
> that would be bad - the nice thing about TCP_QUICKACK is that it's a one
> time setting that causes pending acks to be sent right now but does not
> change the normal ack delay).
I had the impression that the NODELAY would imply QUICKACK behaviour,
and together witht the CORK and UNCORK should do the trick.
but I'm happy to be enlightened.
will commit a slightly modified verion of your quickack soonish.
thanks,
--
: Lars Ellenberg
: LINBIT HA-Solutions GmbH
: DRBD®/HA support and consulting http://www.linbit.com
DRBD® and LINBIT® are registered trademarks
of LINBIT Information Technologies GmbH
__
please don't Cc me, but send to list -- I'm subscribed
next prev parent reply other threads:[~2008-08-16 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 16:31 [Drbd-dev] Huge latency issue with 8.2.6 Graham, Simon
2008-08-16 15:22 ` Lars Ellenberg
2008-08-16 16:44 ` Graham, Simon
2008-08-16 16:55 ` Lars Ellenberg [this message]
[not found] ` <DA0E7D869C862D4095C265233CD1D41EEE9B7D@EXNA.corp.strat us.com>
2008-08-16 19:35 ` Graham, Simon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080816165518.GA15331@racke \
--to=lars.ellenberg@linbit.com \
--cc=drbd-dev@lists.linbit.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox