From: Andrea Arcangeli <andrea@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: ink@jurassic.park.msu.ru, ezolt@perf.zko.dec.com,
axp-list@redhat.com, rth@twiddle.net, Jay.Estabrook@compaq.com,
linux-kernel@vger.kernel.org, clinux@zk3.dec.com,
wcarr@perf.zko.dec.com, linux-alpha@vger.kernel.org
Subject: Re: mm->context[NR_CPUS] and pci fix check [was Re: Alpha SCSI error on 2.4.0-test11]
Date: Fri, 15 Dec 2000 18:55:28 +0100 [thread overview]
Message-ID: <20001215185528.C17781@inspiron.random> (raw)
In-Reply-To: <20001201004049.A980@jurassic.park.msu.ru> <Pine.OSF.3.96.1001130171941.32335D-100000@perf.zko.dec.com> <20001130233742.A21823@athlon.random> <20001201145619.A553@jurassic.park.msu.ru> <20001201151842.C30653@athlon.random> <200012011819.KAA02951@pizda.ninka.net> <20001201201444.A2098@inspiron.random> <20001215164626.C16586@inspiron.random> <200012151711.JAA20826@pizda.ninka.net>
In-Reply-To: <200012151711.JAA20826@pizda.ninka.net>; from davem@redhat.com on Fri, Dec 15, 2000 at 09:11:31AM -0800
On Fri, Dec 15, 2000 at 09:11:31AM -0800, David S. Miller wrote:
> Can you name the mm_struct member "context" [..]
I got you was proposing that but once we change it I preferred to use a generic
mm_arch structure (not just a context field) to have a more generic interface
in the long run. (maybe some port wants to collect something else than a MM
`context')
> Then all the code changes will make the accesses look less
> meaningful. Consider:
>
> if (CTX_VALID(mm->mm_arch))
>
> whereas before the code said:
>
> if (CTX_VALID(mm->context))
>
> which tells the reader lot more. [..]
What I propose is to convert the current:
if (CTX_VALID(mm->context))
to
if (CTX_VALID(mm->mm_arch.context))
(that's the same I did in the alpha tree from mm->context[] to
mm->mm_arch.context[])
I'm aware this way all ports actively using `mm->context' needs to be changed
but the change is certainly a no-brainer... OK?
Andrea
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-15 18:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-30 20:02 Alpha SCSI error on 2.4.0-test11 Phillip Ezolt
2000-11-30 20:37 ` Peter Rival
2000-11-30 21:40 ` Ivan Kokshaysky
2000-11-30 22:26 ` Phillip Ezolt
2000-11-30 22:37 ` Andrea Arcangeli
2000-12-01 11:56 ` Ivan Kokshaysky
2000-12-01 14:18 ` mm->context[NR_CPUS] and pci fix check [was Re: Alpha SCSI error on 2.4.0-test11] Andrea Arcangeli
2000-12-01 18:19 ` David S. Miller
2000-12-01 19:14 ` Andrea Arcangeli
2000-12-15 15:46 ` Andrea Arcangeli
2000-12-15 17:11 ` David S. Miller
2000-12-15 17:55 ` Andrea Arcangeli [this message]
2000-12-15 17:44 ` David S. Miller
2000-12-01 18:30 ` Alpha SCSI error on 2.4.0-test11 Phillip Ezolt
2000-12-01 19:35 ` Andrea Arcangeli
2000-12-01 19:56 ` Phillip Ezolt
2000-12-01 20:26 ` Andrea Arcangeli
2000-12-05 15:52 ` Phillip Ezolt
2000-12-01 22:11 ` Ivan Kokshaysky
2000-12-04 18:53 ` Phillip Ezolt
2000-12-06 0:06 ` Jay Estabrook
2000-12-06 14:51 ` Phillip Ezolt
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=20001215185528.C17781@inspiron.random \
--to=andrea@suse.de \
--cc=Jay.Estabrook@compaq.com \
--cc=axp-list@redhat.com \
--cc=clinux@zk3.dec.com \
--cc=davem@redhat.com \
--cc=ezolt@perf.zko.dec.com \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.net \
--cc=wcarr@perf.zko.dec.com \
/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