[question] page cache studies

2015-06-29 Thread Vladimir Shebordaev
Hello, I'd like to ask, are there any numerical studies of current Linux page cache implementation? I don't mean those nice design documents but rather theoretical estimates based on it, e.g working set size, active and inactive list sizes and cache hit probability one should expect for a given wo

Re: [RFC] proc interface to show file page cache usage details

2014-11-23 Thread Vladimir Shebordaev
On Sun, 2014-11-23 at 14:51 +0400, Vladimir Shebordaev wrote: > Hi, > > I would like to suggest an interface to list inodes that currently > occupy page cache in human readable form. > > A piece of code below creates a dedicated proc entry, namely, > /proc/kpagecache.

[RFC] proc interface to show file page cache usage details

2014-11-23 Thread Vladimir Shebordaev
b/fs/proc/pagecache.c @@ -0,0 +1,412 @@ +/* + * fs/proc/pagecache.c + * + * Copyright (C) 2014 + * + * Author: Vladimir Shebordaev + * + * /proc/kpagecache interface to show file page cache usage + */ + +#include +#include +#include + +#include +#include +#include +#include +#include +#

Re: USB and MMC device problems on Kernel 2.6.22

2007-09-09 Thread Vladimir Shebordaev
Hi! [EMAIL PROTECTED] пишет: Sorry for not clear about the kernel version, let me try again: I have an ARM hardware board works fine with USB and MMC on kernel 2.6.11. Now, I've just upgraded it to kernel 2.6.22. The modules seem loaded fine, please see following list, but neither USB nor MMC

[PATCH] [input] USB touchscreen

2007-09-06 Thread Vladimir Shebordaev
From: Vladimir Shebordaev <[EMAIL PROTECTED]> This patch fixes a nasty typo in usbtouchscreen driver. The typo is inherited from the original mtouchusb. It used to make the input subsytem to incorrectly report the physical device ids to userspace that in turn is much confusing for, e.g.

[PATCH] [input] USB touchscreen

2007-09-06 Thread Vladimir Shebordaev
From: Vladimir Shebordaev <[EMAIL PROTECTED]> This patch fixes a nasty typo in usbtouchscreen driver. The typo is inherited from the original mtouchusb. It used to make the input subsytem to incorrectly report the physical device ids to userspace that in turn is much confusing for, e.g.

[PATCH] [input] USB touchscreen

2007-09-06 Thread Vladimir Shebordaev
identical touchscreens. Signed-off-by: Vladimir Shebordaev <[EMAIL PROTECTED]> --- drivers/input/touchscreen/usbtouchscreen.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/input/touchscreen/usbtouchscreen.c b/drivers/input/touchscreen/usbtouchscreen.c index e

[PATCH] [input] USB touchscreen

2007-09-06 Thread Vladimir Shebordaev
identical touchscreens. Signed-off-by: Vladimir Shebordaev <[EMAIL PROTECTED]> --- drivers/input/touchscreen/usbtouchscreen.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/input/touchscreen/usbtouchscreen.c b/drivers/input/touchscreen/usbtouchscreen.c index e