public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: device-mapper development <dm-devel@redhat.com>,
	Amit Kale <akale@stec-inc.com>,
	"linux-bcache@vger.kernel.org" <linux-bcache@vger.kernel.org>,
	"kent.overstreet@gmail.com" <kent.overstreet@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	lsf-pc@lists.linux-foundation.org, Joe Thornber <ejt@redhat.com>
Subject: Re: [LSF/MM TOPIC] Re: [dm-devel] Announcement: STEC EnhanceIO SSD caching software for Linux kernel
Date: Fri, 18 Jan 2013 16:37:59 -0500	[thread overview]
Message-ID: <20130118213759.GA30278@redhat.com> (raw)
In-Reply-To: <20130118212543.GB6425@blackbox.djwong.org>

On Fri, Jan 18 2013 at  4:25pm -0500,
Darrick J. Wong <darrick.wong@oracle.com> wrote:

> Since Joe is putting together a testing tree to compare the three caching
> things, what do you all think of having a(nother) session about ssd caching at
> this year's LSFMM Summit?
> 
> [Apologies for hijacking the thread.]
> [Adding lsf-pc to the cc list.]

Hopefully we'll have some findings on the comparisons well before LSF
(since we currently have some momentum).  But yes it may be worthwhile
to discuss things further and/or report findings.

Mike

  reply	other threads:[~2013-01-18 21:38 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-11 17:18 Announcement: STEC EnhanceIO SSD caching software for Linux kernel Amit Kale
2013-01-11 22:36 ` Marcin Slusarz
2013-01-14 21:46 ` Mike Snitzer
2013-01-15 13:19   ` Amit Kale
2013-01-16 10:45     ` [dm-devel] " thornber
2013-01-16 12:15       ` thornber
2013-01-16 16:58       ` thornber
2013-01-17  9:52       ` Amit Kale
2013-01-17 11:39         ` Kent Overstreet
2013-01-17 17:17           ` Amit Kale
2013-01-24 23:45           ` Kent Overstreet
2013-01-17 13:26         ` thornber
2013-01-17 17:53           ` Amit Kale
2013-01-17 18:36             ` Jason Warr
2013-01-18  9:08               ` Amit Kale
2013-01-18 15:56                 ` Jason Warr
2013-01-18 16:11                   ` thornber
2013-01-18 16:45                     ` Jason Warr
2013-01-18 17:42                       ` thornber
2013-01-18 17:44                       ` Amit Kale
2013-01-18 18:36                         ` Jason Warr
2013-01-18 21:25                           ` [LSF/MM TOPIC] " Darrick J. Wong
2013-01-18 21:37                             ` Mike Snitzer [this message]
2013-01-21  5:26                               ` Amit Kale
2013-01-21 13:09                                 ` Mike Snitzer
2013-01-21 13:58                                   ` thornber
2013-01-22  5:00                                   ` Amit Kale
2013-02-04 20:33                               ` Kent Overstreet
2013-01-18 16:12                   ` Amit Kale
2013-01-24 23:55                 ` Kent Overstreet
2013-01-17 18:50             ` thornber
2013-01-18  7:03               ` Amit Kale
2013-01-18 14:43       ` thornber
2013-01-30 12:36 ` Pavel Machek
2013-01-30 19:56   ` Amit Kale

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=20130118213759.GA30278@redhat.com \
    --to=snitzer@redhat.com \
    --cc=akale@stec-inc.com \
    --cc=darrick.wong@oracle.com \
    --cc=dm-devel@redhat.com \
    --cc=ejt@redhat.com \
    --cc=kent.overstreet@gmail.com \
    --cc=linux-bcache@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.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