Skip to contentSkip to conversation

file system for solid state disks

DISCUSSION Richard Ballantyne 5 participants 6 messages Aug 23, 2007 – Aug 29, 2007

lore
Share & tools
lore
#0 lore raw

What file system that is already in the linux kernel do people recommend I use for my laptop that now contains a solid state disk?

I appreciate your feedback.

Thank you,
Richard Ballantyne

#1 lore raw
Quoted 3 lines · Richard Ballantyne

What file system that is already in the linux kernel do people recommend I use for my laptop that now contains a solid state disk?

If I had to choose, the list of options seems to be:

- logfs
[unmerged]

- UBI layer with any fs you like
[just a guess]

- UDF in Spared Flavor (mkudffs --media-type=cdrw --utf8) [does not support ACLs/quotas]

Jan

#2 lore raw
Quoted 6 lines · Jan Engelhardt
Quoted 3 lines · Richard Ballantyne

What file system that is already in the linux kernel do people recommend I use for my laptop that now contains a solid state disk?

Quoted 7 lines

If I had to choose, the list of options seems to be:

- logfs
[unmerged]

- UBI layer with any fs you like
[just a guess]

The question is whether the solid state disk gives you access to the raw flash, or whether you have to go through the flash translation layer because it's trying to look (exclusively) like a PATA or SATA drive. There are some SSD's that have a form factor and interfaces that make them a drop-in replacement for a laptop hard drive, and a number of the newer laptops that are supporting SSD's seem to be these because (a) they don't have to radically change their design, (b) so they can be compatible with Windows, and (c) so that users can purchase the laptop either with a traditional hard drive or a SSD's as an option, since at the moment SSD's are far more expensive than disks.

So if you can't get access to the raw flash layer, then what you're probably going to be looking at is a traditional block-oriented filesystem, such as ext3, although there are clearly some things that could be done such as disabling the elevator.

- Ted

#3 lore raw
Quoted 27 lines · Theodore Tso
Quoted 6 lines · Jan Engelhardt
Quoted 3 lines · Richard Ballantyne

What file system that is already in the linux kernel do people recommend I use for my laptop that now contains a solid state disk?

Quoted 7 lines

If I had to choose, the list of options seems to be:

- logfs
[unmerged]

- UBI layer with any fs you like
[just a guess]

The question is whether the solid state disk gives you access to the raw flash, or whether you have to go through the flash translation layer because it's trying to look (exclusively) like a PATA or SATA drive. There are some SSD's that have a form factor and interfaces that make them a drop-in replacement for a laptop hard drive, and a number of the newer laptops that are supporting SSD's seem to be these because (a) they don't have to radically change their design, (b) so they can be compatible with Windows, and (c) so that users can purchase the laptop either with a traditional hard drive or a SSD's as an option, since at the moment SSD's are far more expensive than disks.

Quoted 4 lines

So if you can't get access to the raw flash layer, then what you're probably going to be looking at is a traditional block-oriented filesystem, such as ext3, although there are clearly some things that could be done such as disabling the elevator.

It's more complicated than that, I'd say. If the job of the elevator was purely to sort request based on sector criteria, then I'd agree that noop was the best way to go. But the elevator also abritrates access to the disk for processes. Even if you don't pay a seek penalty, you still would rather like to get your sync reads in without having to wait for that huge writer that just queued hundreds of megabytes of io in front of you (and will have done so behind your read, making you wait again for a subsequent read).

My plan in this area is to add a simple storage profile and attach it to the queue. Just start simple, allow a device driver to inform the block layer that this device has no seek penalty. Then the io scheduler can make more informed decisions on what to do - eg for ssd, sector proximity may not have much meaning, so we should not take that into account.

Signature · 1 line
Jens Axboe
#4 lore raw
Quoted 29 lines · Jens Axboe
Quoted 23 lines · Theodore Tso
Quoted 10 lines · Jan Engelhardt
Quoted 2 lines · Richard Ballantyne

What file system that is already in the linux kernel do people recommend I use for my laptop that now contains a solid state disk?

If I had to choose, the list of options seems to be:

- logfs
[unmerged]

- UBI layer with any fs you like
[just a guess]

The question is whether the solid state disk gives you access to the raw flash, or whether you have to go through the flash translation layer because it's trying to look (exclusively) like a PATA or SATA drive. There are some SSD's that have a form factor and interfaces that make them a drop-in replacement for a laptop hard drive, and a number of the newer laptops that are supporting SSD's seem to be these because (a) they don't have to radically change their design, (b) so they can be compatible with Windows, and (c) so that users can purchase the laptop either with a traditional hard drive or a SSD's as an option, since at the moment SSD's are far more expensive than disks.

Quoted 4 lines

So if you can't get access to the raw flash layer, then what you're probably going to be looking at is a traditional block-oriented filesystem, such as ext3, although there are clearly some things that could be done such as disabling the elevator.

Quoted 8 lines

It's more complicated than that, I'd say. If the job of the elevator was purely to sort request based on sector criteria, then I'd agree that noop was the best way to go. But the elevator also abritrates access to the disk for processes. Even if you don't pay a seek penalty, you still would rather like to get your sync reads in without having to wait for that huge writer that just queued hundreds of megabytes of io in front of you (and will have done so behind your read, making you wait again for a subsequent read).

In most cases the time in the elevator is minimal compared to the benefits. Even without your next suggestion.

Quoted 8 lines

My plan in this area is to add a simple storage profile and attach it to the queue. Just start simple, allow a device driver to inform the block layer that this device has no seek penalty. Then the io scheduler can make more informed decisions on what to do - eg for ssd, sector proximity may not have much meaning, so we should not take that into account.

Eventually the optimal solution may require both bandwidth and seek information. If "solid state disk" means flash, it's on a peripheral bus, it's probably not all that fast at transfer rate. If it means NV memory, battery backed or core, probably nothing changes, again *if* it's on a peripheral bus, but if it's on a card plugged to the backplane, the transfer rate may be high enough to make ordering cost more than waiting. This could be extended to nbd and iSCSI devices as well, I think, to optimize performance.

Your plan seems a good one in this area, but if you agree that transfer rate will be important (if it isn't already), perhaps you will be able to design allowing for that capability to be easily added.

Signature · 3 lines
Bill Davidsen <[email protected]>
  "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot
#5 lore raw
Quoted 39 lines · Bill Davidsen
Quoted 29 lines · Jens Axboe
Quoted 23 lines · Theodore Tso
Quoted 10 lines · Jan Engelhardt
Quoted 2 lines · Richard Ballantyne

What file system that is already in the linux kernel do people recommend I use for my laptop that now contains a solid state disk?

If I had to choose, the list of options seems to be:

- logfs
[unmerged]

- UBI layer with any fs you like
[just a guess]

The question is whether the solid state disk gives you access to the raw flash, or whether you have to go through the flash translation layer because it's trying to look (exclusively) like a PATA or SATA drive. There are some SSD's that have a form factor and interfaces that make them a drop-in replacement for a laptop hard drive, and a number of the newer laptops that are supporting SSD's seem to be these because (a) they don't have to radically change their design, (b) so they can be compatible with Windows, and (c) so that users can purchase the laptop either with a traditional hard drive or a SSD's as an option, since at the moment SSD's are far more expensive than disks.

Quoted 4 lines

So if you can't get access to the raw flash layer, then what you're probably going to be looking at is a traditional block-oriented filesystem, such as ext3, although there are clearly some things that could be done such as disabling the elevator.

Quoted 8 lines

It's more complicated than that, I'd say. If the job of the elevator was purely to sort request based on sector criteria, then I'd agree that noop was the best way to go. But the elevator also abritrates access to the disk for processes. Even if you don't pay a seek penalty, you still would rather like to get your sync reads in without having to wait for that huge writer that just queued hundreds of megabytes of io in front of you (and will have done so behind your read, making you wait again for a subsequent read).

Quoted 2 lines

In most cases the time in the elevator is minimal compared to the benefits. Even without your next suggestion.

Runtime overhead, yes. Head optimizations like trying to avoid seeks, definitely no. That can be several miliseconds for a request, and if you waste that time often, then you are going noticably slower than you could be.

Quoted 7 lines
Quoted 7 lines

My plan in this area is to add a simple storage profile and attach it to the queue. Just start simple, allow a device driver to inform the block layer that this device has no seek penalty. Then the io scheduler can make more informed decisions on what to do - eg for ssd, sector proximity may not have much meaning, so we should not take that into account.

Quoted 8 lines

Eventually the optimal solution may require both bandwidth and seek information. If "solid state disk" means flash, it's on a peripheral bus, it's probably not all that fast at transfer rate. If it means NV memory, battery backed or core, probably nothing changes, again *if* it's on a peripheral bus, but if it's on a card plugged to the backplane, the transfer rate may be high enough to make ordering cost more than waiting. This could be extended to nbd and iSCSI devices as well, I think, to optimize performance.

I've yet to see any real runtime overhead problems for any workload, so the ordering is not an issue imo. It's easy enough to bypass for any io scheduler, should it become interesting.

Signature · 1 line
Jens Axboe