linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* JBD commmit : Get list of all 'to be written' buffers in advance
@ 2011-05-12 14:22 Niraj Kulkarni
  2011-05-17 18:09 ` Jan Kara
  0 siblings, 1 reply; 3+ messages in thread
From: Niraj Kulkarni @ 2011-05-12 14:22 UTC (permalink / raw)
  To: linux-ext4

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2011-05-18 12:39 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-05-12 14:22 JBD commmit : Get list of all 'to be written' buffers in advance Niraj Kulkarni
2011-05-17 18:09 ` Jan Kara
     [not found]   ` <BANLkTinfoPksqnnVPSfSqnaY33=Y76Djhg@mail.gmail.com>
2011-05-18 12:38     ` Jan Kara

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