From: Andi Kleen <andi@firstfloor.org>
To: "Zou, Yi" <yi.zou@intel.com>
Cc: Andi Kleen <andi@firstfloor.org>,
"Love, Robert W" <robert.w.love@intel.com>,
"james.bottomley@hansenpartnership.com"
<james.bottomley@hansenpartnership.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"jgarzik@redhat.com" <jgarzik@redhat.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"james.smart@emulex.com" <james.smart@emulex.com>,
"michaelc@cs.wisc.edu" <michaelc@cs.wisc.edu>,
"jeykholt@cisco.com" <jeykholt@cisco.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>
Subject: Re: [PATCH 2/3] libfc: A modular Fibre Channel library
Date: Fri, 12 Dec 2008 00:33:26 +0100 [thread overview]
Message-ID: <20081211233326.GD25779@one.firstfloor.org> (raw)
In-Reply-To: <7C88852EF6F99F4EB538472FCFEBE22204287E4C@orsmsx509.amr.corp.intel.com>
> name. The dev_stats are allocated initially in a for_each_online_cpu)()
> loop, and after that, corresponding dev_stats is allocated/freed upon
> CPU_ONLINE/CPU_DEAD event callback fcoe_cpu_callback(), do you think
> this is also a problem in using NR_CPUS?
Yes, it's also a problem. Use num_possible_cpus()
-Andi
next prev parent reply other threads:[~2008-12-11 23:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 23:10 [PATCH 0/3] Open-FCoE Submission (round 2) Robert Love
2008-12-09 23:10 ` [PATCH 1/3] FC protocol definition header files Robert Love
2008-12-09 23:10 ` [PATCH 2/3] libfc: A modular Fibre Channel library Robert Love
2008-12-10 0:03 ` Andi Kleen
2008-12-10 18:42 ` Vasu Dev
2008-12-10 19:42 ` Andi Kleen
2008-12-12 1:55 ` Vasu Dev
2008-12-12 2:19 ` Joe Eykholt
2008-12-11 0:44 ` Chris Leech
2008-12-11 0:49 ` Chris Leech
2008-12-11 20:32 ` Zou, Yi
2008-12-11 23:33 ` Andi Kleen [this message]
2008-12-09 23:10 ` [PATCH 3/3] fcoe: Fibre Channel over Ethernet Robert Love
2009-02-05 2:24 ` Andrew Morton
2009-02-06 19:05 ` Robert Love
2009-02-06 19:13 ` Andrew Morton
2009-02-06 19:26 ` [PATCH] kernel-doc: preferred ending marker and examples Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2008-11-18 22:20 [PATCH 0/3] Open-FCoE Submission Robert Love
2008-11-18 22:21 ` [PATCH 2/3] libfc: A modular Fibre Channel library Robert Love
2008-11-24 10:13 ` Andi Kleen
2008-11-25 20:47 ` Love, Robert W
2008-12-02 23:36 ` Love, Robert W
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=20081211233326.GD25779@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=davem@davemloft.net \
--cc=james.bottomley@hansenpartnership.com \
--cc=james.smart@emulex.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jeykholt@cisco.com \
--cc=jgarzik@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=robert.w.love@intel.com \
--cc=yi.zou@intel.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).