From: Astrid Jekat <hostmaster@cyberlab.de>
To: lartc@vger.kernel.org
Subject: [LARTC] lartc on dual CPU Opteron 64 bit machine?
Date: Tue, 14 Oct 2003 09:47:42 +0000 [thread overview]
Message-ID: <marc-lartc-106612699114959@msgid-missing> (raw)
Greetings, lartc experts! ;-)
I am presently researching if it is possible to *efficiently* use a machine
with 2 AMD Opteron CPUs for traffic shaping with lartc.
1) OS:
ATM it looks as if I can only use SUSE Linux 8 Enterprise Server for
AMD 64bit platforms.
Debian, OpenBSD and NetBSD are working on ports, but are not done yet or
still experimental.
Suse at least is stable (but costs real money! *sigh* so much for open source)
and has a 64bit compiler.
2) Is lartc 64bit capable?
I.e., can I compile lartc only to run as a 32 bit application or 64bit, too?
Any experience here?
3) Is lartc capable of making use of 2 CPUs?
This is probably a question (kernel?) threading.
I managed to find a reference in the ML archives that it might be
possible to "assign" ine CPU to one ethernet interface, but I don't
think this is quite what I need.
I'd like to know if the process can actually use both CPUs.
In a nutshell:
I need to find out if lartc can make use of the nice resources on
this dual Opteron 64bit machine.
If yes, this would save the machine from the terrible fate of becoming a
Windoze file server!
So please advise ;-)
Cheers,
--
Astrid Jekat
Fa. Secnetix
jekat@secnetix.de
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-10-14 9:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 9:47 Astrid Jekat [this message]
2003-10-17 15:22 ` [LARTC] lartc on dual CPU Opteron 64 bit machine? Debreczeni Peter
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=marc-lartc-106612699114959@msgid-missing \
--to=hostmaster@cyberlab.de \
--cc=lartc@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