allow for persistent l2arc #925
Comments
|
Seems there's an implementation of this in illumos going through final testing now: |
|
Once it's merged in to Illumos in it's final form and soaks for a while I'm sure we'll pick this up. |
|
Are there anyone interested in doing this? Otherwise I'll try porting and keeping track of this patch set. |
|
@yshui Nobody on the Linux side I know if working on this right now. If you can port the upstream patches and keep them up current that would be great. I'm sure @skiselkov would appreciate any additional testing and feedback you can provide. |
For details, see: https://www.illumos.org/issues/3525 v2: Change two KM_SLEEP to KM_PUSHPAGE. v3: Change one more KM_SLEEP. v4: Fix log buffer alignment in l2arc_dev_log_commit. v5: Fix style. v6: l2arc vdev can go away, remove ASSERT in l2arc_spa_rebuild_start. Close openzfs#925 Ported-by: Yuxuan Shui <yshuiv7@gmail.com>
|
From irc://chat.freenode.net/#illumos today:
|
|
@grahamperrin thanks for the pointer ! Nexenta/illumos-nexenta@f0a9ee9 NEX-3514 Implement persistent L2ARC Nexenta/illumos-nexenta@8872632 NEX-3514 Implement persistent L2ARC - fix build breakage in libzpool. Nexenta/illumos-nexenta@9498bb1 NEX-3514 Implement persistent L2ARC - fix build breakage in libzpool (v2). https://github.com/Nexenta/illumos-nexenta/commits/master?page=4 |
|
illumos 3525 is now in code review. |
|
Updated progress at https://reviews.csiden.org/r/267/ |
|
@behlendorf what does closing of this mean? it has been integrated/ported already? it will never be? |
|
The intention was to pick up this work once it was finalized and merged for illumos. |
|
@behlendorf could you mark it a duplicate of #3744, even if this is chronologicallty the oldest? |
This commit makes the L2ARC persistent across reboots. We implement a light-weight persistent L2ARC metadata structure that allows L2ARC contents to be recovered after a reboot. This significantly eases the impact a reboot has on read performance on systems with large caches. Reviewed-by: Matthew Ahrens <mahrens@delphix.com> Reviewed-by: George Wilson <gwilson@delphix.com> Reviewed-by: Ryan Moeller <ryan@iXsystems.com> Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Co-authored-by: Saso Kiselkov <skiselkov@gmail.com> Co-authored-by: Jorgen Lundman <lundman@lundman.net> Co-authored-by: George Amanakis <gamanakis@gmail.com> Ported-by: Yuxuan Shui <yshuiv7@gmail.com> Signed-off-by: George Amanakis <gamanakis@gmail.com> Closes #925 Closes #1823 Closes #2672 Closes #3744 Closes #9582
|
@behlendorf is this going to 0.8 series, or is it planned only for openzfs v2? |
|
It's planned for OpenZFS 2.0. |
This commit makes the L2ARC persistent across reboots. We implement a light-weight persistent L2ARC metadata structure that allows L2ARC contents to be recovered after a reboot. This significantly eases the impact a reboot has on read performance on systems with large caches. Reviewed-by: Matthew Ahrens <mahrens@delphix.com> Reviewed-by: George Wilson <gwilson@delphix.com> Reviewed-by: Ryan Moeller <ryan@iXsystems.com> Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Co-authored-by: Saso Kiselkov <skiselkov@gmail.com> Co-authored-by: Jorgen Lundman <lundman@lundman.net> Co-authored-by: George Amanakis <gamanakis@gmail.com> Ported-by: Yuxuan Shui <yshuiv7@gmail.com> Signed-off-by: George Amanakis <gamanakis@gmail.com> Closes openzfs#925 Closes openzfs#1823 Closes openzfs#2672 Closes openzfs#3744 Closes openzfs#9582
https://groups.google.com/a/zfsonlinux.org/forum/?fromgroups=#!topic/zfs-discuss/eSYYLdx73r4
References request and a suggestion on how it might be done.
The text was updated successfully, but these errors were encountered: