Jesse Barnes writes: > On Thu, Sep 04, 2003 at 12:06:46PM -0700, Luck, Tony wrote: > > What are the remaining issues with sparse memory within a node? > > CONFIG_VIRTUAL_MEM_MAP should be able to cope with this without > > wasting memory on "struct page" for non-existent pages in the holes. > > Yeah, that's what we're using the latest discontig patches. > > > Presumably there are some bootmem bitmap size issues if the gaps > > within nodes are too huge. But a few GB shouldn't be a problem (with > > a 16K page size, each GB of memory/hole only takes 8K of bitmap). > > Right, until we get really huge holes, that'll be ok, and there are > already some optimizations to keep track of the last place a successful > bootmem allocation came from so that you don't keep walking through the > holes, which helped zx1 boots. This allows supporting our platform without specific modifications. > > > Is there anything else that blows up? > > Not that I know of... > > > If not, then could we just drop the printk altogether? > > Sure, sounds good to me. About code cleaning, it seems that the IA64_NODESIZE_* options are still present in Kconfig but no more used, at least for DIG platforms. Thanks again for taking in account our problem. Xavier -- Sincères salutations. _____________________________________________________________________ Xavier BRU BULL ISD/R&D/INTEL office: FREC B1-422 tel : +33 (0)4 76 29 77 45 http://www-frec.bull.fr fax : +33 (0)4 76 29 77 70 mailto:Xavier.Bru@bull.net addr: BULL, 1 rue de Provence, BP 208, 38432 Echirolles Cedex, FRANCE _____________________________________________________________________ - To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Fri Sep 5 06:10:51 2003
This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:17 EST