From: Tim Mattox <tmattox@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: davem@redhat.com, hadi@cyberus.ca, netdev@oss.sgi.com
Subject: Re: [RFC,PATCH] fastroute dead code...
Date: Fri, 30 Jul 2004 15:29:25 -0400 [thread overview]
Message-ID: <ea86ce220407301229522be64f@mail.gmail.com> (raw)
In-Reply-To: <20040730060348.GA22854@havoc.gtf.org>
I looked into fastroute about a year ago as well. It's been used in
some clusters
AFAIK, but I'm not sure if it's still being actively used. I was
considering trying to
use it myself in some cluster FNN research work I'm doing. But that's probably
still 6 months away if I get to it. Since I'd be having to patch
other things anyway,
I have no qualms with it going away from mainline... Especially with GigE so
cheap today, and legacy PCI bandwidths so low, it's not particularly economical
today to route through nodes in an HPC cluster that uses TCP/IP interconnect.
I don't know if the webserver/load balancing community would mind it going
away though.
On Fri, 30 Jul 2004 02:03:48 -0400, Jeff Garzik <jgarzik@pobox.com> wrote:
[snip]
> This actually does something, dependent upon options from the packet
> socket, so I left it alone. The rest was dead code.
>
> If nobody objects I can push to David, but right now this is more
> an RFC than a merge request for David.
[snip]
--
Tim Mattox - tmattox@gmail.com - http://homepage.mac.com/tmattox/
next prev parent reply other threads:[~2004-07-30 19:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-30 6:03 [RFC,PATCH] fastroute dead code Jeff Garzik
2004-07-30 19:29 ` Tim Mattox [this message]
2004-07-30 19:35 ` Jeff Garzik
2004-07-30 20:10 ` David S. Miller
2004-07-30 20:27 ` jamal
2004-07-30 21:11 ` Jeff Garzik
2004-08-02 11:45 ` Andi Kleen
2004-07-30 20:29 ` Tim Mattox
2004-07-30 21:08 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2004-07-30 20:31 Manish Lachwani
2004-07-30 21:05 ` jamal
2004-08-02 15:26 ` Kumar Gala
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=ea86ce220407301229522be64f@mail.gmail.com \
--to=tmattox@gmail.com \
--cc=davem@redhat.com \
--cc=hadi@cyberus.ca \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.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).