mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: [PATCH 00/11] ramfs: Use dynamically sized chunks
Date: Mon, 15 Jun 2020 08:02:18 +0200	[thread overview]
Message-ID: <20200615060229.7533-1-s.hauer@pengutronix.de> (raw)

So far ramfs uses equally sized chunks. This series changes it to use
dynamically sized chunks instead. When making a file bigger ramfs now
always tries to put the additional data in a single chunk. With this
we get fewer chunks and with it better performance as we have less list
iterations to do.
Also this allows us to provide a memmap implementation for ramfs which
works for a good bunch of cases. When a file is created, truncated to
its final size and then filled with data, the data will end up in one
contiguous memory region. In this case we can provide a pointer to this
data which is important for usecases where we would otherwise duplicate
big image files in memory.

Sascha

Sascha Hauer (11):
  update list.h from Linux-5.7
  fs: Add destroy_inode callbacks to filesystems
  fs: Make iput() accept NULL pointers
  fs: free inodes we no longer need
  digest: Drop usage of memmap
  fs: ramfs: Return -ENOSPC
  fs: ramfs: Drop dead code
  fs: ramfs: Use dynamically sized chunks
  fs: ramfs: Implement memmap
  libfile: copy_file: Fix calling discard_range
  libfile: copy_file: explicitly truncate to final size

 crypto/digest.c          |  27 +-
 fs/cramfs/cramfs.c       |  10 +
 fs/devfs.c               |   8 +
 fs/fs.c                  |   7 +-
 fs/nfs.c                 |   8 +
 fs/ramfs.c               | 349 ++++++++++---------
 fs/squashfs/squashfs.c   |  10 +-
 include/linux/compiler.h |   1 -
 include/linux/list.h     | 700 ++++++++++++++++++++++++++++++---------
 include/linux/poison.h   |  26 ++
 include/linux/types.h    |  12 +
 lib/libfile.c            |  25 +-
 12 files changed, 826 insertions(+), 357 deletions(-)
 create mode 100644 include/linux/poison.h

-- 
2.27.0


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2020-06-15  6:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15  6:02 Sascha Hauer [this message]
2020-06-15  6:02 ` [PATCH 01/11] update list.h from Linux-5.7 Sascha Hauer
2020-06-15  6:02 ` [PATCH 02/11] fs: Add destroy_inode callbacks to filesystems Sascha Hauer
2020-06-15  6:02 ` [PATCH 03/11] fs: Make iput() accept NULL pointers Sascha Hauer
2020-06-15  6:02 ` [PATCH 04/11] fs: free inodes we no longer need Sascha Hauer
2020-08-03 22:02   ` Ahmad Fatoum
2020-08-10 11:13     ` Sascha Hauer
2020-06-15  6:02 ` [PATCH 05/11] digest: Drop usage of memmap Sascha Hauer
2020-06-15  6:02 ` [PATCH 06/11] fs: ramfs: Return -ENOSPC Sascha Hauer
2020-06-15  6:02 ` [PATCH 07/11] fs: ramfs: Drop dead code Sascha Hauer
2020-06-15  6:02 ` [PATCH 08/11] fs: ramfs: Use dynamically sized chunks Sascha Hauer
2020-07-02 14:28   ` Ahmad Fatoum
2020-07-05 14:14     ` Sascha Hauer
2020-06-15  6:02 ` [PATCH 09/11] fs: ramfs: Implement memmap Sascha Hauer
2020-06-15  6:02 ` [PATCH 10/11] libfile: copy_file: Fix calling discard_range Sascha Hauer
2020-06-15  6:02 ` [PATCH 11/11] libfile: copy_file: explicitly truncate to final size Sascha Hauer

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=20200615060229.7533-1-s.hauer@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox