All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Masover <ninja@slaphack.com>
To: Islam Amer <pharon@gmail.com>
Cc: Hans Reiser <reiser@namesys.com>,
	Valdis.Kletnieks@vt.edu, Fionn Behrens <fionn@spamfilter.de>,
	reiserfs-list@namesys.com
Subject: Re: iosched (was Re: Full of surprises - A reiser4 story from userland)
Date: Wed, 28 Sep 2005 19:55:39 -0500	[thread overview]
Message-ID: <433B3B8B.5090007@slaphack.com> (raw)
In-Reply-To: <5d8b7b9050928133842241311@mail.gmail.com>

Islam Amer wrote:

> Problem is lots of experimental patches in -mm series hurt throughput
> and performance and reiser4 users have to suffer. Otherwise we have to
> go through the slightly non-trivial procedure of patching the vanilla
> kernel.

Non-trivial?  How's this:

for i in `egrep '^reiser4' ../broken-out/series`; do
	patch -p1 < ../broken-out/$1;
done

That won't always work, but it's certainly trivial.

Places it won't work:  patch names with spaces (won't happen), commented
patches (just generates weird errors), and a couple of kernels also need
the attached patch.  I don't remember which ones, but you get a compiler
error unless you've got it right.

It'll also fail (obviously) if anything's changed since I last checked.

  parent reply	other threads:[~2005-09-29  0:55 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-28 13:40 Full of surprises - A reiser4 story from userland Fionn Behrens
2005-09-28 14:12 ` Domenico Andreoli
2005-09-28 14:51   ` Clemens Eisserer
2005-09-28 15:35     ` Fionn Behrens
2005-09-28 14:25 ` Vitaly Fertman
2005-09-28 14:51   ` Islam Amer
2005-09-28 15:56     ` Fionn Behrens
2005-09-28 18:13       ` Hans Reiser
2005-09-28 18:07     ` Hans Reiser
2005-09-28 15:28   ` Fionn Behrens
2005-09-28 15:57     ` David Masover
2005-09-28 18:32       ` Fionn Behrens
2005-09-28 19:13         ` Islam Amer
2005-09-28 19:52           ` iosched (was Re: Full of surprises - A reiser4 story from userland) Valdis.Kletnieks
2005-09-28 20:31             ` Islam Amer
2005-09-28 20:48               ` Hans Reiser
2005-09-28 20:32             ` Hans Reiser
2005-09-28 20:38               ` Islam Amer
2005-09-28 20:48                 ` vs, can you port to 2.6.13 and put the port on our website as part of analyzing the latest patches added to the -mm series and their impact on reiser4 performance Hans Reiser
2005-09-29 15:05                   ` Vladimir V. Saveliev
2005-09-29  0:55                 ` David Masover [this message]
2005-09-29  1:22                   ` iosched (was Re: Full of surprises - A reiser4 story from userland) michael chang
2005-09-29  9:34                     ` Islam Amer
2005-09-29 18:47                       ` David Masover
2005-09-29 19:01                         ` Dan Oglesby
     [not found]               ` <5a59ce53050928143267c9d779@mail.gmail.com>
2005-09-28 21:33                 ` studdugie
2005-09-28 22:20                   ` Jonathan Briggs
2005-09-28 16:40     ` Full of surprises - A reiser4 story from userland Vitaly Fertman
2005-09-28 17:57       ` Fionn Behrens
2005-09-28 20:05         ` Vitaly Fertman
2005-09-28 18:11     ` Hans Reiser
2005-09-28 15:39 ` Ingo Bormuth

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=433B3B8B.5090007@slaphack.com \
    --to=ninja@slaphack.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=fionn@spamfilter.de \
    --cc=pharon@gmail.com \
    --cc=reiser@namesys.com \
    --cc=reiserfs-list@namesys.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.