9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] interface for per process gdt manipulation
Date: Mon, 15 Jun 2009 23:00:46 -0700	[thread overview]
Message-ID: <dd6fe68a0906152300h2df2b61dx35b6648625b1c615@mail.gmail.com> (raw)
In-Reply-To: <b84f17381aebb941c76d61e7abde7bc3@gmx.de>

On Mon, Jun 15, 2009 at 10:37 PM, <cinap_lenrek@gmx.de> wrote:
>> i haven't looked at your code,
>> but a text interface is better than binary.
>> if you make the first field the table index number,
>> then you don't need to bother with seeking
>> to fixed offsets.  design a text format that is
>> convenient to use instead of forcing the binary
>> interface on everyone.
>
> thats a good idea. i'll look into it. should the descriptor be
> presented in a decoded/splitted up form or just be the text
> representation of the numerical values?

i would hope the former; that's what i meant by
design a text format that is convenient to use.
ideally, cat /dev/gdt should give me something
that is easily human-readable, and if i feed the
lines back into /dev/gdt one at a time
    aux/lines </dev/gdt >/dev/gdt
it should be valid input.

>> also i wonder if this should really be in
>> a separate ldt instead of polluting the gdt.
>
> older versions of glibc use an ldt entry per thread but it got
> deprecated for tls use by set_thread_area wich works only with with
> gdt entries.
>
> also ldt is not supported on amd64, but gdt segments are still
> present and used for tls on linux.

good to know; thanks.

russ


      reply	other threads:[~2009-06-16  6:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16  3:46 cinap_lenrek
2009-06-16  3:52 ` Russ Cox
2009-06-16  5:37   ` cinap_lenrek
2009-06-16  6:00     ` Russ Cox [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=dd6fe68a0906152300h2df2b61dx35b6648625b1c615@mail.gmail.com \
    --to=rsc@swtch.com \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).