From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Raghava Raju <vraghava_raju@yahoo.com>
Cc: arjanv@redhat.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: delegating to a cpu
Date: 30 Jun 2003 21:55:25 +0100 [thread overview]
Message-ID: <1057006524.17589.35.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030630200949.96698.qmail@web20003.mail.yahoo.com>
Unless your other work is really expensive its doubtful another CPU will
help you. If it is then probably you want to have threads that you pin
to each CPU (with the cpu affinity calls) and wake. You do want to work
hard to keep the same data being needed on both CPUs however
prev parent reply other threads:[~2003-06-30 20:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-29 15:34 Raghava Raju
2003-06-29 15:47 ` Arjan van de Ven
2003-06-30 20:09 ` Raghava Raju
2003-06-30 20:55 ` Alan Cox [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=1057006524.17589.35.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vraghava_raju@yahoo.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
all inboxes | Powered by JetHome®