From: Arnd Bergmann <arnd@bergmann-dalldorf.de>
To: Tim Schmielau <tim@physik3.uni-rostock.de>,
lkml <linux-kernel@vger.kernel.org>
Cc: John Levon <levon@movementarian.org>
Subject: Re: [patch] tasks.h
Date: Sat, 12 Oct 2002 17:03:11 +0200 [thread overview]
Message-ID: <200210121703.11220.arnd@bergmann-dalldorf.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0210120842070.25918-100000@gans.physik3.uni-rostock.de>
On Saturday 12 October 2002 08:59, Tim Schmielau wrote:
> More work will be neccessary to completely disentangle both files, so that
> sched.h doesn't need to include tasks.h. Biggest obstacle is get_task_mm()
> which needs both task_struct and mm_struct. Maybe I'll break out something
> like a <linux/task_mm.h> later.
AFAICS, get_task_mm() is never used in a fast path, only in
ptrace and procfs code where a few cpu cycles don't hurt anyone.
Any reason why you can't just make it an extern function?
Arnd <><
next prev parent reply other threads:[~2002-10-12 12:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-12 6:59 Tim Schmielau
2002-10-12 15:03 ` Arnd Bergmann [this message]
2002-10-12 15:21 ` John Levon
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=200210121703.11220.arnd@bergmann-dalldorf.de \
--to=arnd@bergmann-dalldorf.de \
--cc=levon@movementarian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tim@physik3.uni-rostock.de \
/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®