[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200612152327.25706.rjw@sisk.pl>
Date: Fri, 15 Dec 2006 23:27:24 +0100
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Jeff Garzik <jeff@...zik.org>
Cc: Alan <alan@...rguk.ukuu.org.uk>, Andrew Morton <akpm@...l.org>,
Neil Brown <neilb@...e.de>, Jurriaan <thunder7@...all.nl>,
linux-kernel@...r.kernel.org, linux-raid@...r.kernel.org,
Tejun Heo <htejun@...il.com>
Subject: Re: sata badness in 2.6.20-rc1? [Was: Re: md patches in -mm]
On Friday, 15 December 2006 23:19, Jeff Garzik wrote:
> Alan wrote:
> > On Fri, 15 Dec 2006 13:39:27 -0800
> > Andrew Morton <akpm@...l.org> wrote:
> >
> >> On Fri, 15 Dec 2006 13:05:52 -0800
> >> Andrew Morton <akpm@...l.org> wrote:
> >>
> >>> Jeff, I shall send all the sata patches which I have at you one single time
> >>> and I shall then drop the lot. So please don't flub them.
> >>>
> >>> I'll then do a rc1-mm2 without them.
> >> hm, this is looking like a lot of work for not much gain. Rafael, are
> >> you able to do a quick chop and tell us whether these:
> >
> > The md one and the long history of reports about parallel I/O causing
> > problems sounds a lot more like the kmap stuff you were worried about
> > Andrew. I'd be very intereste dto know if it happens on x86_32 built with
> > a standard memory split and no highmem....
>
> 2.6.20-rc1 works, and 2.6.20-rc1 does not have the kmap_atomic() fix.
>
> Upstream does kmap_atomic(KM_USER0) and -mm does kmap_atomic(KM_IRQ0)
On x86_64 that shouldn't be a problem, I think, and my machine is an x86_64
one.
Greetings,
Rafael
--
If you don't have the time to read,
you don't have the time or the tools to write.
- Stephen King
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists