public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Finn Hakansson <finn@axis.com>
Cc: "Rogelio M. Serrano Jr." <rogelio@evoserve.com>,
	"mtd@infradead.org" <mtd@infradead.org>,
	jffs-dev@axis.com
Subject: Re: jffs_file_write
Date: Tue, 25 Jul 2000 10:29:47 +0100	[thread overview]
Message-ID: <31773.964517387@cygnus.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.21.0007241657220.18380-100000@vvv.axis.se>


finn@axis.com said:
>  Yeah. One day, write and rewrite should be merged into one single
> function... 

I'm been thinking about this, and about the problems with garbage collection
taking to long. What about shifting all node writes into a kernel thread,
which also does the GC?

The jffs_file_write() function then only needs to queue the node(s) to be 
written, and can return immediately. Obviously we have to implement a way 
of flushing a particular file, but that shouldn't be too difficult.

--
dwmw2




To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

  reply	other threads:[~2000-07-25  9:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-21 23:41 jffs_file_write Rogelio M. Serrano Jr.
2000-07-24 15:09 ` jffs_file_write Finn Hakansson
2000-07-25  9:29   ` David Woodhouse [this message]
2000-07-25  9:44     ` jffs_file_write Finn Hakansson
2000-07-25 10:01       ` jffs_file_write David Woodhouse
2000-07-25 10:11         ` jffs_file_write Finn Hakansson
2000-07-25 13:02           ` jffs_file_write Bjorn Wesen
2000-07-25 13:19             ` jffs_file_write David Woodhouse
2000-07-25 13:54           ` jffs_file_write David Woodhouse
2000-07-25 10:02     ` jffs_file_write Bjorn Wesen
2000-07-25 10:15       ` jffs_file_write David Woodhouse
2000-07-25 14:29     ` jffs_file_write Philipp Rumpf
2000-07-25 15:12       ` jffs_file_write David Woodhouse
2000-07-25 15:24         ` jffs_file_write Philipp Rumpf

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=31773.964517387@cygnus.co.uk \
    --to=dwmw2@infradead.org \
    --cc=finn@axis.com \
    --cc=jffs-dev@axis.com \
    --cc=mtd@infradead.org \
    --cc=rogelio@evoserve.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