Home
last modified time | relevance | path

Searched refs:stripe (Results 1 – 25 of 43) sorted by relevance

12

/kernel/linux/linux-5.10/drivers/md/
Ddm-stripe.c21 struct stripe { struct
44 struct stripe stripe[]; argument
62 unsigned int stripe, char **argv) in get_stripe() argument
72 &sc->stripe[stripe].dev); in get_stripe()
76 sc->stripe[stripe].physical_start = start; in get_stripe()
132 sc = kmalloc(struct_size(sc, stripe, stripes), GFP_KERNEL); in stripe_ctr()
179 dm_put_device(ti, sc->stripe[i].dev); in stripe_ctr()
183 atomic_set(&(sc->stripe[i].error_count), 0); in stripe_ctr()
197 dm_put_device(ti, sc->stripe[i].dev); in stripe_dtr()
204 uint32_t *stripe, sector_t *result) in stripe_map_sector() argument
[all …]
Draid5.c563 static void stripe_set_idx(sector_t stripe, struct r5conf *conf, int previous,
2917 sector_t stripe, stripe2; in raid5_compute_sector() local
2942 stripe = chunk_number; in raid5_compute_sector()
2943 *dd_idx = sector_div(stripe, data_disks); in raid5_compute_sector()
2944 stripe2 = stripe; in raid5_compute_sector()
3111 new_sector = (sector_t)stripe * sectors_per_chunk + chunk_offset; in raid5_compute_sector()
3125 sector_t stripe; in raid5_compute_blocknr() local
3133 stripe = new_sector; in raid5_compute_blocknr()
3221 chunk_number = stripe * data_disks + i; in raid5_compute_blocknr()
3532 static void stripe_set_idx(sector_t stripe, struct r5conf *conf, int previous, in stripe_set_idx() argument
[all …]
DMakefile6 dm-mod-y += dm.o dm-table.o dm-target.o dm-linear.o dm-stripe.o \
/kernel/linux/linux-5.10/fs/btrfs/
Draid56.c616 static int rbio_stripe_page_index(struct btrfs_raid_bio *rbio, int stripe, in rbio_stripe_page_index() argument
619 return stripe * rbio->stripe_npages + index; in rbio_stripe_page_index()
626 static struct page *rbio_stripe_page(struct btrfs_raid_bio *rbio, int stripe, in rbio_stripe_page() argument
629 return rbio->stripe_pages[rbio_stripe_page_index(rbio, stripe, index)]; in rbio_stripe_page()
1097 struct btrfs_bio_stripe *stripe; in rbio_add_io_page() local
1100 stripe = &rbio->bbio->stripes[stripe_nr]; in rbio_add_io_page()
1101 disk_start = stripe->physical + (page_index << PAGE_SHIFT); in rbio_add_io_page()
1104 if (!stripe->dev->bdev) in rbio_add_io_page()
1117 last->bi_disk == stripe->dev->bdev->bd_disk && in rbio_add_io_page()
1118 last->bi_partno == stripe->dev->bdev->bd_partno) { in rbio_add_io_page()
[all …]
Dextent_map.c363 struct btrfs_bio_stripe *stripe = &map->stripes[i]; in extent_map_device_set_bits() local
364 struct btrfs_device *device = stripe->dev; in extent_map_device_set_bits()
366 set_extent_bits_nowait(&device->alloc_state, stripe->physical, in extent_map_device_set_bits()
367 stripe->physical + stripe_size - 1, bits); in extent_map_device_set_bits()
378 struct btrfs_bio_stripe *stripe = &map->stripes[i]; in extent_map_device_clear_bits() local
379 struct btrfs_device *device = stripe->dev; in extent_map_device_clear_bits()
381 __clear_extent_bit(&device->alloc_state, stripe->physical, in extent_map_device_clear_bits()
382 stripe->physical + stripe_size - 1, bits, in extent_map_device_clear_bits()
/kernel/linux/linux-5.10/drivers/staging/media/ipu3/
Dipu3-css-params.c1008 osys->stripe[s].crop_top[pin] = in imgu_css_osys_calc()
1010 osys->stripe[s].input_width = in imgu_css_osys_calc()
1012 osys->stripe[s].input_height = in imgu_css_osys_calc()
1014 osys->stripe[s].block_height = in imgu_css_osys_calc()
1016 osys->stripe[s].block_width = in imgu_css_osys_calc()
1018 osys->stripe[s].output_width[pin] = in imgu_css_osys_calc()
1020 osys->stripe[s].output_height[pin] = in imgu_css_osys_calc()
1025 osys->stripe[s].crop_left[pin] = in imgu_css_osys_calc()
1027 osys->stripe[s].output_offset[pin] = in imgu_css_osys_calc()
1035 osys->stripe[s].crop_left[pin] = 0; in imgu_css_osys_calc()
[all …]
/kernel/linux/linux-5.10/drivers/md/bcache/
Dwriteback.c556 int stripe; in bcache_dev_sectors_dirty_add() local
561 stripe = offset_to_stripe(d, offset); in bcache_dev_sectors_dirty_add()
562 if (stripe < 0) in bcache_dev_sectors_dirty_add()
577 if (stripe >= d->nr_stripes) in bcache_dev_sectors_dirty_add()
581 d->stripe_sectors_dirty + stripe); in bcache_dev_sectors_dirty_add()
583 set_bit(stripe, d->full_dirty_stripes); in bcache_dev_sectors_dirty_add()
585 clear_bit(stripe, d->full_dirty_stripes); in bcache_dev_sectors_dirty_add()
589 stripe++; in bcache_dev_sectors_dirty_add()
608 int stripe; in refill_full_stripes() local
611 stripe = offset_to_stripe(&dc->disk, KEY_OFFSET(&buf->last_scanned)); in refill_full_stripes()
[all …]
Dwriteback.h78 int stripe = offset_to_stripe(&dc->disk, offset); in bcache_dev_stripe_dirty() local
80 if (stripe < 0) in bcache_dev_stripe_dirty()
84 if (atomic_read(dc->disk.stripe_sectors_dirty + stripe)) in bcache_dev_stripe_dirty()
91 stripe++; in bcache_dev_stripe_dirty()
/kernel/linux/linux-5.10/Documentation/driver-api/md/
Draid5-ppl.rst6 addressed by PPL is that after a dirty shutdown, parity of a particular stripe
15 Partial parity for a write operation is the XOR of stripe data chunks not
18 the stripe, consistent with its state before the write operation, regardless of
20 this stripe is missing, this updated parity can be used to recover its
29 stripe. It does not require a dedicated journaling drive. Write performance is
36 silent data corruption. If a dirty disk of a stripe is lost, no PPL recovery is
37 performed for this stripe (parity is not updated). So it is possible to have
38 arbitrary data in the written part of a stripe if that disk is lost. In such
Draid5-cache.rst27 and parity don't match. The reason is that a stripe write involves several RAID
52 write. If a write crosses all RAID disks of a stripe, we call it full-stripe
53 write. For non-full-stripe writes, MD must read old data before the new parity
57 RAID disks only after the data becomes a full stripe write. This will
101 release the memory cache. The flush conditions could be stripe becomes a full
102 stripe write, free cache disk space is low or free in-kernel memory cache space
107 data and data. If MD finds a stripe with data and valid parities (1 parity for
/kernel/linux/linux-5.10/fs/nfs/blocklayout/
Ddev.c127 p = xdr_decode_hyper(p, &b->stripe.chunk_size); in nfs4_block_decode_volume()
128 b->stripe.volumes_count = be32_to_cpup(p++); in nfs4_block_decode_volume()
129 if (b->stripe.volumes_count > PNFS_BLOCK_MAX_DEVICES) { in nfs4_block_decode_volume()
130 dprintk("Too many volumes: %d\n", b->stripe.volumes_count); in nfs4_block_decode_volume()
134 p = xdr_inline_decode(xdr, b->stripe.volumes_count * 4); in nfs4_block_decode_volume()
137 for (i = 0; i < b->stripe.volumes_count; i++) in nfs4_block_decode_volume()
138 b->stripe.volumes[i] = be32_to_cpup(p++); in nfs4_block_decode_volume()
453 d->children = kcalloc(v->stripe.volumes_count, in bl_parse_stripe()
458 for (i = 0; i < v->stripe.volumes_count; i++) { in bl_parse_stripe()
460 volumes, v->stripe.volumes[i], gfp_mask); in bl_parse_stripe()
[all …]
Dblocklayout.h83 } stripe; member
/kernel/linux/linux-5.10/Documentation/admin-guide/device-mapper/
Dunstriped.rst14 <number of stripes> <chunk size> <stripe #> <dev_path> <offset>
25 <stripe #>
26 The stripe number within the device that corresponds to physical
33 An example of undoing an existing dm-stripe
88 in a 256k stripe across the two cores::
Dstriped.rst2 dm-stripe
Ddm-raid.rst83 "stripe size". It is the only mandatory parameter and
194 starting at data_offset to fill up a new stripe with the larger
196 and write that new stripe to offset 0. Same will be applied to all
355 of a RAID 4/5/6 stripe and if subsequent read results are not
416 1.14.0 Fix reshape race on small devices. Fix stripe adding reshape
Ddm-log.rst7 inconsistent because a RAID stripe is currently being operated on or
/kernel/linux/linux-5.10/drivers/staging/media/atomisp/pci/isp/modes/interface/
Disp_const.h85 #define CEIL_ROUND_DIV_STRIPE(width, stripe, padding) \ argument
86 …CEIL_MUL(padding + CEIL_DIV(width - padding, stripe), ((ENABLE_RAW_BINNING || ENABLE_FIXED_BAYER_D…
/kernel/linux/linux-5.10/Documentation/filesystems/
Dntfs.rst15 - Using NTFS volume and stripe sets
35 For fault tolerance and raid support (i.e. volume and stripe sets), you can
245 Using NTFS volume and stripe sets
248 For support of volume and stripe sets, you can either use the kernel's
257 You will need to create a table of the components of the volume/stripe set and
262 though untested, there is no reason why stripe sets, i.e. raid level 0, and
397 Linear volume sets, i.e. linear raid, as well as stripe sets, i.e. raid level
404 NTFS volume/stripe you are configuring in /etc/raidtab as the persistent
407 Windows by default uses a stripe chunk size of 64k, so you probably want the
410 For example, if you have a stripe set consisting of two partitions /dev/hda5
[all …]
/kernel/linux/linux-5.10/Documentation/admin-guide/
Dxfs.rst134 stripe unit configured at **mkfs(8)** time.
147 Data allocations will not be aligned at stripe unit
183 Used to specify the stripe unit and width for a RAID device
184 or a stripe volume. "value" must be specified in 512-byte
200 Data allocations will be rounded up to stripe width boundaries
202 size is larger than the stripe width size.
/kernel/linux/linux-5.10/Documentation/scsi/
Darcmsr_spec.rst421 byte 8 stripe size
768 10:new stripe size
811 byte 29 stripe size
835 byte 29 new stripe size
DChangeLog.ips121 8K stripe size.
/kernel/linux/linux-5.10/sound/hda/
Dhdac_stream.c99 if (azx_dev->stripe) { in snd_hdac_stream_start()
123 if (azx_dev->stripe) in snd_hdac_stream_clear()
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-block138 block size. For RAID arrays it is often the stripe
151 usually the stripe width or the internal track size. A
305 stripe segment. For a zoned block device, either
/kernel/linux/patches/linux-4.19/prebuilts/usr/include/linux/
Dbtrfs_tree.h155 struct btrfs_stripe stripe; member
/kernel/linux/linux-5.10/include/uapi/linux/
Dbtrfs_tree.h442 struct btrfs_stripe stripe; member

12