lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080908141555.GB31784@elf.ucw.cz>
Date:	Mon, 8 Sep 2008 16:15:55 +0200
From:	Pavel Machek <pavel@...e.cz>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	dwmw2@...radead.org, drepper@...hat.com, mingo@...e.hu,
	tglx@...x.de
Subject: Re: [PATCH 12/13] hrtimer: create a "timer_slack" field in the
	task struct

On Mon 2008-09-08 06:40:02, Arjan van de Ven wrote:
> On Mon, 8 Sep 2008 15:27:16 +0200
> Pavel Machek <pavel@...e.cz> wrote:
> > > 
> > > ... which nobody uses today.
> > > It's not just new syscalls, it's a new glibc api as well at that
> > > point.
> > 
> > ...and new applications, yes. I believe applications should
> > explicitely enable slacking timers.
> 
> timers are slacking today, at least for select() and poll(), and are a
> great deal more so than the defaults in this patchkit.

Ok, so select()/poll() may default to non-zero slack for legacy apps.

> The great advantage of the prctl() approach (which is usable) over new
> system calls and glibc APIs is that it will get used, because the admin
> can use it just like he uses the "nice" command, on existing software.

Yes, it is a great advantage, but it feels like a hack. Maybe it is
better done with LD_PRELOAD or something?

I'd certianly want the applications to specify slack themselves in
like 10 years.

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ