From: Brian Geffon <hidden> Date: 2021-09-17 21:07:08
This change introduces a new sysfs file for the zram idle interface.
The current idle interface has only a single mode "all." This is
severely limiting in that it requires that you have the foresight
to know that you'll want to have pages idle at some point in the future
and forces the user to mark everything as idle.
This new proposed file idle_aged takes a single integer argument which
represents the age of the pages (in seconds since access) to mark as idle.
Because it requires accessed tracking it is only enabled when
CONFIG_ZRAM_MEMORY_TRACKING is enabled. There are a few
reasons why this is being proposed as a new file rather than extending
the existing file. The first reason is that it wouldn't allow more code
sharing as this change already refactors the existing code to do so.
Secondly, having a standalone file allows a caller to quickly check if this
idle_aged interface is supported. Finally, it simplifies the parsing
logic because now you only need to parse an int rather than more complex
logic which would need to parse things like "aged 50."
Signed-off-by: Brian Geffon <redacted>
---
Documentation/admin-guide/blockdev/zram.rst | 11 ++-
drivers/block/zram/zram_drv.c | 75 +++++++++++++++++----
2 files changed, 70 insertions(+), 16 deletions(-)
@@ -209,6 +209,8 @@ compact WO trigger memory compaction debug_stat RO this file is used for zram debugging purposes backing_dev RW set up backend storage for zram to write out idle WO mark allocated slot as idle+idle_aged WO mark allocated slot older than 'age' seconds+ as idle (see later) ====================== ====== ===============================================
@@ -325,8 +327,13 @@ as idle:: echo all > /sys/block/zramX/idle-From now on, any pages on zram are idle pages. The idle mark-will be removed until someone requests access of the block.+Alternatively if the config option CONFIG_ZRAM_MEMORY_TRACKING is enabled+the idle_aged interface can be used to mark only pages older than 'age'+seconds as idle::++ echo 86400 > /sys/block/zramX/idle_aged++The idle mark will be removed until someone requests access of the block. IOW, unless there is access request, those pages are still idle pages. Admin can request writeback of those idle pages at right timing via::
From: Minchan Kim <minchan@kernel.org> Date: 2021-09-21 02:03:16
On Fri, Sep 17, 2021 at 02:06:40PM -0700, Brian Geffon wrote:
This change introduces a new sysfs file for the zram idle interface.
The current idle interface has only a single mode "all." This is
severely limiting in that it requires that you have the foresight
to know that you'll want to have pages idle at some point in the future
and forces the user to mark everything as idle.
This new proposed file idle_aged takes a single integer argument which
represents the age of the pages (in seconds since access) to mark as idle.
Because it requires accessed tracking it is only enabled when
CONFIG_ZRAM_MEMORY_TRACKING is enabled. There are a few
reasons why this is being proposed as a new file rather than extending
the existing file. The first reason is that it wouldn't allow more code
sharing as this change already refactors the existing code to do so.
Secondly, having a standalone file allows a caller to quickly check if this
idle_aged interface is supported. Finally, it simplifies the parsing
logic because now you only need to parse an int rather than more complex
logic which would need to parse things like "aged 50."
I am not convinced with create new sysfs node to support the aged time.
The reason I used the "all" was to have the room to support the aged
time as you suggested for the future. IOW, If the value is not "all" but
"only numeric", we could take it as "aged" value.
And then, we can write up in the doc "The age-based idle" supported by
kernel version 5.XX with CONFIG_ZRAM_MEMORY_TRACKING.
I understand the separate interface will make code simple but not sure
it's worth to create another sysfs knob.
Any thoughts?
@@ -209,6 +209,8 @@ compact WO trigger memory compaction debug_stat RO this file is used for zram debugging purposes backing_dev RW set up backend storage for zram to write out idle WO mark allocated slot as idle+idle_aged WO mark allocated slot older than 'age' seconds+ as idle (see later) ====================== ====== ===============================================
@@ -325,8 +327,13 @@ as idle:: echo all > /sys/block/zramX/idle-From now on, any pages on zram are idle pages. The idle mark-will be removed until someone requests access of the block.+Alternatively if the config option CONFIG_ZRAM_MEMORY_TRACKING is enabled+the idle_aged interface can be used to mark only pages older than 'age'+seconds as idle::++ echo 86400 > /sys/block/zramX/idle_aged++The idle mark will be removed until someone requests access of the block. IOW, unless there is access request, those pages are still idle pages. Admin can request writeback of those idle pages at right timing via::
I am not sure it's a good idea to compare those ktime_t directly
without using the ktime API(e.g., ktime_after or ktime_before).
Maybe, we can get age_sec ktime_t directly as a argument and then
use the ktime API with ktime_get_boottime to compare them.
From: Brian Geffon <hidden> Date: 2021-09-21 02:03:47
On Mon, Sep 20, 2021 at 5:15 PM Minchan Kim [off-list ref] wrote:
On Fri, Sep 17, 2021 at 02:06:40PM -0700, Brian Geffon wrote:
quoted
This change introduces a new sysfs file for the zram idle interface.
The current idle interface has only a single mode "all." This is
severely limiting in that it requires that you have the foresight
to know that you'll want to have pages idle at some point in the future
and forces the user to mark everything as idle.
This new proposed file idle_aged takes a single integer argument which
represents the age of the pages (in seconds since access) to mark as idle.
Because it requires accessed tracking it is only enabled when
CONFIG_ZRAM_MEMORY_TRACKING is enabled. There are a few
reasons why this is being proposed as a new file rather than extending
the existing file. The first reason is that it wouldn't allow more code
sharing as this change already refactors the existing code to do so.
Secondly, having a standalone file allows a caller to quickly check if this
idle_aged interface is supported. Finally, it simplifies the parsing
logic because now you only need to parse an int rather than more complex
logic which would need to parse things like "aged 50."
I am not convinced with create new sysfs node to support the aged time.
The reason I used the "all" was to have the room to support the aged
time as you suggested for the future. IOW, If the value is not "all" but
"only numeric", we could take it as "aged" value.
And then, we can write up in the doc "The age-based idle" supported by
kernel version 5.XX with CONFIG_ZRAM_MEMORY_TRACKING.
I understand the separate interface will make code simple but not sure
it's worth to create another sysfs knob.
Any thoughts?
Sure, Sergey had similar feedback on that. I'll mail a new patch that
uses the existing knob but attempts to parse the input as an integer.
@@ -209,6 +209,8 @@ compact WO trigger memory compaction debug_stat RO this file is used for zram debugging purposes backing_dev RW set up backend storage for zram to write out idle WO mark allocated slot as idle+idle_aged WO mark allocated slot older than 'age' seconds+ as idle (see later) ====================== ====== ===============================================
@@ -325,8 +327,13 @@ as idle:: echo all > /sys/block/zramX/idle-From now on, any pages on zram are idle pages. The idle mark-will be removed until someone requests access of the block.+Alternatively if the config option CONFIG_ZRAM_MEMORY_TRACKING is enabled+the idle_aged interface can be used to mark only pages older than 'age'+seconds as idle::++ echo 86400 > /sys/block/zramX/idle_aged++The idle mark will be removed until someone requests access of the block. IOW, unless there is access request, those pages are still idle pages. Admin can request writeback of those idle pages at right timing via::
I am not sure it's a good idea to compare those ktime_t directly
without using the ktime API(e.g., ktime_after or ktime_before).
Maybe, we can get age_sec ktime_t directly as a argument and then
use the ktime API with ktime_get_boottime to compare them.
I will make this change in the next version of the patch.
From: Brian Geffon <hidden> Date: 2021-09-21 18:52:00
This change introduces an aged idle interface to the existing
idle sysfs file for zram.
When CONFIG_ZRAM_MEMORY_TRACKING is enabled the idle file
now also accepts an integer argument. This integer is the
age (in seconds) of pages to mark as idle. The idle file
still supports 'all' as it always has. This new approach
allows for much more control over which pages get marked
as idle.
Signed-off-by: Brian Geffon <redacted>
---
Documentation/admin-guide/blockdev/zram.rst | 8 +++
drivers/block/zram/zram_drv.c | 60 +++++++++++++++------
2 files changed, 52 insertions(+), 16 deletions(-)
@@ -328,6 +328,14 @@ as idle:: From now on, any pages on zram are idle pages. The idle mark will be removed until someone requests access of the block. IOW, unless there is access request, those pages are still idle pages.+Additionally, when CONFIG_ZRAM_MEMORY_TRACKING is enabled pages can be+marked as idle based on how long (in seconds) it's been since they were+last accessed, in seconds::++ echo 86400 > /sys/block/zramX/idle++In this example all pages which haven't been accessed in more than 86400+seconds (one day) will be marked idle. Admin can request writeback of those idle pages at right timing via::
@@ -314,14 +308,48 @@ static ssize_t idle_store(struct device *dev,*/zram_slot_lock(zram,index);if(zram_allocated(zram,index)&&-!zram_test_flag(zram,index,ZRAM_UNDER_WB))-zram_set_flag(zram,index,ZRAM_IDLE);+!zram_test_flag(zram,index,ZRAM_UNDER_WB)){+#ifdef CONFIG_ZRAM_MEMORY_TRACKING+is_idle=(!cutoff||ktime_after(cutoff,zram->table[index].ac_time));+#endif+if(is_idle)+zram_set_flag(zram,index,ZRAM_IDLE);+}zram_slot_unlock(zram,index);}+}-up_read(&zram->init_lock);+staticssize_tidle_store(structdevice*dev,+structdevice_attribute*attr,constchar*buf,size_tlen)+{+structzram*zram=dev_to_zram(dev);+u64age_sec;+ktime_tcutoff_time=0;+ssize_trv=-EINVAL;-returnlen;+if(!sysfs_streq(buf,"all")){+#ifdef CONFIG_ZRAM_MEMORY_TRACKING+/* If it did not parse as 'all' try to treat it as an integer */+if(!kstrtoull(buf,10,&age_sec))+cutoff_time=ktime_sub(ktime_get_boottime(),+ns_to_ktime(age_sec*NSEC_PER_SEC));+else+#endif+gotoout;+}++down_read(&zram->init_lock);+if(!init_done(zram))+gotoout_unlock;++/* A age_sec of 0 marks everything as idle, this is the "all" behavior */+mark_idle(zram,cutoff_time);+rv=len;++out_unlock:+up_read(&zram->init_lock);+out:+returnrv;}#ifdef CONFIG_ZRAM_WRITEBACK
From: Brian Geffon <hidden> Date: 2021-09-21 19:43:57
This change introduces an aged idle interface to the existing
idle sysfs file for zram.
When CONFIG_ZRAM_MEMORY_TRACKING is enabled the idle file
now also accepts an integer argument. This integer is the
age (in seconds) of pages to mark as idle. The idle file
still supports 'all' as it always has. This new approach
allows for much more control over which pages get marked
as idle.
v2 -> v3:
- Correct unused variable warning when
CONFIG_ZRAM_MEMORY_TRACKING is not enabled.
v1 -> v2:
- Switch to using existing idle file.
- Dont compare ktime directly.
Signed-off-by: Brian Geffon <redacted>
---
Documentation/admin-guide/blockdev/zram.rst | 8 +++
drivers/block/zram/zram_drv.c | 60 +++++++++++++++------
2 files changed, 52 insertions(+), 16 deletions(-)
@@ -328,6 +328,14 @@ as idle:: From now on, any pages on zram are idle pages. The idle mark will be removed until someone requests access of the block. IOW, unless there is access request, those pages are still idle pages.+Additionally, when CONFIG_ZRAM_MEMORY_TRACKING is enabled pages can be+marked as idle based on how long (in seconds) it's been since they were+last accessed, in seconds::++ echo 86400 > /sys/block/zramX/idle++In this example all pages which haven't been accessed in more than 86400+seconds (one day) will be marked idle. Admin can request writeback of those idle pages at right timing via::
@@ -314,14 +308,48 @@ static ssize_t idle_store(struct device *dev,*/zram_slot_lock(zram,index);if(zram_allocated(zram,index)&&-!zram_test_flag(zram,index,ZRAM_UNDER_WB))-zram_set_flag(zram,index,ZRAM_IDLE);+!zram_test_flag(zram,index,ZRAM_UNDER_WB)){+#ifdef CONFIG_ZRAM_MEMORY_TRACKING+is_idle=(!cutoff||ktime_after(cutoff,zram->table[index].ac_time));+#endif+if(is_idle)+zram_set_flag(zram,index,ZRAM_IDLE);+}zram_slot_unlock(zram,index);}+}-up_read(&zram->init_lock);+staticssize_tidle_store(structdevice*dev,+structdevice_attribute*attr,constchar*buf,size_tlen)+{+structzram*zram=dev_to_zram(dev);+ktime_tcutoff_time=0;+ssize_trv=-EINVAL;-returnlen;+if(!sysfs_streq(buf,"all")){+#ifdef CONFIG_ZRAM_MEMORY_TRACKING+u64age_sec;+/* If it did not parse as 'all' try to treat it as an integer */+if(!kstrtoull(buf,10,&age_sec))+cutoff_time=ktime_sub(ktime_get_boottime(),+ns_to_ktime(age_sec*NSEC_PER_SEC));+else+#endif+gotoout;+}++down_read(&zram->init_lock);+if(!init_done(zram))+gotoout_unlock;++/* A age_sec of 0 marks everything as idle, this is the "all" behavior */+mark_idle(zram,cutoff_time);+rv=len;++out_unlock:+up_read(&zram->init_lock);+out:+returnrv;}#ifdef CONFIG_ZRAM_WRITEBACK
From: Minchan Kim <minchan@kernel.org> Date: 2021-09-23 00:09:41
On Tue, Sep 21, 2021 at 12:43:36PM -0700, Brian Geffon wrote:
quoted hunk
This change introduces an aged idle interface to the existing
idle sysfs file for zram.
When CONFIG_ZRAM_MEMORY_TRACKING is enabled the idle file
now also accepts an integer argument. This integer is the
age (in seconds) of pages to mark as idle. The idle file
still supports 'all' as it always has. This new approach
allows for much more control over which pages get marked
as idle.
v2 -> v3:
- Correct unused variable warning when
CONFIG_ZRAM_MEMORY_TRACKING is not enabled.
v1 -> v2:
- Switch to using existing idle file.
- Dont compare ktime directly.
Signed-off-by: Brian Geffon <redacted>
---
Documentation/admin-guide/blockdev/zram.rst | 8 +++
drivers/block/zram/zram_drv.c | 60 +++++++++++++++------
2 files changed, 52 insertions(+), 16 deletions(-)
@@ -328,6 +328,14 @@ as idle:: From now on, any pages on zram are idle pages. The idle mark will be removed until someone requests access of the block. IOW, unless there is access request, those pages are still idle pages.+Additionally, when CONFIG_ZRAM_MEMORY_TRACKING is enabled pages can be+marked as idle based on how long (in seconds) it's been since they were+last accessed, in seconds::++ echo 86400 > /sys/block/zramX/idle++In this example all pages which haven't been accessed in more than 86400+seconds (one day) will be marked idle. Admin can request writeback of those idle pages at right timing via::
@@ -314,14 +308,48 @@ static ssize_t idle_store(struct device *dev,*/zram_slot_lock(zram,index);if(zram_allocated(zram,index)&&-!zram_test_flag(zram,index,ZRAM_UNDER_WB))-zram_set_flag(zram,index,ZRAM_IDLE);+!zram_test_flag(zram,index,ZRAM_UNDER_WB)){+#ifdef CONFIG_ZRAM_MEMORY_TRACKING+is_idle=(!cutoff||ktime_after(cutoff,zram->table[index].ac_time));+#endif+if(is_idle)+zram_set_flag(zram,index,ZRAM_IDLE);+}zram_slot_unlock(zram,index);}+}-up_read(&zram->init_lock);+staticssize_tidle_store(structdevice*dev,+structdevice_attribute*attr,constchar*buf,size_tlen)+{+structzram*zram=dev_to_zram(dev);+ktime_tcutoff_time=0;+ssize_trv=-EINVAL;-returnlen;+if(!sysfs_streq(buf,"all")){+#ifdef CONFIG_ZRAM_MEMORY_TRACKING+u64age_sec;+/* If it did not parse as 'all' try to treat it as an integer */+if(!kstrtoull(buf,10,&age_sec))
nit:
Do we need such limit base which work with only 10 base?
Passing 0 would give more flexibility.
Otherwise, looks good to me.
Thanks, Brian.
+ cutoff_time = ktime_sub(ktime_get_boottime(),
+ ns_to_ktime(age_sec * NSEC_PER_SEC));
+ else
+#endif
+ goto out;
+ }
+
+ down_read(&zram->init_lock);
+ if (!init_done(zram))
+ goto out_unlock;
+
+ /* A age_sec of 0 marks everything as idle, this is the "all" behavior */
+ mark_idle(zram, cutoff_time);
+ rv = len;
+
+out_unlock:
+ up_read(&zram->init_lock);
+out:
+ return rv;
}
#ifdef CONFIG_ZRAM_WRITEBACK
--
2.33.0.464.g1972c5931b-goog
From: Brian Geffon <hidden> Date: 2021-09-23 00:43:23
Hi Minchan,
Thank you for taking a look. I'm happy to make that change, but I
personally cannot see why userspace would want to do something like
idle pages older than "0x3C seconds" or "0o250600 seconds," it just
seems like a strange way to represent seconds. What do you think?
Brian
On Wed, Sep 22, 2021 at 8:09 PM Minchan Kim [off-list ref] wrote:
On Tue, Sep 21, 2021 at 12:43:36PM -0700, Brian Geffon wrote:
quoted
This change introduces an aged idle interface to the existing
idle sysfs file for zram.
When CONFIG_ZRAM_MEMORY_TRACKING is enabled the idle file
now also accepts an integer argument. This integer is the
age (in seconds) of pages to mark as idle. The idle file
still supports 'all' as it always has. This new approach
allows for much more control over which pages get marked
as idle.
v2 -> v3:
- Correct unused variable warning when
CONFIG_ZRAM_MEMORY_TRACKING is not enabled.
v1 -> v2:
- Switch to using existing idle file.
- Dont compare ktime directly.
Signed-off-by: Brian Geffon <redacted>
---
Documentation/admin-guide/blockdev/zram.rst | 8 +++
drivers/block/zram/zram_drv.c | 60 +++++++++++++++------
2 files changed, 52 insertions(+), 16 deletions(-)
@@ -328,6 +328,14 @@ as idle:: From now on, any pages on zram are idle pages. The idle mark will be removed until someone requests access of the block. IOW, unless there is access request, those pages are still idle pages.+Additionally, when CONFIG_ZRAM_MEMORY_TRACKING is enabled pages can be+marked as idle based on how long (in seconds) it's been since they were+last accessed, in seconds::++ echo 86400 > /sys/block/zramX/idle++In this example all pages which haven't been accessed in more than 86400+seconds (one day) will be marked idle. Admin can request writeback of those idle pages at right timing via::
@@ -314,14 +308,48 @@ static ssize_t idle_store(struct device *dev,*/zram_slot_lock(zram,index);if(zram_allocated(zram,index)&&-!zram_test_flag(zram,index,ZRAM_UNDER_WB))-zram_set_flag(zram,index,ZRAM_IDLE);+!zram_test_flag(zram,index,ZRAM_UNDER_WB)){+#ifdef CONFIG_ZRAM_MEMORY_TRACKING+is_idle=(!cutoff||ktime_after(cutoff,zram->table[index].ac_time));+#endif+if(is_idle)+zram_set_flag(zram,index,ZRAM_IDLE);+}zram_slot_unlock(zram,index);}+}-up_read(&zram->init_lock);+staticssize_tidle_store(structdevice*dev,+structdevice_attribute*attr,constchar*buf,size_tlen)+{+structzram*zram=dev_to_zram(dev);+ktime_tcutoff_time=0;+ssize_trv=-EINVAL;-returnlen;+if(!sysfs_streq(buf,"all")){+#ifdef CONFIG_ZRAM_MEMORY_TRACKING+u64age_sec;+/* If it did not parse as 'all' try to treat it as an integer */+if(!kstrtoull(buf,10,&age_sec))
nit:
Do we need such limit base which work with only 10 base?
Passing 0 would give more flexibility.
Otherwise, looks good to me.
Thanks, Brian.
quoted
+ cutoff_time = ktime_sub(ktime_get_boottime(),
+ ns_to_ktime(age_sec * NSEC_PER_SEC));
+ else
+#endif
+ goto out;
+ }
+
+ down_read(&zram->init_lock);
+ if (!init_done(zram))
+ goto out_unlock;
+
+ /* A age_sec of 0 marks everything as idle, this is the "all" behavior */
+ mark_idle(zram, cutoff_time);
+ rv = len;
+
+out_unlock:
+ up_read(&zram->init_lock);
+out:
+ return rv;
}
#ifdef CONFIG_ZRAM_WRITEBACK
--
2.33.0.464.g1972c5931b-goog
From: Minchan Kim <minchan@kernel.org> Date: 2021-09-23 06:02:15
Hey Brian,
On Wed, Sep 22, 2021 at 08:42:44PM -0400, Brian Geffon wrote:
Hi Minchan,
Thank you for taking a look. I'm happy to make that change, but I
personally cannot see why userspace would want to do something like
idle pages older than "0x3C seconds" or "0o250600 seconds," it just
seems like a strange way to represent seconds. What do you think?
Kernel communty loves inline reply instead of top posting. ;-)
I am not strong opinion about mutiple base support. The question
just started from "what's the benefit with only 10-base support?"
if we can support multiple bases with almost zero maintainace
overhead.
Brian
On Wed, Sep 22, 2021 at 8:09 PM Minchan Kim [off-list ref] wrote:
quoted
On Tue, Sep 21, 2021 at 12:43:36PM -0700, Brian Geffon wrote:
quoted
This change introduces an aged idle interface to the existing
idle sysfs file for zram.
When CONFIG_ZRAM_MEMORY_TRACKING is enabled the idle file
now also accepts an integer argument. This integer is the
age (in seconds) of pages to mark as idle. The idle file
still supports 'all' as it always has. This new approach
allows for much more control over which pages get marked
as idle.
v2 -> v3:
- Correct unused variable warning when
CONFIG_ZRAM_MEMORY_TRACKING is not enabled.
v1 -> v2:
- Switch to using existing idle file.
- Dont compare ktime directly.
Signed-off-by: Brian Geffon <redacted>
---
Documentation/admin-guide/blockdev/zram.rst | 8 +++
drivers/block/zram/zram_drv.c | 60 +++++++++++++++------
2 files changed, 52 insertions(+), 16 deletions(-)
@@ -328,6 +328,14 @@ as idle:: From now on, any pages on zram are idle pages. The idle mark will be removed until someone requests access of the block. IOW, unless there is access request, those pages are still idle pages.+Additionally, when CONFIG_ZRAM_MEMORY_TRACKING is enabled pages can be+marked as idle based on how long (in seconds) it's been since they were+last accessed, in seconds::++ echo 86400 > /sys/block/zramX/idle++In this example all pages which haven't been accessed in more than 86400+seconds (one day) will be marked idle. Admin can request writeback of those idle pages at right timing via::
@@ -314,14 +308,48 @@ static ssize_t idle_store(struct device *dev,*/zram_slot_lock(zram,index);if(zram_allocated(zram,index)&&-!zram_test_flag(zram,index,ZRAM_UNDER_WB))-zram_set_flag(zram,index,ZRAM_IDLE);+!zram_test_flag(zram,index,ZRAM_UNDER_WB)){+#ifdef CONFIG_ZRAM_MEMORY_TRACKING+is_idle=(!cutoff||ktime_after(cutoff,zram->table[index].ac_time));+#endif+if(is_idle)+zram_set_flag(zram,index,ZRAM_IDLE);+}zram_slot_unlock(zram,index);}+}-up_read(&zram->init_lock);+staticssize_tidle_store(structdevice*dev,+structdevice_attribute*attr,constchar*buf,size_tlen)+{+structzram*zram=dev_to_zram(dev);+ktime_tcutoff_time=0;+ssize_trv=-EINVAL;-returnlen;+if(!sysfs_streq(buf,"all")){+#ifdef CONFIG_ZRAM_MEMORY_TRACKING+u64age_sec;+/* If it did not parse as 'all' try to treat it as an integer */+if(!kstrtoull(buf,10,&age_sec))
nit:
Do we need such limit base which work with only 10 base?
Passing 0 would give more flexibility.
Otherwise, looks good to me.
Thanks, Brian.
quoted
+ cutoff_time = ktime_sub(ktime_get_boottime(),
+ ns_to_ktime(age_sec * NSEC_PER_SEC));
+ else
+#endif
+ goto out;
+ }
+
+ down_read(&zram->init_lock);
+ if (!init_done(zram))
+ goto out_unlock;
+
+ /* A age_sec of 0 marks everything as idle, this is the "all" behavior */
+ mark_idle(zram, cutoff_time);
+ rv = len;
+
+out_unlock:
+ up_read(&zram->init_lock);
+out:
+ return rv;
}
#ifdef CONFIG_ZRAM_WRITEBACK
--
2.33.0.464.g1972c5931b-goog
From: Brian Geffon <hidden> Date: 2021-09-23 13:01:34
This change introduces an aged idle interface to the existing
idle sysfs file for zram.
When CONFIG_ZRAM_MEMORY_TRACKING is enabled the idle file
now also accepts an integer argument. This integer is the
age (in seconds) of pages to mark as idle. The idle file
still supports 'all' as it always has. This new approach
allows for much more control over which pages get marked
as idle.
v3 -> v4:
- Remove base10 restriction.
v2 -> v3:
- Correct unused variable warning when
CONFIG_ZRAM_MEMORY_TRACKING is not enabled.
v1 -> v2:
- Switch to using existing idle file.
- Dont compare ktime directly.
Signed-off-by: Brian Geffon <redacted>
---
Documentation/admin-guide/blockdev/zram.rst | 8 +++
drivers/block/zram/zram_drv.c | 60 +++++++++++++++------
2 files changed, 52 insertions(+), 16 deletions(-)
@@ -328,6 +328,14 @@ as idle:: From now on, any pages on zram are idle pages. The idle mark will be removed until someone requests access of the block. IOW, unless there is access request, those pages are still idle pages.+Additionally, when CONFIG_ZRAM_MEMORY_TRACKING is enabled pages can be+marked as idle based on how long (in seconds) it's been since they were+last accessed::++ echo 86400 > /sys/block/zramX/idle++In this example all pages which haven't been accessed in more than 86400+seconds (one day) will be marked idle. Admin can request writeback of those idle pages at right timing via::
@@ -314,14 +308,48 @@ static ssize_t idle_store(struct device *dev,*/zram_slot_lock(zram,index);if(zram_allocated(zram,index)&&-!zram_test_flag(zram,index,ZRAM_UNDER_WB))-zram_set_flag(zram,index,ZRAM_IDLE);+!zram_test_flag(zram,index,ZRAM_UNDER_WB)){+#ifdef CONFIG_ZRAM_MEMORY_TRACKING+is_idle=(!cutoff||ktime_after(cutoff,zram->table[index].ac_time));+#endif+if(is_idle)+zram_set_flag(zram,index,ZRAM_IDLE);+}zram_slot_unlock(zram,index);}+}-up_read(&zram->init_lock);+staticssize_tidle_store(structdevice*dev,+structdevice_attribute*attr,constchar*buf,size_tlen)+{+structzram*zram=dev_to_zram(dev);+ktime_tcutoff_time=0;+ssize_trv=-EINVAL;-returnlen;+if(!sysfs_streq(buf,"all")){+#ifdef CONFIG_ZRAM_MEMORY_TRACKING+u64age_sec;+/* If it did not parse as 'all' try to treat it as an integer */+if(!kstrtoull(buf,0,&age_sec))+cutoff_time=ktime_sub(ktime_get_boottime(),+ns_to_ktime(age_sec*NSEC_PER_SEC));+else+#endif+gotoout;+}++down_read(&zram->init_lock);+if(!init_done(zram))+gotoout_unlock;++/* A age_sec of 0 marks everything as idle, this is the "all" behavior */+mark_idle(zram,cutoff_time);+rv=len;++out_unlock:+up_read(&zram->init_lock);+out:+returnrv;}#ifdef CONFIG_ZRAM_WRITEBACK
From: Minchan Kim <minchan@kernel.org> Date: 2021-09-23 16:47:54
On Thu, Sep 23, 2021 at 06:01:15AM -0700, Brian Geffon wrote:
This change introduces an aged idle interface to the existing
idle sysfs file for zram.
When CONFIG_ZRAM_MEMORY_TRACKING is enabled the idle file
now also accepts an integer argument. This integer is the
age (in seconds) of pages to mark as idle. The idle file
still supports 'all' as it always has. This new approach
allows for much more control over which pages get marked
as idle.
v3 -> v4:
- Remove base10 restriction.
v2 -> v3:
- Correct unused variable warning when
CONFIG_ZRAM_MEMORY_TRACKING is not enabled.
v1 -> v2:
- Switch to using existing idle file.
- Dont compare ktime directly.
Signed-off-by: Brian Geffon <redacted>
From: Andrew Morton <akpm@linux-foundation.org> Date: 2021-09-23 22:53:12
On Thu, 23 Sep 2021 06:01:15 -0700 Brian Geffon [off-list ref] wrote:
quoted hunk
This change introduces an aged idle interface to the existing
idle sysfs file for zram.
When CONFIG_ZRAM_MEMORY_TRACKING is enabled the idle file
now also accepts an integer argument. This integer is the
age (in seconds) of pages to mark as idle. The idle file
still supports 'all' as it always has. This new approach
allows for much more control over which pages get marked
as idle.
@@ -291,22 +291,16 @@ static ssize_t mem_used_max_store(struct device *dev, return len; }-static ssize_t idle_store(struct device *dev,- struct device_attribute *attr, const char *buf, size_t len)+/*+ * Mark all pages which are older than or equal to cutoff as IDLE.+ * Callers should hold the zram init lock in read mode+ **/
A simple "*/" is conventional.
quoted hunk
+static void mark_idle(struct zram *zram, ktime_t cutoff)
{
- struct zram *zram = dev_to_zram(dev);
+ int is_idle = 1;
unsigned long nr_pages = zram->disksize >> PAGE_SHIFT;
int index;
- if (!sysfs_streq(buf, "all"))
- return -EINVAL;
-
- down_read(&zram->init_lock);
- if (!init_done(zram)) {
- up_read(&zram->init_lock);
- return -EINVAL;
- }
-
for (index = 0; index < nr_pages; index++) {
/*
* Do not mark ZRAM_UNDER_WB slot as ZRAM_IDLE to close race.
@@ -314,14 +308,48 @@ static ssize_t idle_store(struct device *dev, */ zram_slot_lock(zram, index); if (zram_allocated(zram, index) &&- !zram_test_flag(zram, index, ZRAM_UNDER_WB))- zram_set_flag(zram, index, ZRAM_IDLE);+ !zram_test_flag(zram, index, ZRAM_UNDER_WB)) {+#ifdef CONFIG_ZRAM_MEMORY_TRACKING+ is_idle = (!cutoff || ktime_after(cutoff, zram->table[index].ac_time));+#endif+ if (is_idle)+ zram_set_flag(zram, index, ZRAM_IDLE);+ } zram_slot_unlock(zram, index); }+}- up_read(&zram->init_lock);+static ssize_t idle_store(struct device *dev,+ struct device_attribute *attr, const char *buf, size_t len)+{+ struct zram *zram = dev_to_zram(dev);+ ktime_t cutoff_time = 0;+ ssize_t rv = -EINVAL;- return len;+ if (!sysfs_streq(buf, "all")) {+#ifdef CONFIG_ZRAM_MEMORY_TRACKING+ u64 age_sec;+ /* If it did not parse as 'all' try to treat it as an integer */+ if (!kstrtoull(buf, 0, &age_sec))+ cutoff_time = ktime_sub(ktime_get_boottime(),+ ns_to_ktime(age_sec * NSEC_PER_SEC));+ else+#endif+ goto out;+ }
The ifdef tricks are pretty ugly. Can things be improved with IS_ENABLED()?
From: Brian Geffon <hidden> Date: 2021-09-24 16:11:50
This change introduces an aged idle interface to the existing
idle sysfs file for zram.
When CONFIG_ZRAM_MEMORY_TRACKING is enabled the idle file
now also accepts an integer argument. This integer is the
age (in seconds) of pages to mark as idle. The idle file
still supports 'all' as it always has. This new approach
allows for much more control over which pages get marked
as idle.
v4 -> v5:
- Andrew's suggestions to use IS_ENABLED and
cleanup comment.
v3 -> v4:
- Remove base10 restriction.
v2 -> v3:
- Correct unused variable warning when
CONFIG_ZRAM_MEMORY_TRACKING is not enabled.
v1 -> v2:
- Switch to using existing idle file.
- Dont compare ktime directly.
Signed-off-by: Brian Geffon <redacted>
Acked-by: Minchan Kim <minchan@kernel.org>
---
Documentation/admin-guide/blockdev/zram.rst | 8 +++
drivers/block/zram/zram_drv.c | 61 +++++++++++++++------
2 files changed, 53 insertions(+), 16 deletions(-)
@@ -327,6 +327,14 @@ as idle:: From now on, any pages on zram are idle pages. The idle mark will be removed until someone requests access of the block. IOW, unless there is access request, those pages are still idle pages.+Additionally, when CONFIG_ZRAM_MEMORY_TRACKING is enabled pages can be+marked as idle based on how long (in seconds) it's been since they were+last accessed::++ echo 86400 > /sys/block/zramX/idle++In this example all pages which haven't been accessed in more than 86400+seconds (one day) will be marked idle. Admin can request writeback of those idle pages at right timing via::
@@ -314,14 +308,49 @@ static ssize_t idle_store(struct device *dev,*/zram_slot_lock(zram,index);if(zram_allocated(zram,index)&&-!zram_test_flag(zram,index,ZRAM_UNDER_WB))-zram_set_flag(zram,index,ZRAM_IDLE);+!zram_test_flag(zram,index,ZRAM_UNDER_WB)){+#ifdef CONFIG_ZRAM_MEMORY_TRACKING+is_idle=(!cutoff||ktime_after(cutoff,zram->table[index].ac_time));+#endif+if(is_idle)+zram_set_flag(zram,index,ZRAM_IDLE);+}zram_slot_unlock(zram,index);}+}-up_read(&zram->init_lock);+staticssize_tidle_store(structdevice*dev,+structdevice_attribute*attr,constchar*buf,size_tlen)+{+structzram*zram=dev_to_zram(dev);+ktime_tcutoff_time=0;+ssize_trv=-EINVAL;-returnlen;+if(!sysfs_streq(buf,"all")){+/*+*Ifitdidnotparseas'all'trytotreatitasanintegerwhen+*wehavememorytrackingenabled.+*/+u64age_sec;+if(IS_ENABLED(CONFIG_ZRAM_MEMORY_TRACKING)&&!kstrtoull(buf,0,&age_sec))+cutoff_time=ktime_sub(ktime_get_boottime(),+ns_to_ktime(age_sec*NSEC_PER_SEC));+else+gotoout;+}++down_read(&zram->init_lock);+if(!init_done(zram))+gotoout_unlock;++/* A age_sec of 0 marks everything as idle, this is the "all" behavior */+mark_idle(zram,cutoff_time);+rv=len;++out_unlock:+up_read(&zram->init_lock);+out:+returnrv;}#ifdef CONFIG_ZRAM_WRITEBACK
From: Andrew Morton <akpm@linux-foundation.org> Date: 2021-09-24 19:54:27
On Fri, 24 Sep 2021 09:11:28 -0700 Brian Geffon [off-list ref] wrote:
This change introduces an aged idle interface to the existing
idle sysfs file for zram.
When CONFIG_ZRAM_MEMORY_TRACKING is enabled the idle file
now also accepts an integer argument. This integer is the
age (in seconds) of pages to mark as idle. The idle file
still supports 'all' as it always has. This new approach
allows for much more control over which pages get marked
as idle.
v4 -> v5:
- Andrew's suggestions to use IS_ENABLED and
cleanup comment.
Hi Andrew,
As written that patch won't compile when
CONFIG_ZRAM_MEMORY_TRACKING=n, my guess is that the compiler pass that
removes the dead branch only happens after it attempts to compile the
branch itself. So it appears that even though IS_ENABLED(..) always
evaluates to 0, the compile will fail because table[index].ac_time
does not exist. You should get an error like this:
drivers/block/zram/zram_drv.c:314:57: error: no member named 'ac_time'
in 'struct zram_table_entry'
(!cutoff
|| ktime_after(cutoff, zram->table[index].ac_time)))
Brian
From: Brian Geffon <hidden> Date: 2021-09-29 14:31:19
This change introduces an aged idle interface to the existing
idle sysfs file for zram.
When CONFIG_ZRAM_MEMORY_TRACKING is enabled the idle file
now also accepts an integer argument. This integer is the
age (in seconds) of pages to mark as idle. The idle file
still supports 'all' as it always has. This new approach
allows for much more control over which pages get marked
as idle.
v5 -> v6:
- Sergey's cleanup suggestions.
v4 -> v5:
- Andrew's suggestions to use IS_ENABLED and
cleanup comment.
v3 -> v4:
- Remove base10 restriction.
v2 -> v3:
- Correct unused variable warning when
CONFIG_ZRAM_MEMORY_TRACKING is not enabled.
v1 -> v2:
- Switch to using existing idle file.
- Dont compare ktime directly.
Signed-off-by: Brian Geffon <redacted>
Acked-by: Minchan Kim <minchan@kernel.org>
---
Documentation/admin-guide/blockdev/zram.rst | 8 +++
drivers/block/zram/zram_drv.c | 62 +++++++++++++++------
2 files changed, 54 insertions(+), 16 deletions(-)
@@ -328,6 +328,14 @@ as idle:: From now on, any pages on zram are idle pages. The idle mark will be removed until someone requests access of the block. IOW, unless there is access request, those pages are still idle pages.+Additionally, when CONFIG_ZRAM_MEMORY_TRACKING is enabled pages can be+marked as idle based on how long (in seconds) it's been since they were+last accessed::++ echo 86400 > /sys/block/zramX/idle++In this example all pages which haven't been accessed in more than 86400+seconds (one day) will be marked idle. Admin can request writeback of those idle pages at right timing via::
@@ -314,14 +308,50 @@ static ssize_t idle_store(struct device *dev,*/zram_slot_lock(zram,index);if(zram_allocated(zram,index)&&-!zram_test_flag(zram,index,ZRAM_UNDER_WB))-zram_set_flag(zram,index,ZRAM_IDLE);+!zram_test_flag(zram,index,ZRAM_UNDER_WB)){+#ifdef CONFIG_ZRAM_MEMORY_TRACKING+is_idle=!cutoff||ktime_after(cutoff,zram->table[index].ac_time);+#endif+if(is_idle)+zram_set_flag(zram,index,ZRAM_IDLE);+}zram_slot_unlock(zram,index);}+}-up_read(&zram->init_lock);+staticssize_tidle_store(structdevice*dev,+structdevice_attribute*attr,constchar*buf,size_tlen)+{+structzram*zram=dev_to_zram(dev);+ktime_tcutoff_time=0;+ssize_trv=-EINVAL;-returnlen;+if(!sysfs_streq(buf,"all")){+/*+*Ifitdidnotparseas'all'trytotreatitasanintegerwhen+*wehavememorytrackingenabled.+*/+u64age_sec;++if(IS_ENABLED(CONFIG_ZRAM_MEMORY_TRACKING)&&!kstrtoull(buf,0,&age_sec))+cutoff_time=ktime_sub(ktime_get_boottime(),+ns_to_ktime(age_sec*NSEC_PER_SEC));+else+gotoout;+}++down_read(&zram->init_lock);+if(!init_done(zram))+gotoout_unlock;++/* A cutoff_time of 0 marks everything as idle, this is the "all" behavior */+mark_idle(zram,cutoff_time);+rv=len;++out_unlock:+up_read(&zram->init_lock);+out:+returnrv;}#ifdef CONFIG_ZRAM_WRITEBACK