The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Thunder from the hill <thunder@ngforever.de>
Cc: Tobias Ringstrom <tori@ringstrom.mine.nu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.19rc2aa1
Date: Tue, 23 Jul 2002 17:03:44 +0200	[thread overview]
Message-ID: <20020723150344.GN1116@dualathlon.random> (raw)
In-Reply-To: <Pine.LNX.4.44.0207181530390.3911-100000@hawkeye.luckynet.adm>

On Thu, Jul 18, 2002 at 03:34:51PM -0600, Thunder from the hill wrote:
> Hi,
> 
> On Thu, 18 Jul 2002, Tobias Ringstrom wrote:
> > Why are you not changing the EXTRAVERSION in your patch?  I would make it 
> > much easier to diffrentiate between kernels.
> 
> I did that for me.
> 
> # uname -r
> 2.4.19-rc2-aa1
> # 
> 
> It's working fine for some hours now. The EXTRAVERSION is the only thing 
> that I changed, and -rc2-aa1 works just fine. But my bdflush seems - with 
> the same values as from -rc1-aa2 - not to have 100% of the old efficiency 
> any more.

I guess it's your userspace workload that changed, there are no
bdflush/vm/blkdev related changes between rc1aa2 and rc2aa1 that can
explain a change of behaviour in bdflush.

Andrea

  reply	other threads:[~2002-07-23 14:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-17 22:55 2.4.19rc2aa1 Andrea Arcangeli
2002-07-18 10:16 ` 2.4.19rc2aa1 Tobias Ringstrom
2002-07-18 21:34   ` 2.4.19rc2aa1 Thunder from the hill
2002-07-23 15:03     ` Andrea Arcangeli [this message]
2002-07-19 16:58 ` 2.4.19rc2aa1 J.A. Magallon
2002-07-19 17:03 ` 2.4.19rc2aa1 J.A. Magallon
  -- strict thread matches above, loose matches on Subject: below --
2002-07-19 23:05 2.4.19rc2aa1 Feldman, Scott
2002-07-20  0:10 ` 2.4.19rc2aa1 J.A. Magallon
2002-07-20  0:27 ` 2.4.19rc2aa1 J.A. Magallon

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=20020723150344.GN1116@dualathlon.random \
    --to=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thunder@ngforever.de \
    --cc=tori@ringstrom.mine.nu \
    /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