From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2 0/3] bmaptool support
Date: Wed, 27 Apr 2016 12:36:29 +0300 [thread overview]
Message-ID: <cover.1461749328.git.ed.bartosh@linux.intel.com> (raw)
Hi,
This patchset adds ability to use bmaptool to flash images faster than
using traditional methods.
Bmaptool is a generic tool for creating the block map (bmap) for a file
and and copying files using the block map. The idea is that large file
containing unused blocks, like raw system image files, can be copied or
flashed a lot faster with bmaptool than with traditional tools like
"dd" or "cp".
Here is an example of flashing image using dd and bmaptool showing
around 25% performance gain in flashing time:
> ls -slh
19M -rw-r--r-- 1 ed ed 26M Apr 26 11:36 core-image-minimal-qemux86-64-20160426083554.rootfs.ext4
4.0K -rw-r--r-- 1 ed ed 2.7K Apr 26 11:36 core-image-minimal-qemux86-64-20160426083554.rootfs.ext4.bmap
> time dd if=core-image-minimal-qemux86-64-20160426083554.rootfs.ext4 of=/dev/sdb
52302+0 records in
52302+0 records out
26778624 bytes (27 MB) copied, 2.51183 s, 10.7 MB/s
real 0m2.515s
user 0m0.014s
sys 0m0.329s
> time bmaptool copy core-image-minimal-qemux86-64-20160426083554.rootfs.ext4 /dev/sdb
bmaptool: info: discovered bmap file 'core-image-minimal-qemux86-64-20160426083554.rootfs.ext4.bmap'
bmaptool: info: block map format version 2.0
bmaptool: info: 6538 blocks of size 4096 (25.5 MiB), mapped 4799 blocks (18.7 MiB or 73.4%)
bmaptool: info: copying image 'core-image-minimal-qemux86-64-20160426083554.rootfs.ext4' to block device '/dev/sdb' using bmap file 'core-image-minimal-qemux86-64-20160426083554.rootfs.ext4.bmap'
bmaptool: info: 100% copied
bmaptool: info: synchronizing '/dev/sdb'
bmaptool: info: copying time: 1.8s, copying speed 10.3 MiB/sec
real 0m1.909s
user 0m0.226s
sys 0m0.052s
The test was repeated 5 times with the same image and the same usb stick device.
Changes in v2: Combined Alexander's and my bmap-tools recipes.
Got rid of generating standalone script as it breaks build of bmap-tools-native.
The following changes since commit a9b503b268e94d311f892fa00c5d6bd9ffdb228e:
license.bbclass: make sure that image manifest dir exists (2016-04-22 16:28:57 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib ed/oe-core/bmap-tools-9414
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=ed/oe-core/bmap-tools-9414
Alexander D. Kanevskiy (1):
image types: add bmap generation option
Ed Bartosh (2):
bmap-tools: initial commit, version 3.2
selftest: add bmap test
meta/classes/image_types.bbclass | 4 +++-
meta/lib/oeqa/selftest/imagefeatures.py | 27 +++++++++++++++++++++++
meta/recipes-support/bmap-tools/bmap-tools_3.2.bb | 24 ++++++++++++++++++++
3 files changed, 54 insertions(+), 1 deletion(-)
create mode 100644 meta/recipes-support/bmap-tools/bmap-tools_3.2.bb
--
2.1.4
next reply other threads:[~2016-04-27 11:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 9:36 Ed Bartosh [this message]
2016-04-27 9:36 ` [PATCH v2 1/3] bmap-tools: initial commit, version 3.2 Ed Bartosh
2016-04-28 22:07 ` Alexander Kanevskiy
2016-04-29 4:55 ` Paul Eggleton
2016-04-29 8:38 ` Alexander Kanevskiy
2016-05-02 5:43 ` Ed Bartosh
2016-04-27 9:36 ` [PATCH v2 2/3] image types: add bmap generation option Ed Bartosh
2016-04-27 9:36 ` [PATCH v2 3/3] selftest: add bmap test Ed Bartosh
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=cover.1461749328.git.ed.bartosh@linux.intel.com \
--to=ed.bartosh@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.