From: Willy TARREAU <willy@w.ods.org>
To: Mathias Kretschmer <posting@blx4.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] Linux Kernel Useful Patches (2.4)
Date: Sat, 4 Feb 2006 19:15:54 +0100 [thread overview]
Message-ID: <20060204181554.GG6026@w.ods.org> (raw)
In-Reply-To: <43E27895.4010904@blx4.net>
On Thu, Feb 02, 2006 at 10:24:37PM +0100, Mathias Kretschmer wrote:
> Willy Tarreau wrote:
> >Hi all,
> >
> >after some discussions with some people, I made available a collection of
> >useful patches for kernel 2.4. There are only a dozen of patches right
> >now, but it's very easy to add more. Amongst those patches can be found
> >some drivers, security enhancements, polling optimisations, gcc4 fixes,
> >VM optimisations, etc... Links to the original sites as well as a local
> >mirror are provided.
> >
> >They are classified by categories and can easily be found in more than
> >one category. I plan to add many more patches such as ACL, squashfs,
> >preempt, netdev-random, patch-o-matic, etc... when I have the time, and
>
> O(1) and low latency would also be interesting candidates for inclusion.
The last O(1) patch I've seen does not apply to kernels more recent than 2.4.19
(it's on Ingo's site). Do you have any up to date pointer that I could use ?
However, I have a local rediff of the lowlat patch that I will include.
> BTW, does anyone know about the state of the (l)ck patches for recent
> 2.4 kernels ?
No idea.
Regards,
Willy
next prev parent reply other threads:[~2006-02-04 18:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-30 8:52 [ANNOUNCE] Linux Kernel Useful Patches (2.4) Willy Tarreau
2006-01-30 14:33 ` Thomas Voegtle
2006-02-02 21:24 ` Mathias Kretschmer
2006-02-04 18:15 ` Willy TARREAU [this message]
2006-02-04 20:54 ` Barry K. Nathan
2006-02-04 22:24 ` Willy Tarreau
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=20060204181554.GG6026@w.ods.org \
--to=willy@w.ods.org \
--cc=linux-kernel@vger.kernel.org \
--cc=posting@blx4.net \
/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