From: Roberto Fichera <kernel@tekno-soft.it>
To: "David S. Miller" <davem@redhat.com>
Cc: rasmus@jaquet.dk, torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm->rss is modified without page_table_lock held
Date: Sat, 09 Dec 2000 16:07:03 +0100 [thread overview]
Message-ID: <4.3.2.7.2.20001209160215.00c901e0@mail.tekno-soft.it> (raw)
In-Reply-To: <200012091442.GAA20532@pizda.ninka.net>
In-Reply-To: <4.3.2.7.2.20001209152806.00c8e7b0@mail.tekno-soft.it> <4.3.2.7.2.20001209111347.00c829f0@mail.tekno-soft.it> <4.3.2.7.2.20001209111347.00c829f0@mail.tekno-soft.it> <4.3.2.7.2.20001209152806.00c8e7b0@mail.tekno-soft.it>
At 06.42 09/12/00 -0800, David S. Miller wrote:
> Date: Sat, 09 Dec 2000 15:48:05 +0100
> From: Roberto Fichera <kernel@tekno-soft.it>
>
> >atomic_t does not guarentee a large enough range necessary for mm->rss
>
> If we haven't some atomic_t that can be negative we could define atomic_t
> as unsigned long for all arch,
> this is sufficient to fitting all the range for the mm->rss.
>
>32-bit Sparc has unsigned long as 32-bit, and the top 8 bits of the
>atomic_t are used for a spinlock, thus a 27-bit atomic_t, there
>is not enough precision.
8 bits for a spinlock ? What kind of use we have here ? All arch except Sparc32
don't have this trick.
Roberto Fichera.
-
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-09 15:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-08 20:29 Rasmus Andersen
2000-12-08 20:36 ` Mark Hahn
2000-12-08 20:58 ` David S. Miller
2000-12-09 10:25 ` Roberto Fichera
2000-12-09 12:32 ` David S. Miller
2000-12-09 12:43 ` Rasmus Andersen
2000-12-09 14:42 ` David S. Miller
2000-12-09 22:38 ` Albert D. Cahalan
2000-12-09 14:48 ` Roberto Fichera
2000-12-09 15:00 ` David S. Miller
2000-12-09 15:07 ` Roberto Fichera [this message]
2000-12-09 18:11 ` Roberto Fichera
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=4.3.2.7.2.20001209160215.00c901e0@mail.tekno-soft.it \
--to=kernel@tekno-soft.it \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rasmus@jaquet.dk \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®