Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1191216
| From | Tejun Heo <tj@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 0/5] Make cpuid <-> nodeid mapping persistent. |
| Date | 2015-07-23 20:40 +0200 |
| Message-ID | <pPtzs-6sr-25@gated-at.bofh.it> (permalink) |
| References | <pJxw5-3UB-5@gated-at.bofh.it> <pMDbY-4gz-11@gated-at.bofh.it> <pPgCe-4F9-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hello, Tang. On Thu, Jul 23, 2015 at 12:44:53PM +0800, Tang Chen wrote: > Allocating cpuid when a new cpu comes up and reusing the cpuid when it > comes up again is possible. But I'm not quite sure if it will be less > modification > because we still need an array or bit map or something to keep the mapping, > and select backup nodes for cpus on memory-less nodes when allocating > memory. > > I can post a set of patches for this idea. And then we can see which one is > better. I suspect the difference could be that in the current code the users (workqueue) can remain the same while if we do it lazily there probably needs to be a way to poke it. As long as the IDs are allocated to the online CPUs first, I think pre-allocating everything should be fine too. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [PATCH 0/5] Make cpuid <-> nodeid mapping persistent. Tang Chen <tangchen@cn.fujitsu.com> - 2015-07-23 06:50 +0200 Re: [PATCH 0/5] Make cpuid <-> nodeid mapping persistent. Tejun Heo <tj@kernel.org> - 2015-07-23 20:40 +0200
csiph-web