From: Andiry Xu <jix024@eng.ucsd.edu>
To: Jan Kara <jack@suse.cz>
Cc: lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
andiry@gmail.com
Subject: Re: [Lsf-pc] [LSF/MM ATTEND] [LSF/MM TOPIC] NOVA: A log-structured file system for NVM
Date: Wed, 10 Feb 2016 08:03:47 -0800 [thread overview]
Message-ID: <CAD4Szjvue4-ASP9FAH_EZTMVQFJ4vQ2XOkMZNrcSd7nLXHieFw@mail.gmail.com> (raw)
In-Reply-To: <20160210111414.GF12245@quack.suse.cz>
On Wed, Feb 10, 2016 at 3:14 AM, Jan Kara <jack@suse.cz> wrote:
> Hi,
>
> On Tue 09-02-16 22:15:00, Andiry Xu wrote:
>> I would like to attend LSF/MM to present a new file system design for
>> non-volatile main memories.
>
> Well, LSF/MM is based more on discussions than presentations. Also a lot of
> people from LSF/MM will go to Vault so I don't think presenting at LSF/MM
> would make much sense. But we register your attend request.
>
> Honza
>
Thank you Jan.
>> The goal of NOVA is to provide high performance and strong consistency
>> (atomic metadata, data, mmap updates) at the same time.
>>
>> Although NOVA is a LFS, as it targets a different memory technology,
>> it looks very different from conventional LFS. Some of the key design
>> decisions of NOVA include:
>>
>> Per-inode log: Each inode has a log, with tail pointer points to the
>> latest committed entry. This allows for high concurrency and parallel
>> log scanning.
>>
>> Log is a linked list: Allows for fine-grained, page-size granularity
>> garbage collection. Also, allocating log space is easy since NOVA does
>> not need to allocate large, contiguous space for logs.
>>
>> Cheap atomicity: To atomically append a log, NOVA simply appends the
>> log entry and then updates the log tail pointer. To coordinate updates
>> across logs, NOVA appends each log and journal the log tails to update
>> all logs atomically. This mechanism has lower overhead than journaling
>> (which doubles writes) and shadow paging (which causes cascade
>> updates).
>>
>> Stores file data outside the log: NOVA appends metadata of writes to
>> the log and handles file data in a copy-on-write way. This results in
>> a shorter log, and garbage collection is simple and efficient, as NOVA
>> never copies data in log cleaning.
>>
>> Highly scalable: NOVA has free list, journal and inode table at each
>> CPU to avoid global locking and scalability bottlenecks.
>>
>> NOVA is available on GitHub:
>>
>> https://github.com/NVSL/NOVA
>>
>> And the paper of NOVA will appear in FAST 2016. I will also give a
>> talk in the Vault conference.
>>
>> I'm also interested in any NVM/DAX related topics. Thank you.
> --
> Jan Kara <jack@suse.com>
> SUSE Labs, CR
next prev parent reply other threads:[~2016-02-10 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 6:15 [LSF/MM ATTEND] [LSF/MM TOPIC] NOVA: A log-structured file system for NVM Andiry Xu
2016-02-10 11:14 ` [Lsf-pc] " Jan Kara
2016-02-10 16:03 ` Andiry Xu [this message]
2016-02-10 16:19 ` James Bottomley
2016-02-11 14:00 ` Jan Kara
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=CAD4Szjvue4-ASP9FAH_EZTMVQFJ4vQ2XOkMZNrcSd7nLXHieFw@mail.gmail.com \
--to=jix024@eng.ucsd.edu \
--cc=andiry@gmail.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).