From: Niraj Kulkarni <kulkarniniraj14@gmail.com>
To: linux-ext4@vger.kernel.org
Subject: JBD commmit : Get list of all 'to be written' buffers in advance
Date: Thu, 12 May 2011 19:52:21 +0530 [thread overview]
Message-ID: <4DCBED1D.2010109@gmail.com> (raw)
Hi all,
I am trying to implement a concept called Transactional Flash
(http://www.usenix.org/event/osdi08/tech/full_papers/prabhakaran/prabhakaran_html/)
in which all writes are flushed to disk (in this case Flash)
as a circular linked list of pages. No journaling mechanisms are used.
For that I am trying to get list of all buffers to be written
(metadata or data) before actually writing them. I thought of 2
approaches :
1. Get conservative list of all buffers before flushing any of them
(before commit phase 2) in journal_commit_transaction function.
Problem : Metadata writes use temporary buffers which are
allocated just before write.
2. Instead of submitting buffers straightaway, collect all of them (
data + metadata ) and flush them in end.
Problem : i. Possibility of blocking after data buffers are
collected but before metadata buffer collection.
Since data buffers are locked, this may lead
to deadlock. (I am not sure if it is spinlock)
ii. Not able to differentiate between metadata
buffers and Descriptor buffers.
Can anybody please help me in this regard?
Niraj
next reply other threads:[~2011-05-12 14:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 14:22 Niraj Kulkarni [this message]
2011-05-17 18:09 ` JBD commmit : Get list of all 'to be written' buffers in advance Jan Kara
[not found] ` <BANLkTinfoPksqnnVPSfSqnaY33=Y76Djhg@mail.gmail.com>
2011-05-18 12:38 ` 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=4DCBED1D.2010109@gmail.com \
--to=kulkarniniraj14@gmail.com \
--cc=linux-ext4@vger.kernel.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).