From: sfaibish <sfaibish@emc.com>
To: Jan Kara <jack@suse.cz>
Cc: Boaz Harrosh <bharrosh@panasas.com>,
lsf-pc@lists.linuxfoundation.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, Wu Fengguang <fengguang.wu@intel.com>
Subject: Re: [LSF/MM TOPIC] Writeback - current state and future
Date: Fri, 11 Feb 2011 11:22:18 -0500 [thread overview]
Message-ID: <op.vqqyfgtmunckof@usensfaibisl2e.eng.emc.com> (raw)
In-Reply-To: <20110211144717.GH5187@quack.suse.cz>
On Fri, 11 Feb 2011 09:47:17 -0500, Jan Kara <jack@suse.cz> wrote:
> On Sun 06-02-11 10:13:41, Sorin Faibish wrote:
>> I was thinking to have a special track for all the writeback related
>> topics.
> Well, a separate track might be a bit too much I feel ;). I'm
> interested
> also in other things that are happening... We'll see what the program
> will
> be but I can imagine we can discuss for a couple of hours but that might
> be
> just a discussion in a small circle over a <enter preferable drink>.
No problem. I pay for the beer. :) You make the expert pick.
>
>> I would like also to include a discussion on new cache writeback paterns
>> with the target to prevent any cache swaps that are becoming a
>> bigger problem
>> when dealing with servers wir 100's GB caches. The swap is the worst
>> that
>> could happen to the performance of such systems. I will share my
>> latest findings
>> in the cache writeback in continuation to my previous discussion at
>> last LSF.
> I'm not sure what do you exactly mean by 'cache swaps'. If you mean
> that
> your application private cache is swapped out, then I can imagine this
> is a
> problem but I'd need more details to tell how big.
What I meant is to prevent any global cache swap. Think that you have to
SWAP
256GB of cache to a 120MB/sec SATA disk. How long it will take? Cannot be
tolerated. Even if you use SSD at say 1GB/sec it is still a long time. Not
typical but common in HPC. I am not sure you saw my latest results but I
had an example where the swap was taking a long time to the point that a
build on a small memory system didn't finish. The good news are that the
latest kernels 37 RC3 made progress. I have additional data to present.
I will present the latest results next week at FAST conference.
/Sorin
>
> Honza
--
Best Regards
Sorin Faibish
Corporate Distinguished Engineer
Unified Storage Division
EMC2
where information lives
Phone: 508-249-5745
Cellphone: 617-510-0422
Email : sfaibish@emc.com
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-02-11 16:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 16:42 Jan Kara
2011-02-04 18:06 ` Curt Wohlgemuth
2011-02-05 7:55 ` Tao Ma
2011-02-06 10:43 ` Boaz Harrosh
2011-02-06 15:13 ` Sorin Faibish
2011-02-06 16:24 ` Boaz Harrosh
2011-02-11 14:47 ` Jan Kara
2011-02-11 16:22 ` sfaibish [this message]
2011-02-26 21:03 ` Sorin Faibish
2011-02-26 21:07 ` [Lsf-pc] " James Bottomley
2011-02-26 23:21 ` Sorin Faibish
2011-02-26 23:48 ` James Bottomley
2011-02-27 1:50 ` Trond Myklebust
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=op.vqqyfgtmunckof@usensfaibisl2e.eng.emc.com \
--to=sfaibish@emc.com \
--cc=bharrosh@panasas.com \
--cc=fengguang.wu@intel.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linuxfoundation.org \
/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