Production hosts using the devicemapper storage driver must use direct-lvm For production systems, seeĬonfigure direct-lvm mode for production.
This is indicated by the fact that the Data loop fileĪnd a Metadata loop file are on files under This host is running in loop-lvm mode, which is not supported on Metadata loop file: /var/lib/docker/devicemapper/metadata Therefore only be used to perform rudimentary testing prior to configuringĬonfigure direct-lvm mode for production.ĭata loop file: /var/lib/docker/devicemapper/data Missing user space packages, kernel drivers, etc.) ahead of attempting the moreĬomplex set up required to enable direct-lvm mode. However, setting up loop-lvm mode can help identify basic issues (such as Use of loopback devices can also introduce race conditions. However, the addition of the loopback mechanism, and interaction with the OSįilesystem layer, means that IO operations can be slow and resource-intensive. Read from and written to as if they were an actual physical disk or block Use of a ‘loopback’ mechanism that allows files on the local disk to be This configuration is only appropriate for testing. Use docker save to save containers,Īnd push existing images to Docker Hub or a private repository, so you doĬonfigure Docker with the devicemapper storage driverīefore following these procedures, you must first meet all the
The block level, rather than the file level. The devicemapper driver uses block devices dedicated to Docker and operates at However, specific configuration is required to use it with Storage driver as devicemapper, and the kernel framework as Device Mapper.įor the systems where it is supported, devicemapper support is included in Leverages the thin provisioning and snapshotting capabilities of this frameworkįor image and container management. + * delay between soft reset and loopback enablement.Device Mapper is a kernel-based framework that underpins many advanced
+ /* FIXME: Based on trial and error test, it seem 1G need to have + /* Need soft reset to have speed configuration takes effect */ + phy_modify_paged(phydev, MII_MARVELL_MSCR_PAGE, + phy_modify(phydev, MII_BMCR, ~0, bmcr_ctl) +static int marvell_loopback(struct phy_device *phydev, bool enable) #define -1932,6 +1934,48 static void marvell_get_stats(struct phy_device *phydev, For loopback enabled, add bit-6 and bit-13 configuration in both PageĠ Register 0 and Register 21. Signed-off-by: Mohammad Athari Bin Ismail Tested working on Marvell88E1510 PHY for all speeds (1000/100/10Mbps).įIXME: Based on trial and error test, it seem 1G need to have delay betweenįixes: 014068dcb5b1 ("net: phy: genphy_loopback: add link speed configuration") Register 21 (MAC Specific Control Register 2) according to speed of Register), it is also required to configure same bits in BesidesĬonfiguring bit-6 and bit-13 in Register 0 (Copper Control Miller, Jakub Kicinski, Oleksij Rempel,Ĭc: netdev, linux-kernel,, stableĮxisting genphy_loopback() is not applicable for Marvell PHY. 13:12 ` Russell King (Oracle) 0 siblings, 1 reply 3+ messages in threadįrom: Mohammad Athari Bin Ismail 9:33 UTC ( / raw)
Net: phy: marvell: add Marvell specific PHY loopback Netdev Archive on help / color / mirror / Atom feed * net: phy: marvell: add Marvell specific PHY loopback 9:33 Mohammad Athari Bin Ismail