All of lore.kernel.org
 help / color / mirror / Atom feed
From: vda <vda@port.imtp.ilyichevsk.odessa.ua>
To: Robert Love <rml@tech9.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] Smbfs + preempt on 2.4.10
Date: Tue, 30 Oct 2001 13:23:52 +0000	[thread overview]
Message-ID: <01103013235202.00855@nemo> (raw)
In-Reply-To: <01102919120800.05333@nemo> <3BDDA646.B5D0E526@lexus.com> <1004388815.805.11.camel@phantasy>
In-Reply-To: <1004388815.805.11.camel@phantasy>

On Monday 29 October 2001 20:53, you wrote:
> > > I narrowed down Samba weirdness I observe on 2.4.10 to preempt patch.
> > > Plain 2.4.10 works fine, 2.4.10+preempt (with latency measurement
> > > turned on) is sometimes oopses, and sometimes reports 'file already
> > > exists' when I attempt to copy a file from WinNT box to Linux.
> > > Sometimes it works ok (50% or so...)
> >
> > Why not try a recent kernel + preempt?
>
> Yes, would you mind retesting on a recent kernel and a recent patch?

Will try 2.4.13 and report.

BTW:
I'd like to reduce latency in one specific place which bites me most
(latencies up to 400000usec) coz I use VESA fb:
a BKL in tty_io.c:712 (in do_tty_write()).
It looks like we need to move BKL into write()
and/or replace it with spinlock.
I can't find where that write() func ptr is coming
(tracked it to tty->ldisc.write, but failed to find out
where that field is assigned to).
Somebody enlighten me...

BTW #2:
You're doing excellent work, Robert. Thank you.
--
vda

  reply	other threads:[~2001-10-30 11:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-29 19:12 [BUG] Smbfs + preempt on 2.4.10 vda
2001-10-29 18:17 ` Urban Widmark
2001-10-29 18:56 ` J Sloan
2001-10-29 20:53   ` Robert Love
2001-10-30 13:23     ` vda [this message]
2001-10-30 11:57       ` Alan Cox
2001-10-31 12:55         ` vda
2001-10-31 12:10     ` vda
2001-11-05 17:01     ` vda
2001-11-05 15:18       ` Urban Widmark
     [not found] <Pine.LNX.4.10.10110291339010.27909-100000@coffee.psychology.mcmaster.ca>
2001-10-31 12:05 ` vda

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=01103013235202.00855@nemo \
    --to=vda@port.imtp.ilyichevsk.odessa.ua \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.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 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.