From: Neil Brown <neilb@cse.unsw.edu.au>
To: Frank Cusack <fcusack@fcusack.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: help backporting workqueue to 2.4; for net/sunrpc/cache.c
Date: Fri, 4 Jul 2003 22:07:49 +1000 [thread overview]
Message-ID: <16133.28181.941806.630834@gargle.gargle.HOWL> (raw)
In-Reply-To: message from Frank Cusack on Friday July 4
On Friday July 4, fcusack@fcusack.com wrote:
> Hi all,
>
> Should I expect any problems backporting the 2.5 workqueue.c to 2.4?
> It looks pretty straightforward, but I am {naive,novice}. The only
> interesting looking bit is setting current->flags |= PF_IOTHREAD,
> which doesn't exist in 2.4. At a glance, it looks like I can ignore
> this; it's used in suspend.c which doesn't exist in 2.4 either.
>
> The reason I'd like to backport this is because of changes in sunrpc
> which now use the workqueue to clean auth caches. Related question:
> how is this (periodic cache clean) done in 2.5.73 and earlier?
> net/sunrpc/cache.c didn't use the workqueue until 2.5.74.
The nfsd threads called cache_clean() from nfsd() in nfsd/nfssvc.c,
whenever they didn't have anything else to do, but this wasn't really
often enough. You could probably get them to do it after every
request as cache_clean() does virtually nothing unless there is
evidence that something needs doing.
NeilBrown
>
> Any advice is appreciated.
>
> thanks
> /fc
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2003-07-04 11:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-04 11:35 Frank Cusack
2003-07-04 12:07 ` Neil Brown [this message]
2003-07-04 16:21 ` Marc-Christian Petersen
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=16133.28181.941806.630834@gargle.gargle.HOWL \
--to=neilb@cse.unsw.edu.au \
--cc=fcusack@fcusack.com \
--cc=linux-kernel@vger.kernel.org \
/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®