From: "David Boreham" <david_list@boreham.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] SMP in regards to routing/filtering
Date: Tue, 03 Sep 2002 14:11:29 +0000 [thread overview]
Message-ID: <marc-lartc-103106236515760@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103076253625864@msgid-missing>
> > Just wondering if it's worth grabbing an extra processor for the box, or
if
> > it will largely go unused.
It is also possible that two processors will be _slower_ than one,
due to contention. So it will be worthwhile to test with one CPU
disabled (UP kernel) just to see what happens.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-09-03 14:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-31 2:55 [LARTC] SMP in regards to routing/filtering Phil Doroff
2002-08-31 11:55 ` bert hubert
2002-09-03 14:11 ` David Boreham [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=marc-lartc-103106236515760@msgid-missing \
--to=david_list@boreham.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.