linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [LSF/MM ATTEND] Persistent Memory Error Handling
@ 2016-01-23  6:37 Vishal Verma
  0 siblings, 0 replies; only message in thread
From: Vishal Verma @ 2016-01-23  6:37 UTC (permalink / raw)
  To: lsf-pc; +Cc: linux-fsdevel, linux-block, linux-mm, linux-nvdimm@lists.01.org

Hi,

I'd like to attend LSF/MM. My primary topic of interest is the above as
proposed by Jeff Moyer:

http://www.spinics.net/lists/linux-mm/msg100560.html

I wrote the initial enabling for error handling that was merged for 4.5
(Building a poison list in the libnvdimm subsystem, exposing it as
'badblocks'), and am working on subsequent improvements in this areaa.
These would include making the initial poison gathering asynchronous,
and finer grained DAX control instead of turning DAX off entirely in
the presence of poison which we currently do.

Another topic of discussion I'd like to propose within this session is
to explore if there are use cases that the now-generic badblocks
implementation can fit. There is at least one opportunity of
consolidation between md-raid's sysfs representation of badblocks, and
the generically available one in gendisk.

Thanks,
	-Vishal

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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2016-01-23  6:37 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-01-23  6:37 [LSF/MM ATTEND] Persistent Memory Error Handling Vishal Verma

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