[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMO-S2hAYg9+0iJkwy6xsBiR+g1YPr34Am+C6UR47qqDRiH0ow@mail.gmail.com>
Date: Sun, 5 Feb 2012 16:01:31 +0900
From: Hitoshi Mitake <h.mitake@...il.com>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: "H. Peter Anvin" <hpa@...ux.intel.com>,
James Bottomley <jbottomley@...allels.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Matthew Wilcox <matthew.r.wilcox@...el.com>,
Roland Dreier <roland@...estorage.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] NVMe: Fix compilation on architecturs without readq/writeq
On Sun, Feb 5, 2012 at 15:53, Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
> On Sat, Feb 4, 2012 at 16:39, Hitoshi Mitake <h.mitake@...il.com> wrote:
>>> I worked myself on a driver (which sadly never shipped) which had an WC
>>> window and a UC window... the final write in a series had a completion bit
>>> in it and would go to the UC window after setting up a whole chunk of
>>> operations in the WC window (writing UC memory flushes WC memory ahead of
>>> it.)
>>>
>>> Thus, the two-part breakdown of writeq() to the UC window had to write the
>>> low half to the WC window instead. This is clearly not generic.
>>
>> Because of my ignorant, I don't know the words "UC window" and "WC window"
>> in this context. Could you teach me?
>
> UN = uncached, WC = writecombining.
Thanks a lot for your teaching!
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
--
Hitoshi Mitake
h.mitake@...il.com
--
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