From: Petko Manolov <petkan@varel.bg>
To: mingo@chiara.csoma.elte.hu
Cc: linux-kernel@vger.rutgers.edu
Subject: Unlimited number of processes, x86, 2.1.131
Date: Tue, 08 Dec 1998 18:51:12 +0200 [thread overview]
Message-ID: <366D5900.201AF930@varel.bg> (raw)
In-Reply-To: Pine.LNX.3.96.981208013108.1838A-100000@localhost
> sure. I've attached a cleartext version too. (it's my freshest version,
> one slight bug fixed and some debugging code removed)
>
> feel free to ask questions and please Cc: linux-kernel too, so others see
> the questions too. (and thus i have to answer them only once :)
Ok, the patch applied cleanly. Sadly there was a problem with compiling.
You'd forgot to comment mmu_cr4_features in arch/i386/mm/init.c and
linkker is moaning for duplicate. The variable is in
arch/i386/kernel/setup.c. Except this all went OK. I'm writing this
with your kernel running ;-).
If i understand correctly this can't be aplied for 2.0.xx series -
you remove tr field from tss struct(as tss itself) - where we do
task switch thru TSS descriptor in GDT. But this is obviously not
necessery for 2.1.xxx where we do SW task switch.
I'm still not so familiar with the patch, but "soft_thread_struct" is
far smaller than task_struct and this should be an improvement for
clone().
All this is general change of concept (GDT, task structures, etc...)
and i'm curious what Linus will say about this ;-))
regards
--
Petko Manolov - petkan@varel.bg
http://www.varel.bg/~petkan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~1998-12-08 14:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-08 0:01 [patch] Unlimited number of processes, x86, 2.1.131 mingo
1998-12-08 16:51 ` Petko Manolov [this message]
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=366D5900.201AF930@varel.bg \
--to=petkan@varel.bg \
--cc=linux-kernel@vger.rutgers.edu \
--cc=mingo@chiara.csoma.elte.hu \
/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