All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manuel Krause <manuel.krause@mb.tu-ilmenau.de>
To: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
Cc: "Yury Yu. Rupasov" <yura@yura.polnet.botik.ru>,
	reiserfs-list <reiserfs-list@namesys.com>
Subject: Re: Comparison of notail and notail,iicache(14)  2.4.19-pre7
Date: Fri, 26 Apr 2002 23:21:58 +0200	[thread overview]
Message-ID: <3CC9C4F6.2090508@mb.tu-ilmenau.de> (raw)
In-Reply-To: 200204261845.45178.Dieter.Nuetzel@hamburg.de

On 04/26/2002 06:45 PM, Dieter Nützel wrote:

> On Friday 26 April 2002 13:41, Yury Yu. Rupasov wrote:
> 
>>Dieter Nützel wrote:
>>
>>>Manuel Krause wrote:
>>>
>>>[-]
>>>
>>>>What's really unclear is the problem with my
>>>>failing Netscape files on the living iicache-mounted FS...
>>>>
>>>I had one outlier with iicache-new-13 here, too.
>>>
>>>/etc/cups/ppds.dat
>>>
>>>couldn't be accessed. I reported back but got no response.
>>>
> 
> [-]
> 
>>>Next thing could be linux-2.4.19p6-compound-speedup.patch.
>>>Any version for -pre7 ready?
>>>
>>This patch should work with linux-2.4.19-pre7 as well.
>>
> 
> Yes, Yura.
> I tried it today and got one rejection with preempt+lock-break.
> fs/reiserfs/journal.c.rej
> 
[-]
> 
> Had that before but Chris and Oleg gave me advice.
> I tried it this way:
> 
> /* lock the current transaction */
> inline static void lock_journal(struct super_block *p_s_sb) {
>   PROC_INFO_INC( p_s_sb, journal.lock_journal );
>   debug_lock_break(1);
>   conditional_schedule();
>   down(&SB_JOURNAL(p_s_sb)->j_lock);
> }
> 
> /* unlock the current transaction */
> inline static void unlock_journal(struct super_block *p_s_sb) {
>   up(&SB_JOURNAL(p_s_sb)->j_lock);
> }
> 
> But then it seems to be _NOT_ preempt (+lock-break) save.
> System lock up (nothing in the logs, SysRq key didn't work) during 
> latencytest0.42-png write test. Read test worked.
> 
> Thanks,
> 	Dieter
> 
> 

Mmh, I made this adjustment in the patch, too, since the first speedup 
patches had been posted. I really don't know how serious this could be 
in this code context.

I had random hard locks,too, but blamed it to my degenerating hardware 
so far. Could anyone else advise on preempt+lock-break-awareness here?

The linux-2.4.19p6-compound-speedup.patch seems to be another measurable 
tick faster than Olegs first patchset. Maybe, I'll post some values on 
my setup over the weekend. I've had one faster run so far but it locked 
up without log hints... ;-))


Best regards,

Manuel



  reply	other threads:[~2002-04-26 21:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-26  4:57 Comparison of notail and notail,iicache(14) 2.4.19-pre7 Dieter Nützel
2002-04-26 11:41 ` Yury Yu. Rupasov
2002-04-26 16:45   ` Dieter Nützel
2002-04-26 21:21     ` Manuel Krause [this message]
2002-04-26 22:00       ` Dieter Nützel
2002-04-26 22:56         ` Manuel Krause
  -- strict thread matches above, loose matches on Subject: below --
2002-04-24 22:25 Manuel Krause
2002-04-24 22:51 ` Manuel Krause
2002-04-25  1:09   ` Manuel Krause
2002-04-25  2:16     ` Manuel Krause
2002-04-25 10:37   ` Hans Reiser
2002-04-26  1:09     ` Manuel Krause

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=3CC9C4F6.2090508@mb.tu-ilmenau.de \
    --to=manuel.krause@mb.tu-ilmenau.de \
    --cc=Dieter.Nuetzel@hamburg.de \
    --cc=reiserfs-list@namesys.com \
    --cc=yura@yura.polnet.botik.ru \
    /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.