Skip to content

K
Kernel

openeuler / Kernel
大约 1 年 前同步成功

通知 5
Star 0
Fork 0
K
Kernel

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 15 10月, 2011 6 次提交
    • B
      ore: Support for partial component table · 3bd98568
      由 Boaz Harrosh 提交于 
      Users like the objlayout-driver would like to only pass
a partial device table that covers the IO in question.
For example exofs divides the file into raid-group-sized
chunks and only serves group_width number of devices at
a time.

The partiality is communicated by setting
ore_componets->first_dev and the array covers all logical
devices from oc->first_dev upto (oc->first_dev + oc->numdevs)

The ore_comp_dev() API receives a logical device index
and returns the actual present device in the table.
An out-of-range dev_index will BUG.

Logical device index is the theoretical device index as if
all the devices of a file are present. .i.e:
	total_devs = group_width * mirror_p1 * group_count
	0 <= dev_index < total_devs
Signed-off-by: NBoaz Harrosh <bharrosh@panasas.com>
      3bd98568
    • B
      ore: Support for short read/writes · bbf9a31b
      由 Boaz Harrosh 提交于 
      Memory conditions and max_bio constraints might cause us to
not comply to the full length of the requested IO. Instead of
failing the complete IO we can issue a shorter read/write and
report how much was actually executed in the ios->length
member.

All users must check ios->length at IO_done or upon return of
ore_read/write and re-issue the reminder of the bytes. Because
other wise there is no error returned like before.

This is part of the effort to support the pnfs-obj layout driver.
Signed-off-by: NBoaz Harrosh <bharrosh@panasas.com>
      bbf9a31b
    • B
      exofs: Support for short read/writes · 154a9300
      由 Boaz Harrosh 提交于 
      If at read/write_done the actual IO was shorter then requested,
reported in returned ios->length. It is not an error. The reminder
of the pages should just be unlocked but not marked uptodate or
end_page_writeback. They will be re issued later by the VFS.
Signed-off-by: NBoaz Harrosh <bharrosh@panasas.com>
      154a9300
    • B
      ore: Remove check for ios->kern_buff in _prepare_for_striping to later · 6851a5e5
      由 Boaz Harrosh 提交于 
      Move the check and preparation of the ios->kern_buff case to
later inside _write_mirror().

Since read was never used with ios->kern_buff its support is removed
instead of fixed.
Signed-off-by: NBoaz Harrosh <bharrosh@panasas.com>
      6851a5e5
    • B
      ore: cleanup: Embed an ore_striping_info inside ore_io_state · 98260754
      由 Boaz Harrosh 提交于 
      Now that each ore_io_state covers only a single raid group.
A single striping_info math is needed. Embed one inside
ore_io_state to cache the calculation results and eliminate
an extra call.

Also the outer _prepare_for_striping is removed since it does nothing.
Signed-off-by: NBoaz Harrosh <bharrosh@panasas.com>
      98260754
    • B
      ore: Only IO one group at a time (API change) · b916c5cd
      由 Boaz Harrosh 提交于 
      Usually a single IO is confined to one group of devices
(group_width) and at the boundary of a raid group it can
spill into a second group. Current code would allocate a
full device_table size array at each io_state so it can
comply to requests that span two groups. Needless to say
that is very wasteful, specially when device_table count
can get very large (hundreds even thousands), while a
group_width is usually 8 or 10.

* Change ore API to trim on IO that spans two raid groups.
  The user passes offset+length to ore_get_rw_state, the
  ore might trim on that length if spanning a group boundary.
  The user must check ios->length or ios->nrpages to see
  how much IO will be preformed. It is the responsibility
  of the user to re-issue the reminder of the IO.

* Modify exofs To copy spilled pages on to the next IO.
  This means one last kick is needed after all coalescing
  of pages is done.
Signed-off-by: NBoaz Harrosh <bharrosh@panasas.com>
      b916c5cd
  3. 04 10月, 2011 1 次提交
    • B
      ore/exofs: Change the type of the devices array (API change) · d866d875
      由 Boaz Harrosh 提交于 
      In the pNFS obj-LD the device table at the layout level needs
to point to a device_cache node, where it is possible and likely
that many layouts will point to the same device-nodes.

In Exofs we have a more orderly structure where we have a single
array of devices that repeats twice for a round-robin view of the
device table

This patch moves to a model that can be used by the pNFS obj-LD
where struct ore_components holds an array of ore_dev-pointers.
(ore_dev is newly defined and contains a struct osd_dev *od
 member)

Each pointer in the array of pointers will point to a bigger
user-defined dev_struct. That can be accessed by use of the
container_of macro.

In Exofs an __alloc_dev_table() function allocates the
ore_dev-pointers array as well as an exofs_dev array, in one
allocation and does the addresses dance to set everything pointing
correctly. It still keeps the double allocation trick for the
inodes round-robin view of the table.

The device table is always allocated dynamically, also for the
single device case. So it is unconditionally freed at umount.
Signed-off-by: NBoaz Harrosh <bharrosh@panasas.com>
      d866d875
  5. 03 10月, 2011 5 次提交
  7. 22 9月, 2011 1 次提交
  9. 13 9月, 2011 8 次提交
  11. 12 9月, 2011 3 次提交
  13. 11 9月, 2011 16 次提交