From: Linus Torvalds <torvalds@linux-foundation.org>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: clameter@sgi.com, linux-kernel@vger.kernel.org
Subject: Re: tlb_finish_mmu() bogisity
Date: Sun, 23 Dec 2007 13:15:59 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.0.9999.0712231311530.21557@woody.linux-foundation.org> (raw)
In-Reply-To: <20071223093241.GR8181@ftp.linux.org.uk>
On Sun, 23 Dec 2007, Al Viro wrote:
>
> tlb->need_flush += &__get_cpu_var(quicklist)[0].nr_pages != 0;
> makes no sense whatsoever. How the hell can you ever get the address of
> __get_cpu_var(quicklist)[0].nr_pages to be NULL? Postfix operators have
> higher precedence than prefix ones, so that's
> &(((__get_cpu_var(quicklist))[0]).nr_pages)
>
> What did you intend here? s/&//, perhaps?
I think that thing is bogus in other ways. It plays games with
"needs_flush", just because it seems to want the generic code to then call
"check_pgt_cache()", not because it actually wants any flushing to take
place.
But we already call "check_pgt_cache()" there in tlb_finish_mmu()
unconditionally, so I think the whole patch was utter crap.
Or is there any other reason going on here? That quicklist stuff has been
totally broken, it's done too many totally invalid things to really be
worth even keeping. We should get rid of that unmaintainable hack, and if
it has a real performance upside, we should make it part of the *native*
mmu-gather infrastructure, instead of maintaining it as some separate and
buggy/unmaintainable piece-of-sh*t code.
Linus
next prev parent reply other threads:[~2007-12-23 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-23 9:32 Al Viro
2007-12-23 21:15 ` Linus Torvalds [this message]
2007-12-24 19:25 ` Christoph Lameter
2007-12-26 20:43 ` Christoph Lameter
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=alpine.LFD.0.9999.0712231311530.21557@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ftp.linux.org.uk \
/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
all inboxes | Powered by JetHome®