From: David Miller <davem@davemloft.net>
To: netdev@axxeo.de
Cc: woodard@redhat.com, netdev@vger.kernel.org, mgrondona@llnl.gov,
behlendorf1@llnl.gov
Subject: Re: [PATCH] Customizable TCP backoff patch
Date: Wed, 04 Oct 2006 02:08:06 -0700 (PDT) [thread overview]
Message-ID: <20061004.020806.41635871.davem@davemloft.net> (raw)
In-Reply-To: <200610041056.12704.netdev@axxeo.de>
From: Ingo Oeser <netdev@axxeo.de>
Date: Wed, 4 Oct 2006 10:56:12 +0200
> David Miller wrote:
> > At the very least, seconds might not be fine enough granularity
> > for some circumstances. Heck, the default RTO_MIN is 1/5 of a
> > second. :-)
> >
> > I also understand that going to milliseconds or microseconds would
> > make the size of the in-socket struct members an issue again. These
> > things are never easy are they? :-/
>
> Would be, if floating point values would be allowed. Single precision would
> be enough in this case and its just 32 bits IIRC.
>
> I mean floating point values just for the user->kernel ABI and
> NOT for the internal timer representation.
We got the struct members down to 16-bits each, the problem is in
fact that we'd need to make them 32-bits again.
next prev parent reply other threads:[~2006-10-04 9:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 18:52 [PATCH] Customizable TCP backoff patch Ben Woodard
2006-09-27 23:16 ` David Miller
2006-09-27 23:00 ` Stephen Hemminger
2006-09-28 2:06 ` David Miller
2006-10-03 18:14 ` Ben Woodard
2006-10-04 7:07 ` David Miller
2006-10-04 8:56 ` Ingo Oeser
2006-10-04 9:08 ` David Miller [this message]
2006-10-04 17:17 ` Stephen Hemminger
2006-10-11 1:46 ` Ben Woodard
2006-10-11 1:59 ` YOSHIFUJI Hideaki / 吉藤英明
2006-10-11 2:53 ` David Miller
2006-10-11 2:54 ` David Miller
2006-10-11 14:01 ` Vlad Yasevich
2006-10-12 0:51 ` Ben Woodard
2006-10-12 1:06 ` YOSHIFUJI Hideaki / 吉藤英明
2006-10-12 15:49 ` Ben Woodard
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=20061004.020806.41635871.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=behlendorf1@llnl.gov \
--cc=mgrondona@llnl.gov \
--cc=netdev@axxeo.de \
--cc=netdev@vger.kernel.org \
--cc=woodard@redhat.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;
as well as URLs for NNTP newsgroup(s).