Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1424630 > unrolled thread
| Started by | Geliang Tang <geliangtang@gmail.com> |
|---|---|
| First post | 2016-06-17 05:40 +0200 |
| Last post | 2016-06-17 06:20 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
[PATCH] zram: use writer semaphores in device attributes store Geliang Tang <geliangtang@gmail.com> - 2016-06-17 05:40 +0200
Re: [PATCH] zram: use writer semaphores in device attributes store Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> - 2016-06-17 06:20 +0200
| From | Geliang Tang <geliangtang@gmail.com> |
|---|---|
| Date | 2016-06-17 05:40 +0200 |
| Subject | [PATCH] zram: use writer semaphores in device attributes store |
| Message-ID | <rKSNr-19K-11@gated-at.bofh.it> |
Since the device attributes store provides write access. This patch uses
down_write()/up_write() instead of down_read()/up_read() in
mem_used_max_store() and compact_store().
Signed-off-by: Geliang Tang <geliangtang@gmail.com>
---
drivers/block/zram/zram_drv.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c
index 7454cf1..cfed743 100644
--- a/drivers/block/zram/zram_drv.c
+++ b/drivers/block/zram/zram_drv.c
@@ -293,13 +293,13 @@ static ssize_t mem_used_max_store(struct device *dev,
if (err || val != 0)
return -EINVAL;
- down_read(&zram->init_lock);
+ down_write(&zram->init_lock);
if (init_done(zram)) {
struct zram_meta *meta = zram->meta;
atomic_long_set(&zram->stats.max_used_pages,
zs_get_total_pages(meta->mem_pool));
}
- up_read(&zram->init_lock);
+ up_write(&zram->init_lock);
return len;
}
@@ -372,15 +372,15 @@ static ssize_t compact_store(struct device *dev,
struct zram *zram = dev_to_zram(dev);
struct zram_meta *meta;
- down_read(&zram->init_lock);
+ down_write(&zram->init_lock);
if (!init_done(zram)) {
- up_read(&zram->init_lock);
+ up_write(&zram->init_lock);
return -EINVAL;
}
meta = zram->meta;
zs_compact(meta->mem_pool);
- up_read(&zram->init_lock);
+ up_write(&zram->init_lock);
return len;
}
--
1.9.1
[toc] | [next] | [standalone]
| From | Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> |
|---|---|
| Date | 2016-06-17 06:20 +0200 |
| Message-ID | <rKTq9-1Ds-3@gated-at.bofh.it> |
| In reply to | #1424630 |
Hello,
On (06/17/16 11:31), Geliang Tang wrote:
[..]
> Since the device attributes store provides write access. This patch uses
> down_write()/up_write() instead of down_read()/up_read() in
> mem_used_max_store() and compact_store().
we use ->init_lock not to make attrs exclusive, but to prevent
concurrent reset/etc.
> Signed-off-by: Geliang Tang <geliangtang@gmail.com>
> ---
> drivers/block/zram/zram_drv.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c
> index 7454cf1..cfed743 100644
> --- a/drivers/block/zram/zram_drv.c
> +++ b/drivers/block/zram/zram_drv.c
> @@ -293,13 +293,13 @@ static ssize_t mem_used_max_store(struct device *dev,
> if (err || val != 0)
> return -EINVAL;
>
> - down_read(&zram->init_lock);
> + down_write(&zram->init_lock);
> if (init_done(zram)) {
> struct zram_meta *meta = zram->meta;
> atomic_long_set(&zram->stats.max_used_pages,
> zs_get_total_pages(meta->mem_pool));
> }
> - up_read(&zram->init_lock);
> + up_write(&zram->init_lock);
not critical. can work.
> return len;
> }
> @@ -372,15 +372,15 @@ static ssize_t compact_store(struct device *dev,
> struct zram *zram = dev_to_zram(dev);
> struct zram_meta *meta;
>
> - down_read(&zram->init_lock);
> + down_write(&zram->init_lock);
> if (!init_done(zram)) {
> - up_read(&zram->init_lock);
> + up_write(&zram->init_lock);
> return -EINVAL;
> }
>
> meta = zram->meta;
> zs_compact(meta->mem_pool);
> - up_read(&zram->init_lock);
> + up_write(&zram->init_lock);
pool compaction can take some time. *probably* seconds in the worst
case, when the device is under IO pressure and class' locks are heavily
contended and every class has a considerable number of objects to move.
so I think we don't want to block other attrs while we compact the pool,
compaction takes care of the concurrency internally.
-ss
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web