>> Do you have some before/after numbers from lmbench fork overhead >> (I wouldn't expect much impact from this, but it would be nice to >> make sure). > >I am running lmbench even as we speak. Is there a way to run lmbench >and only get the fork overhead information?
You can run the "lat_proc" binary with the "fork" argument. >I started with this patch because it goes part of the way to where I >need to be. I am trying to get 4 level page table directories working >efficiently on SGI boxes. I see this as three problems. Do you mean full four-level page tables, or just fixing the quirks in the current implementation that has an empty PUD level (and seems to have caused a slight drop in performance for reasons that are not yet completely understood)? >Right now, neither the quicklists nor slabs are node local. I think >that is a larger issue. I will start a seperate discussion about node >locality soon. Making the slab node aware is probably the right thing to do, but making quicklists node aware is less invasive. -Tony - To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
