linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: Ric Wheeler <rwheeler@redhat.com>
Cc: Jeff Moyer <jmoyer@redhat.com>,
	lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
	linux-block@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] Persistent Memory Error Handling
Date: Fri, 22 Jan 2016 08:09:11 -0500	[thread overview]
Message-ID: <20160122130910.GA28642@bfoster.bfoster> (raw)
In-Reply-To: <56A20A26.1070104@redhat.com>

On Fri, Jan 22, 2016 at 05:53:26AM -0500, Ric Wheeler wrote:
> On 01/21/2016 08:28 PM, Jeff Moyer wrote:
> >Hi,
> >
> >The SNIA Non-volatile Memory Programming Technical Work Group (NVMP-TWG)
> >is working on more closely defining how errors are reported and
> >cleared for persistent memory.  I'd like to give an overview of that
> >work and open the floor to discussion.  This topic covers file systems,
> >memory management, and the block layer so would be suitable for a
> >plenary session.
> >
> >Thanks,
> >Jeff
> >
> 
> Great topic, very interesting to me as well,
> 

Ditto... along with understanding of the error management mechanism, I'd
like to understand the expectations around at what layer errors should
be handled for what configurations. E.g., my understanding is that while
btt handles this internally and returns an error a la traditional
storage, the story is different for pmem and the expectation is for some
kind of filesystem involvement...

Brian

> ric
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
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>

      reply	other threads:[~2016-01-22 13:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-22  1:28 [LSF/MM TOPIC] Persistent Memory Error Handling Jeff Moyer
2016-01-22  7:48 ` Jan Kara
2016-01-22 10:53 ` [Lsf-pc] " Ric Wheeler
2016-01-22 13:09   ` Brian Foster [this message]

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=20160122130910.GA28642@bfoster.bfoster \
    --to=bfoster@redhat.com \
    --cc=jmoyer@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=rwheeler@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).