do so.
This could be a mount option. Something like nofile in spirit of nodev
but with opposite effect. My assumption is that changing default
behavior is unlikely to be approvable.
--
Sami Kerola
http://www.iki.fi/kerolasa/
e issue. That is almost certainly down to speed the
system in hand, e.g., quicker the computer less likely to trigger.
--
Sami Kerola
http://www.iki.fi/kerolasa/
On 19 December 2016 at 10:24, Christoph Hellwig wrote:
> On Sun, Dec 18, 2016 at 06:57:27PM +0000, Sami Kerola wrote:
>> An attempt to freeze a filesystem that does not support such operation is
>> reported as EOPNOTSUPP to user. Running unfreeze to the same filesystem
>> r
-by: Sami Kerola
---
fs/ioctl.c | 4
1 file changed, 4 insertions(+)
diff --git a/fs/ioctl.c b/fs/ioctl.c
index cb9b02940805..1d6372ef4008 100644
--- a/fs/ioctl.c
+++ b/fs/ioctl.c
@@ -566,6 +566,10 @@ static int ioctl_fsthaw(struct file *filp)
if (!capable(CAP_SYS_ADMIN
On 6 August 2014 13:19, Sergey Senozhatsky wrote:
> Cc Minchan Kim, Jerome Marchand, Nitin Gupta, linux-kernel
>
> On (08/05/14 23:36), Sami Kerola wrote:
>> On 4 August 2014 12:55, Karel Zak wrote:
>> > On Mon, Aug 04, 2014 at 12:08:10AM +0100, Sami Kerola wrote:
>&
On 5 August 2014 09:12, Minchan Kim wrote:
> On Tue, Aug 05, 2014 at 09:07:16AM +0200, Karel Zak wrote:
>> On Tue, Aug 05, 2014 at 11:00:24AM +0900, Minchan Kim wrote:
>> > On Wed, Jul 30, 2014 at 12:14:42AM +0100, Sami Kerola wrote:
>> > > The zram devices
Both disksize and comp_algorithm return EBUSY when a change is attempted
to a device in use, and so should max_comp_streams.
Signed-off-by: Sami Kerola
---
drivers/block/zram/zram_drv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/block/zram/zram_drv.c b/drivers
xt?id=31dab719fa50cf56d56d3dc25980fecd336f6ca8
[5]
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/block/loop.c?id=31dab719fa50cf56d56d3dc25980fecd336f6ca8#n1757
[6] such as: modprobe zram num_devices=4
[7] requires 'rmmod zram' which is not possible if any zram device is busy
--
S
Commit-ID: 8192f5bccf26968a1d78ef71890f7a27f824119f
Gitweb: http://git.kernel.org/tip/8192f5bccf26968a1d78ef71890f7a27f824119f
Author: Sami Kerola
AuthorDate: Wed, 17 Jul 2013 17:30:28 +0100
Committer: Ingo Molnar
CommitDate: Thu, 18 Jul 2013 09:03:33 +0200
x86/boot: Add lz4
On 30 June 2013 16:10, Kay Sievers wrote:
> On Sat, Jun 29, 2013 at 10:53 PM, Sami Kerola wrote:
>
>> BTW having a way to measure effect of suspend/resume could lead to a
>> way to fix time time distortion.
>
>> Perhaps there is better alternative to fix user space p
On 29 June 2013 15:23, Eric W. Biederman wrote:
>
> Nacked-by: "Eric W. Biederman"
>
> The pach does not solve the problem described.
Which might be true, and I am open to better proposals.
> Sami Kerola writes:
>
>> The kernel does not expose precise
he boot time as precisily as it can.
CC: Karel Zak
CC: Lennart Poettering
CC: Kay Sievers
CC: Eric W. Biederman
References: http://www.spinics.net/lists/util-linux-ng/msg08092.html
Measurement: https://plus.google.com/u/0/117341944650953092607/posts/SHy5qu1HpSU
Signed-off-by: Sami Kerola
--
On Tue, Nov 20, 2012 at 12:21 PM, Karel Zak wrote:
> On Mon, Nov 19, 2012 at 04:12:50PM -0800, Andrew Morton wrote:
>> Where's the benefit in switching ipcs over to using /proc?
>>
>> procfs reads are probably slower than the syscalls?
>
> 32bit userspace and 64bit kernel (RHEL ppc64), it seems m
g the concept
makes sense and could be considered part of upstream kernel (assuming
my coding meets the usual quality criteria).
Any thoughts, comments, recommendations?
--
Sami Kerola
http://www.iki.fi/kerolasa/
--
To unsubscribe from this list: send the line "unsubscribe linux-kern
Make resulted to untraced files, which where the binaries make
produced, such need to be ignored.
Signed-off-by: Sami Kerola
---
tools/power/x86/turbostat/.gitignore | 1 +
tools/power/x86/x86_energy_perf_policy/.gitignore | 1 +
2 files changed, 2 insertions(+)
create mode 100644
15 matches
Mail list logo
