Re: [PATCH resend^2] mm: increase RECLAIM_DISTANCE to 30

From: KOSAKI Motohiro
Date: Tue Apr 12 2011 - 03:26:24 EST


> On Tue, 2011-04-12 at 10:01 +0900, KOSAKI Motohiro wrote:
> > > On Mon, 2011-04-11 at 17:19 +0900, KOSAKI Motohiro wrote:
> > > > This patch raise zone_reclaim_mode threshold to 30. 30 don't have
> > > > specific meaning. but 20 mean one-hop QPI/Hypertransport and such
> > > > relatively cheap 2-4 socket machine are often used for tradiotional
> > > > server as above. The intention is, their machine don't use
> > > > zone_reclaim_mode.
> > >
> > > I know specifically of pieces of x86 hardware that set the information
> > > in the BIOS to '21' *specifically* so they'll get the zone_reclaim_mode
> > > behavior which that implies.
> >
> > Which hardware?
>
> I'd have to go digging for the model numbers. I just remember having
> discussions with folks about it a couple of years ago. My memory isn't
> what it used to be. :)

O.K.

>
> > The reason why now we decided to change default is the original bug reporter was using
> > mere commodity whitebox hardware and very common workload.
> > If it is enough commotidy, we have to concern it. but if it is special, we don't care it.
> > Hardware vendor should fix a firmware.
>
> Yeah, it's certainly a "simple" fix. The distance tables can certainly
> be adjusted easily, and worked around pretty trivially with boot
> options. If we decide to change the generic case, let's also make sure
> that we put something else in place simultaneously that is nice for the
> folks that don't want it changed. Maybe something DMI-based that digs
> for model numbers?

That pretty makes sense. If you can find exacl model number, I'm fully
assist this portion.


> I'll go try and dig for some more specifics on the hardware so we at
> least have something to test on.

Thank you!



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/