Hello Chrstoph,
On Mon, Jul 20, 2020 at 9:53 AM Christoph Hellwig wrote:
>
> Set up a readahead size by default. This changes behavior for mtd,
> ubifs, and vboxsf to actually enabled readahead, the lack of which
> very much looks like an oversight.
UBIFS doesn't enable readahead on purpose, pl
On Mon, Jul 20, 2020 at 2:37 PM Artem Bityutskiy wrote:
>
> On Mon, 2020-07-20 at 14:07 +0200, Christoph Hellwig wrote:
> > What about jffs2 and blk2mtd raw block devices?
I don't worry much about blk2mtd.
> If my memory serves me correctly JFFS2 did not mind readahead.
This covers my knowledge
s/super.c| 1 -
> fs/btrfs/disk-io.c| 1 -
> fs/fuse/inode.c | 1 -
> fs/nfs/super.c| 9 +
> fs/ubifs/super.c | 1 +
For ubifs and mtd:
Acked-by: Richard Weinberger
Thanks,
//richard
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
Helen,
On Wed, Sep 26, 2018 at 7:01 AM Helen Koike wrote:
>
> This series is reviving an old patchwork.
> Booting from a mapped device requires an initramfs. This series is
> allows for device-mapper targets to be configured at boot time for
> use early in the boot process (as the root device or
Helen,
Am Samstag, 3. November 2018, 04:53:39 CET schrieb Helen Koike:
> As mentioned in the discussion from the previous version of this patch,
> Android
> and Chrome OS do not use initramfs mostly due to boot time and size liability.
Do you have numbers on that?
I understand that using someth
,7 @@ struct mtd_blktrans_dev {
> struct blk_mq_tag_set *tag_set;
> spinlock_t queue_lock;
> void *priv;
> - fmode_t file_mode;
> + bool writable;
> };
Acked-by: Richard Weinberger
Thanks,
//richard
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
flags.w){
> - if(--ubd_dev->count == 0) ubd_close_dev(ubd_dev);
> - err = -EROFS;
> - }*/
Acked-by: Richard Weinberger
Thanks,
//richard
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
