:I don't think the current approach with %fs is that confusing. :-) You
:can view it as an optimization of
:
: struct "per processor data" {
: struct proc *curproc;
: ...
: } ppd[NCPUS];
:
: some_func()
: {
: ... ppd[MYCPU]->curpr
On Wed, Apr 28, 1999 at 02:48:56PM -0700, Matthew Dillon wrote:
>
> ...
>
> There might be less confusion with %fs if we simply use it as a
> 'cpu number' index and then make all the cpu-dependant variables
> standard arrays. i.e. instead if 'struct proc *curproc' we would
>
:On Wed, Apr 28, 1999 at 11:19:17AM -0700, Matthew Dillon wrote:
:> I know this is a little late ... but I don't suppose there might be a
:> way to lock a TLB entry in place? That would solve the problem too.
:> Baring that, %fs is the way to go.
:>
:
:Unfortunately, on the x86, the a
On Wed, Apr 28, 1999 at 11:19:17AM -0700, Matthew Dillon wrote:
> I know this is a little late ... but I don't suppose there might be a
> way to lock a TLB entry in place? That would solve the problem too.
> Baring that, %fs is the way to go.
>
Unfortunately, on the x86, the answer i
I know this is a little late ... but I don't suppose there might be a
way to lock a TLB entry in place? That would solve the problem too.
Baring that, %fs is the way to go.
I am happily compiling up a new SMP kernel as we speak :-).
-Matt
On Wed, 28 Apr 1999, Poul-Henning Kamp wrote:
> In message <199904281625.maa05...@lor.watermarkgroup.com>, Luoqi Chen writes:
>
> >> >In this %fs approach, per-processor private pages are no longer mapped at
> >> >identical virtual address for each cpu, instead a new segment descriptor
> >> >(%f
In message <199904281625.maa05...@lor.watermarkgroup.com>, Luoqi Chen writes:
>> >In this %fs approach, per-processor private pages are no longer mapped at
>> >identical virtual address for each cpu, instead a new segment descriptor
>> >(%fs)
>> >is setup to access per-cpu global variables like c
> In message <199904272349.taa28...@lor.watermarkgroup.com>, Luoqi Chen writes:
> >I'm about to commit the SMP vmspace sharing patch (the %fs approach). All
> >kernel modules will need to be recompiled. Recompilation is not neccessary
> >for user land applications including ps, libkvm and friends.
In message <199904272349.taa28...@lor.watermarkgroup.com>, Luoqi Chen writes:
>I'm about to commit the SMP vmspace sharing patch (the %fs approach). All
>kernel modules will need to be recompiled. Recompilation is not neccessary
>for user land applications including ps, libkvm and friends.
>
>In th
I'm about to commit the SMP vmspace sharing patch (the %fs approach). All
kernel modules will need to be recompiled. Recompilation is not neccessary
for user land applications including ps, libkvm and friends.
In this %fs approach, per-processor private pages are no longer mapped at
identical virt
10 matches
Mail list logo
