mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: bert hubert <ahu@ds9a.nl>
Cc: Andrew Morton <akpm@digeo.com>,
	ch@murgatroid.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.69-mm6
Date: 16 May 2003 16:37:43 +0100	[thread overview]
Message-ID: <1053099462.5599.1.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030516100432.GA21627@outpost.ds9a.nl>

On Gwe, 2003-05-16 at 11:04, bert hubert wrote:
> Please don't! For the same reason as the futexes, turning this off will
> randombly break stuff and on a pc it won't give any benefit.
> 
> I'd vote for treating this patch just like the futexes one, making sure that
> those who know *how* can turn epoll off, but leave it out of make config.
> 
> Furthermore, I wonder if this patch is a large savings, the bulk of epoll is
> infrastructure, not the few syscalls.

All of this stuff should be disablable and far more. It probably all
wants hiding under a single "Shrink feature set" type option most people
can skip over as they do with kernel debugging.


  parent reply	other threads:[~2003-05-16 16:24 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-16  8:54 2.5.69-mm6 Andrew Morton
2003-05-16 10:04 ` 2.5.69-mm6 bert hubert
2003-05-16 10:13   ` 2.5.69-mm6 Andrew Morton
2003-05-16 10:16     ` 2.5.69-mm6 bert hubert
2003-05-16 15:37   ` Alan Cox [this message]
2003-05-16 16:58     ` 2.5.69-mm6 Valdis.Kletnieks
2003-05-17 13:46       ` 2.5.69-mm6 Alan Cox
2003-05-16 11:26 ` [OOPS] 2.5.69-mm6 Alexander Hoogerhuis
2003-05-16 18:08   ` William Lee Irwin III
2003-05-16 18:56     ` Dave Jones
2003-05-16 19:17       ` William Lee Irwin III
2003-05-17  3:23         ` Zwane Mwaikambo
2003-05-17 14:16           ` Zwane Mwaikambo
2003-05-18 13:01             ` Alexander Hoogerhuis
2003-05-19  8:23             ` Alexander Hoogerhuis
2003-05-19  8:36               ` Zwane Mwaikambo
2003-05-19  8:45                 ` Zwane Mwaikambo
2003-05-19  8:53                 ` Alexander Hoogerhuis
2003-05-19  8:53                   ` Zwane Mwaikambo
2003-05-19  9:23                     ` Alexander Hoogerhuis
2003-05-19 10:18                     ` Alexander Hoogerhuis
2003-05-19 11:03                       ` Zwane Mwaikambo
2003-05-18 12:59           ` Alexander Hoogerhuis
2003-05-18 12:57         ` Alexander Hoogerhuis
2003-05-16 17:28 ` 2.5.69-mm6 Andreas Henriksson
2003-05-16 17:55   ` 2.5.69-mm6 Dave Jones
2003-05-16 18:10     ` 2.5.69-mm6 Andreas Henriksson
2003-05-16 18:30       ` 2.5.69-mm6 Dave Jones
2003-05-16 19:02         ` 2.5.69-mm6 Andreas Henriksson
2003-05-16 19:25           ` 2.5.69-mm6 Dave Jones
2003-05-17 22:06 ` 2.5.69-mm6 Diego Calleja García
2003-05-18 11:36   ` 2.5.69-mm6 Helge Hafting
2003-05-18 13:05     ` 2.5.69-mm6 Diego Calleja García
2003-05-18 13:58       ` 2.5.69-mm6 Rudmer van Dijk
2003-05-16 19:35 2.5.69-mm6 Alistair Strachan
2003-05-16 21:06 ` 2.5.69-mm6 Andrew Morton
2003-05-16 20:26 2.5.69-mm6 mikpe
2003-05-17  1:23 2.5.69-mm6 Chuck Ebbert
2003-05-17 12:51 ` 2.5.69-mm6 Alan Cox
2003-05-17 18:52   ` 2.5.69-mm6 Oleg Drokin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1053099462.5599.1.camel@dhcp22.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=ahu@ds9a.nl \
    --cc=akpm@digeo.com \
    --cc=ch@murgatroid.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®