netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Daniel Lezcano <daniel.lezcano@free.fr>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>,
	"Julian Anastasov" <ja@ssi.bg>,
	"David Miller" <davem@davemloft.net>,
	"Linux Netdev List" <netdev@vger.kernel.org>
Subject: Re: getsockopt(TCP_DEFER_ACCEPT) value change
Date: Tue, 05 Jan 2010 17:14:23 +0100	[thread overview]
Message-ID: <4B43655F.5030807@gmail.com> (raw)
In-Reply-To: <4B435EB5.1010902@free.fr>

Le 05/01/2010 16:45, Daniel Lezcano a écrit :
  
> It's not problem if the set / get values are not same, but I was asking
> because I am working with a test suite checking if a checkpoint /
> restart solution is correct.  One of these tests, sets the
> TCP_DEFER_ACCEPT value to 12, checkpoints / restarts, and reads the
> value in order to check if it was correctly restored. The value 12 was
> chosen because it is not rounded, so we were able to safely do the test.
> But with the 2.6.32, the behaviour changed, so I preferred to report it
> in case that is something not expected.
> 
> 

12 happened to be rounded to 12 with previous kernels,
but with recent kernels we have another conversion table :

1 -> 3
2 -> 3
3 -> 3
4 -> 9
5 -> 9
6 -> 9
7 -> 9
8 -> 9
9 -> 9
10 -> 21
...
21 -> 21
22 -> 45
...
45 -> 45
46 -> 93
...
93 -> 93
94 -> 189
...
189 -> 189
190 -> 309
...

  reply	other threads:[~2010-01-05 16:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-05 10:42 getsockopt(TCP_DEFER_ACCEPT) value change Daniel Lezcano
2010-01-05 13:40 ` Ilpo Järvinen
2010-01-05 14:11   ` Eric Dumazet
2010-01-05 14:45     ` Eric Dumazet
2010-01-05 15:45     ` Daniel Lezcano
2010-01-05 16:14       ` Eric Dumazet [this message]
2010-01-05 16:57         ` Daniel Lezcano
2010-01-05 20:29   ` David Miller

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=4B43655F.5030807@gmail.com \
    --to=eric.dumazet@gmail.com \
    --cc=daniel.lezcano@free.fr \
    --cc=davem@davemloft.net \
    --cc=ilpo.jarvinen@helsinki.fi \
    --cc=ja@ssi.bg \
    --cc=netdev@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).