grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Valentin Dornauer <valentin@unimplemented.org>
To: Andrey Borzenkov <arvidjaar@gmail.com>
Cc: grub-devel@gnu.org
Subject: Re: [PATCH] Avoid reusing the same TCP port number
Date: Tue, 13 Jan 2015 15:41:55 +0100	[thread overview]
Message-ID: <20150113144155.GA7598@unimplemented.org> (raw)
In-Reply-To: <20140703224125.2e8962fa@opensuse.site>

Hello Andrey,

On Thu, Jul 03, 2014 at 10:41:25PM +0400, Andrey Borzenkov wrote:
> May be you can simply use grub_get_time_ms()? After all, we are not
> interested in exact time, just in some pseudo-random distribution. It
> should have less overhead than grub_get_datetime(). 

I finally got around to trying out your suggestion concerning the
TCP source port "randomization". The main problem I see with using
the TSC's value instead of the current time of day (in seconds)
is that it will have approximately the same value every time the
machine is rebooted and reaches the point where the first file is
loaded. This means that clashes are way more likely than with the
RTC based solution, at least for the first file. Little or no network
jitter could mean even more collisions.

Do you think it's still worth the effort to change the previously
proposed [1] patch?

Thanks
Valentin

[1] http://lists.gnu.org/archive/html/grub-devel/2014-07/msg00000.html


      reply	other threads:[~2015-01-13 14:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-01 11:53 [PATCH] Avoid reusing the same TCP port number Valentin Dornauer
2014-07-03 18:41 ` Andrey Borzenkov
2015-01-13 14:41   ` Valentin Dornauer [this message]

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=20150113144155.GA7598@unimplemented.org \
    --to=valentin@unimplemented.org \
    --cc=arvidjaar@gmail.com \
    --cc=grub-devel@gnu.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).