From: Ingo Molnar <mingo@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Matt B <jackdachef@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com, linux-mm <linux-mm@kvack.org>,
Mel Gorman <mgorman@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [regression v4.0-rc1] mm: IPIs from TLB flushes causing significant performance degradation.
Date: Thu, 5 Mar 2015 00:35:45 +0100 [thread overview]
Message-ID: <20150304233544.GA24733@gmail.com> (raw)
In-Reply-To: <20150304230045.GZ18360@dastard>
* Dave Chinner <david@fromorbit.com> wrote:
> > After going through the series again, I did not spot why there is
> > a difference. It's functionally similar and I would hate the
> > theory that this is somehow hardware related due to the use of
> > bits it takes action on.
>
> I doubt it's hardware related - I'm testing inside a VM, [...]
That might be significant, I doubt Mel considered KVM's interpretation
of pte details?
Thanks,
Ingo
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Mel Gorman <mgorman@suse.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Matt B <jackdachef@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
xfs@oss.sgi.com
Subject: Re: [regression v4.0-rc1] mm: IPIs from TLB flushes causing significant performance degradation.
Date: Thu, 5 Mar 2015 00:35:45 +0100 [thread overview]
Message-ID: <20150304233544.GA24733@gmail.com> (raw)
In-Reply-To: <20150304230045.GZ18360@dastard>
* Dave Chinner <david@fromorbit.com> wrote:
> > After going through the series again, I did not spot why there is
> > a difference. It's functionally similar and I would hate the
> > theory that this is somehow hardware related due to the use of
> > bits it takes action on.
>
> I doubt it's hardware related - I'm testing inside a VM, [...]
That might be significant, I doubt Mel considered KVM's interpretation
of pte details?
Thanks,
Ingo
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Mel Gorman <mgorman@suse.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Matt B <jackdachef@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
xfs@oss.sgi.com
Subject: Re: [regression v4.0-rc1] mm: IPIs from TLB flushes causing significant performance degradation.
Date: Thu, 5 Mar 2015 00:35:45 +0100 [thread overview]
Message-ID: <20150304233544.GA24733@gmail.com> (raw)
In-Reply-To: <20150304230045.GZ18360@dastard>
* Dave Chinner <david@fromorbit.com> wrote:
> > After going through the series again, I did not spot why there is
> > a difference. It's functionally similar and I would hate the
> > theory that this is somehow hardware related due to the use of
> > bits it takes action on.
>
> I doubt it's hardware related - I'm testing inside a VM, [...]
That might be significant, I doubt Mel considered KVM's interpretation
of pte details?
Thanks,
Ingo
next prev parent reply other threads:[~2015-03-04 23:35 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 1:04 [regression v4.0-rc1] mm: IPIs from TLB flushes causing significant performance degradation Dave Chinner
2015-03-02 1:04 ` Dave Chinner
2015-03-02 1:04 ` Dave Chinner
2015-03-02 19:47 ` Linus Torvalds
2015-03-02 19:47 ` Linus Torvalds
2015-03-02 19:47 ` Linus Torvalds
2015-03-03 1:47 ` Dave Chinner
2015-03-03 1:47 ` Dave Chinner
2015-03-03 1:47 ` Dave Chinner
2015-03-03 2:22 ` Linus Torvalds
2015-03-03 2:22 ` Linus Torvalds
2015-03-03 2:22 ` Linus Torvalds
2015-03-03 2:37 ` Linus Torvalds
2015-03-03 2:37 ` Linus Torvalds
2015-03-03 2:37 ` Linus Torvalds
2015-03-03 5:20 ` Dave Chinner
2015-03-03 5:20 ` Dave Chinner
2015-03-03 5:20 ` Dave Chinner
2015-03-03 6:56 ` Linus Torvalds
2015-03-03 6:56 ` Linus Torvalds
2015-03-03 6:56 ` Linus Torvalds
2015-03-03 11:34 ` Dave Chinner
2015-03-03 11:34 ` Dave Chinner
2015-03-03 11:34 ` Dave Chinner
2015-03-03 13:43 ` Mel Gorman
2015-03-03 13:43 ` Mel Gorman
2015-03-03 13:43 ` Mel Gorman
2015-03-03 21:33 ` Dave Chinner
2015-03-03 21:33 ` Dave Chinner
2015-03-03 21:33 ` Dave Chinner
2015-03-04 20:00 ` Mel Gorman
2015-03-04 20:00 ` Mel Gorman
2015-03-04 20:00 ` Mel Gorman
2015-03-04 23:00 ` Dave Chinner
2015-03-04 23:00 ` Dave Chinner
2015-03-04 23:00 ` Dave Chinner
2015-03-04 23:35 ` Ingo Molnar [this message]
2015-03-04 23:35 ` Ingo Molnar
2015-03-04 23:35 ` Ingo Molnar
2015-03-04 23:51 ` Dave Chinner
2015-03-04 23:51 ` Dave Chinner
2015-03-04 23:51 ` Dave Chinner
-- strict thread matches above, loose matches on Subject: below --
2015-03-02 19:17 Matt
2015-03-02 19:25 ` Dave Hansen
2015-03-02 19:45 ` Matt
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=20150304233544.GA24733@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=jackdachef@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=torvalds@linux-foundation.org \
--cc=xfs@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.