From: Jan Kara <jack@suse.cz>
To: "Verma, Vishal L" <vishal.l.verma@intel.com>
Cc: "lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [Lsf-pc] [LSF/MM ATTEND] Persistent Memory
Date: Mon, 30 Dec 2013 22:04:04 +0100 [thread overview]
Message-ID: <20131230210404.GB5457@quack.suse.cz> (raw)
In-Reply-To: <1387907056.2487.18.camel@vverma7-desk1.amr.corp.intel.com>
Added some relevant lists to CC (please don't forget about this).
On Tue 24-12-13 17:44:35, Verma, Vishal L wrote:
> I would like to attend LSF/MM 2014 - I am especially interested in
> discussions around persistent memory. I have been studying EXT4 and
> researching on what we'd have to do to best enable it for
> byte-addressable persistent memory.
Do you have some concrete suggestions or observations regarding this?
Because discussing abstract ideas without actually trying something out
beforehand doesn't usually result in a useful discussion...
> I am relatively new in the Linux kernel world, and my previous
> experience has been with device driver work - I wrote a SCSI SG_IO
> translation layer for the NVMe driver. I also contributed to PMFS -
> https://github.com/linux-pmfs/pmfs which was our go-to route for
> enabling PM in the kernel before we decided EXT4 would be a better
> choice.
I would be interested what were your reasons for the decision. Can you
elaborate a bit (that's just my personal curiosity)?
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next parent reply other threads:[~2013-12-30 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1387907056.2487.18.camel@vverma7-desk1.amr.corp.intel.com>
2013-12-30 21:04 ` Jan Kara [this message]
2014-01-03 17:45 ` [Lsf-pc] [LSF/MM ATTEND] Persistent Memory Verma, Vishal L
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=20131230210404.GB5457@quack.suse.cz \
--to=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=vishal.l.verma@intel.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).