From: Hillf Danton <dhillf@gmail.com>
To: Zlatko Calusic <zcalusic@bitsync.net>
Cc: Jiri Slaby <jslaby@suse.cz>,
Daniel J Blueman <daniel@numascale-asia.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Steffen Persvold <sp@numascale.com>, mm <linux-mm@kvack.org>,
Mel Gorman <mgorman@suse.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: kswapd craziness round 2
Date: Fri, 8 Mar 2013 16:27:53 +0800 [thread overview]
Message-ID: <CAJd=RBCLqLKB7SmOPHGS8UUa28whhk6HdchskS8R9yt55Du0Xg@mail.gmail.com> (raw)
In-Reply-To: <51399368.3040200@bitsync.net>
On Fri, Mar 8, 2013 at 3:29 PM, Zlatko Calusic <zcalusic@bitsync.net> wrote:
> There's another bug in there, which I'm still chasing.
>
I am busy in discovering an employer(a really hard work?) so
I dunno the hours I have for that bug.
Hmm, take a look at Mels thoughts?
http://marc.info/?l=linux-mm&m=136189593423501&w=2
BTW, he will be online next week.
Hillf
WARNING: multiple messages have this Message-ID (diff)
From: Hillf Danton <dhillf@gmail.com>
To: Zlatko Calusic <zcalusic@bitsync.net>
Cc: Jiri Slaby <jslaby@suse.cz>,
Daniel J Blueman <daniel@numascale-asia.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Steffen Persvold <sp@numascale.com>, mm <linux-mm@kvack.org>,
Mel Gorman <mgorman@suse.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: kswapd craziness round 2
Date: Fri, 8 Mar 2013 16:27:53 +0800 [thread overview]
Message-ID: <CAJd=RBCLqLKB7SmOPHGS8UUa28whhk6HdchskS8R9yt55Du0Xg@mail.gmail.com> (raw)
In-Reply-To: <51399368.3040200@bitsync.net>
On Fri, Mar 8, 2013 at 3:29 PM, Zlatko Calusic <zcalusic@bitsync.net> wrote:
> There's another bug in there, which I'm still chasing.
>
I am busy in discovering an employer(a really hard work?) so
I dunno the hours I have for that bug.
Hmm, take a look at Mels thoughts?
http://marc.info/?l=linux-mm&m=136189593423501&w=2
BTW, he will be online next week.
Hillf
--
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>
next prev parent reply other threads:[~2013-03-08 8:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 6:18 kswapd craziness round 2 Daniel J Blueman
2013-02-18 11:42 ` Hillf Danton
2013-02-18 15:05 ` Daniel J Blueman
2013-02-20 22:14 ` Jiri Slaby
2013-02-21 12:07 ` Hillf Danton
2013-02-24 21:27 ` Jiri Slaby
2013-02-28 17:02 ` Jiri Slaby
2013-03-01 14:02 ` Hillf Danton
2013-03-07 19:37 ` Jiri Slaby
2013-03-08 6:42 ` Hillf Danton
2013-03-08 6:42 ` Hillf Danton
2013-03-08 7:29 ` Zlatko Calusic
2013-03-08 7:29 ` Zlatko Calusic
2013-03-08 8:27 ` Hillf Danton [this message]
2013-03-08 8:27 ` Hillf Danton
2013-03-08 23:21 ` Jiri Slaby
2013-03-08 23:21 ` Jiri Slaby
2013-03-19 16:59 ` Pádraig Brady
2013-03-19 16:59 ` Pádraig Brady
2013-03-20 4:12 ` Hillf Danton
2013-03-20 4:12 ` Hillf Danton
2013-03-20 8:39 ` Jiri Slaby
2013-03-20 8:39 ` Jiri Slaby
-- strict thread matches above, loose matches on Subject: below --
2013-02-17 22:02 Jiri Slaby
2013-02-17 22:02 ` Jiri Slaby
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='CAJd=RBCLqLKB7SmOPHGS8UUa28whhk6HdchskS8R9yt55Du0Xg@mail.gmail.com' \
--to=dhillf@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=daniel@numascale-asia.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=sp@numascale.com \
--cc=zcalusic@bitsync.net \
/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.