lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20080409213241.GA12179@logfs.org>
Date:	Wed, 9 Apr 2008 23:32:41 +0200
From:	Jörn Engel <joern@...fs.org>
To:	Pavel Machek <pavel@....cz>
Cc:	Tomasz Chmielewski <mangoo@...g.org>,
	LKML <linux-kernel@...r.kernel.org>, penberg@...helsinki.fi,
	ext-adrian.hunter@...ia.com, jwboyer@...il.com,
	"Artem B. Bityutskiy" <dedekind@...dex.ru>
Subject: Re: UBIFS vs Logfs (was [RFC PATCH] UBIFS - new flash file system)

On Wed, 9 April 2008 23:09:07 +0200, Pavel Machek wrote:
> 
> I'd like compressed filesystem for maps and lingvistic data... but
> will the flash flesystems have 'reasonable' performance when used on
> harddrive?

If someone implemented readpages(), that might be possible - depending
on your definition of 'reasonable' and your workload.

Writes will hit the disk roughly in order.  When readahead requests a
bunch of pages, there is some chance of them being adjacent and having
the block layer combine most of the bios into a few large ones.

The main drawbacks are:
- No reservations.  If data is written in random order or several
  writers chew away in parallel, write order will be fairly pessimal.
- No readahead yet.  Wouldn't be hard to do.
- Garbage collection completely ignores fragmentation.  If segments are
  needed and one contains a nice long extend from a single file, that
  data will be written elsewhere, often split between two segments.
  Rinse, repeat and fragmentation will increase over time.
- File creation/deletion currently will cause disk heads to jump in
  triangles.  This hurts write performance on most flash media as well,
  so it will get changed reasonably soon.

All of those are solvable.  Some will definitely be solved because the
help performance on flash media as well.  Other may or may not.

Jörn

-- 
When people work hard for you for a pat on the back, you've got
to give them that pat.
-- Robert Heinlein
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ