From: Peter Osterlund <petero2@telia.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Damian Pietras <daper@daper.net>, Phillip Susi <psusi@cfl.rr.com>,
linux-kernel@vger.kernel.org
Subject: Re: Problems with eject and pktcdvd
Date: 15 Jan 2006 22:34:59 +0100 [thread overview]
Message-ID: <m37j91yy2k.fsf@telia.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0601152216220.9875@yvahk01.tjqt.qr>
Jan Engelhardt <jengelh@linux01.gwdg.de> writes:
> >> pktsetup 0 /dev/hdc
> >> mount /dev/pktcdvd/0 /mnt/tmp
> >> umount /mnt/tmp
>
> A question BTW; I do not seem to need pktcdvd for DVD+RWs,
> I can just mount them after mkfs'ing /dev/hdc - what's up with that?
Basically, if you don't use the packet writing driver, the DVD drive
firmware will do similar work on its own, because the hardware can
only write 32KB blocks. The firmware is often slower than the pktcdvd
driver, because the firmware doesn't have as much memory available as
the kernel to reorder I/O operations for improved throughput.
See also Documentation/cdrom/packet-writing.txt:
Packet writing for DVD+RW media
-------------------------------
According to the DVD+RW specification, a drive supporting DVD+RW discs
shall implement "true random writes with 2KB granularity", which means
that it should be possible to put any filesystem with a block size >=
2KB on such a disc. For example, it should be possible to do:
# dvd+rw-format /dev/hdc (only needed if the disc has never
been formatted)
# mkudffs /dev/hdc
# mount /dev/hdc /cdrom -t udf -o rw,noatime
However, some drives don't follow the specification and expect the
host to perform aligned writes at 32KB boundaries. Other drives do
follow the specification, but suffer bad performance problems if the
writes are not 32KB aligned.
Both problems can be solved by using the pktcdvd driver, which always
generates aligned writes.
# dvd+rw-format /dev/hdc
# pktsetup dev_name /dev/hdc
# mkudffs /dev/pktcdvd/dev_name
# mount /dev/pktcdvd/dev_name /cdrom -t udf -o rw,noatime
--
Peter Osterlund - petero2@telia.com
http://web.telia.com/~u89404340
next prev parent reply other threads:[~2006-01-15 21:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-15 12:35 Problems with eject and pktcdvd Damian Pietras
2006-01-15 17:53 ` Phillip Susi
2006-01-15 18:50 ` Damian Pietras
2006-01-15 19:17 ` Phillip Susi
2006-01-15 20:47 ` Peter Osterlund
2006-01-15 21:04 ` Damian Pietras
2006-01-15 21:18 ` Jan Engelhardt
2006-01-15 21:34 ` Peter Osterlund [this message]
2006-02-05 19:13 ` Peter Osterlund
2006-02-05 21:07 ` Damian Pietras
2006-02-05 22:44 ` Peter Osterlund
2006-02-06 20:15 ` Damian Pietras
2006-02-11 11:21 ` Peter Osterlund
2006-02-12 10:34 ` Damian Pietras
2006-01-15 22:23 ` Phillip Susi
2006-01-15 22:55 ` Nix
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=m37j91yy2k.fsf@telia.com \
--to=petero2@telia.com \
--cc=daper@daper.net \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=psusi@cfl.rr.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