From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Andrew Morton <akpm@osdl.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
Alexander Viro <viro@parcelfarce.linux.theplanet.co.uk>,
manfred@colorfullife.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC] kill sleep_on
Date: Sun, 18 Jan 2004 01:57:54 -0500 [thread overview]
Message-ID: <1074409074.1569.12.camel@nidelv.trondhjem.org> (raw)
In-Reply-To: <20040117224139.5585fb9c.akpm@osdl.org>
På su , 18/01/2004 klokka 01:41, skreiv Andrew Morton:
> It would be nice to fix up the lock_kernel()s in the NFS client: SMP lock
> contention is quite high in there.
Chuck did a study of that particular issue some 2-3 years ago, but we've
addressed all the top problems on his list since then. Do you have any
new numbers to show us? I ask because I'm not at all convinced that the
BKL adds significantly to our latencies for the moment (I've been
looking at those number in the last few days due to the readahead
problems that have already been reported).
I am, however, quite convinced that we need new statistics on this sort
of issue. Chuck is therefore working on a set of patches to add an
"iostat"-like tool to the NFS client. Hopefully that will help settle
these questions.
Cheers,
Trond
next prev parent reply other threads:[~2004-01-18 6:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 18:43 Manfred Spraul
2004-01-17 19:19 ` Arjan van de Ven
2004-01-17 19:28 ` David Woodhouse
2004-01-17 20:10 ` viro
2004-01-17 23:18 ` Trond Myklebust
2004-01-17 23:45 ` David Woodhouse
2004-01-18 6:41 ` Andrew Morton
2004-01-18 6:57 ` Trond Myklebust [this message]
2004-01-18 7:05 ` Trond Myklebust
2004-01-18 7:36 ` Andrew Morton
2004-01-18 7:44 ` Manfred Spraul
2004-01-18 8:03 ` Trond Myklebust
2004-01-18 8:18 ` Manfred Spraul
2004-01-18 17:07 ` Trond Myklebust
2004-01-18 7:54 ` Trond Myklebust
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=1074409074.1569.12.camel@nidelv.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=akpm@osdl.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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
all inboxes | Powered by JetHome®