From: "George Spelvin" <linux@horizon.com>
To: linux@horizon.com, w@1wt.eu
Cc: dan@doxpara.com, davem@davemloft.net, gerrit@erg.abdn.ac.uk,
herbert@gondor.hengli.com.au, linux-kernel@vger.kernel.org,
mpm@selenic.com, netdev@vger.kernel.org
Subject: Re: [PATCH 0/2] Improve sequence number generation.
Date: 20 Aug 2011 23:04:15 -0400 [thread overview]
Message-ID: <20110821030415.18106.qmail@science.horizon.com> (raw)
In-Reply-To: <20110821012844.GA15222@1wt.eu>
>> * Should I worry about 32-bit IPv6 performance, since that's even more
>> unlikely to be running heavy loads on 32-bit hardware?
> On x86 you're probably right, but there are other very fast platforms
> such as ARM, which are used to build routers or appliances, and which
> are 32-bit and there it may matter.
Thanks for the feedback. Your point about routers is well-taken.
It's particularly x86-32 which gives me fits, but I'll keep ARM
performance in mind, too.
>> * If yes, is this fast enough to be acceptable, or do I need to work
>> harder to find more speed?
> I'd suggest that the most important is no performance regression. Probably
> that if you can bring something which brings back what we lost with MD5,
> your work would gain interest.
Okay, I'll go back to the drawing board on performance.
Damn, this is going to be tough.
> I'm copy-pasting here the memo I exchanged in private after my tests, there
> is nothing secret in it, so better post the whole explanation :
Thank you very much. It helps me figure out what the time budget is.
next prev parent reply other threads:[~2011-08-21 3:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110816.021031.1778295949152117484.davem@davemloft.net>
2011-08-16 10:30 ` get_random_int() should use hash[1] George Spelvin
2011-08-20 23:39 ` [PATCH 0/2] Improve sequence number generation George Spelvin
2011-08-20 23:44 ` David Miller
2011-08-21 0:49 ` George Spelvin
2011-08-21 1:28 ` Willy Tarreau
2011-08-21 3:04 ` George Spelvin [this message]
2011-08-21 3:27 ` Ted Ts'o
2011-08-21 4:02 ` Herbert Xu
2011-08-22 2:06 ` George Spelvin
2011-08-07 1:50 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=20110821030415.18106.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=dan@doxpara.com \
--cc=davem@davemloft.net \
--cc=gerrit@erg.abdn.ac.uk \
--cc=herbert@gondor.hengli.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=netdev@vger.kernel.org \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®