From: Ralf Baechle <ralf@linux-mips.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Manfred Spraul <manfred@colorfullife.com>,
Andrew Morton <akpm@digeo.com>,
linux-arch@vger.kernel.org
Subject: Re: [PATCH] Allow arch override for kmem_bufctl_t
Date: Mon, 17 May 2004 13:28:31 +0200 [thread overview]
Message-ID: <20040517112831.GA25974@linux-mips.org> (raw)
In-Reply-To: <Pine.GSO.4.58.0405171111300.19405@waterleaf.sonytel.be>
On Mon, May 17, 2004 at 11:11:59AM +0200, Geert Uytterhoeven wrote:
> > if there are no problems with 16-bit quantities. All accesses to
> > kmem_bufctl_t are under a per-cache spinlock and not in the hottest path.
>
> 16-bit is no problem for m68k, so feel free to switch it.
No problem for MIPS either.
Ralf
next prev parent reply other threads:[~2004-05-17 11:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-15 12:13 [PATCH] Allow arch override for kmem_bufctl_t Manfred Spraul
2004-05-15 12:24 ` Manfred Spraul
2004-05-17 9:09 ` Andi Kleen
2004-05-17 9:11 ` Geert Uytterhoeven
2004-05-17 11:28 ` Ralf Baechle [this message]
2004-05-17 11:39 ` Ivan Kokshaysky
2004-05-17 12:39 ` Andi Kleen
2004-05-17 18:22 ` David Mosberger
2004-05-17 21:16 ` David S. Miller
2004-05-17 21:25 ` Matthew Wilcox
2004-05-18 5:04 ` Manfred Spraul
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040517112831.GA25974@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=akpm@digeo.com \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=manfred@colorfullife.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox