Home arrow Forums
OSDEV Forums  


root
User

Platinum Osdever
Posts: 121
graphgraph
Karma: 1  
Brand new Articles section - 2005/05/23 06:56 Hello,

I've integrated a new section along with the reface, where we will publish the OSDEV articles. They will look similar, and please let me know what do you think about the way (layout) of displaying the documents.

I've also published my 1st article about Round Robin Scheduling, if you have any comments/suggestions the review box under the article is waiting!

Round Robin Scheduling

[ Edited ]
  | | The administrator has disabled public write access.
OSDEV
Community
Advertisement
   
gaf
User

Platinum Osdever
Posts: 153
graph
Karma: 10  
Re: Brand new Articles section - 2005/05/25 10:50 I think it's bit confusing to have both, categories a articles, on one level, especially if they look that similiar..

In my opinion a nested view might be a good alternate (I've uploaded some 'artwork'). With the number of articles growing the site will eventually get pretty long, however. This problem can be circumvented if only the categories are visible when the site first loads. You can then chose one of them and the articles belonging to it will be appear as a dropdown.
This could also be implemented pretty easy if you just use a main-site for the closed categories and then link each catagory to a site on which it's opened.

Btw: Nice article! I hope that I'll also find some time to write some tutorials myself soon, at the moment I'm pretty busy finishing the design concept for my os project..

regards,
gaf
  | | The administrator has disabled public write access.
root
User

Platinum Osdever
Posts: 121
graphgraph
Karma: 1  
Re: Brand new Articles section - 2005/05/25 17:08 Hi gaf,

I do agree with you, but I have to see how can I edit the e107 files to work like that. I like the nested view layout, thanks.

This, along with the suggestions you made on the previous thread about the new layout are issues I also noted, but there's a bit of a problem: I can edit the files to work as we want, but I'm looking forward for the final release of e107 v0.7, which is slightly different, and a proper upgrade to it would be impossible.

Thanks for looking into writing some articles. If I remember correctly you almost finished a boot related one, am I right?
  | | The administrator has disabled public write access.
bubach
User

Senior Osdever
Posts: 33
graphgraph
Karma: 0  
Re: Brand new Articles section - 2005/05/26 03:45 Once I finish my floppy code, I'll definitely going to write a tutorial about it.
Haven't found any good ( with steps and sample code ) and I don't understand much about the intel manuals..

/ Christoffer
  | | The administrator has disabled public write access.
root
User

Platinum Osdever
Posts: 121
graphgraph
Karma: 1  
Re: Brand new Articles section - 2005/05/26 07:14 That's good news. Speaking of Intel, I've recently finished a HyperThreading document (the interest came since the HTT vulnerabilities rummors and Percival's docs).

http://www.osdcom.info/content.php?article.6
[ Edited Thu May 26 2005, 12:17PM ]
  | | The administrator has disabled public write access.
gaf
User

Platinum Osdever
Posts: 153
graph
Karma: 10  
Re: Brand new Articles section - 2005/05/26 09:22 I've read the article and really like it because it's brief and yet pretty complete. There are however some sections in the text that might be misunderstood by a reader that isn't yet very experienced with os dev:

1) In the paragraph (#6+7) that explain what a process is, you write that threads can have an "own local context in addition to the process's context" which might also be interpreted as "threads have their own address-space". It might therefore be usefull to further divide the term context into address-space and register state (->thread).

Process: task + OS data (all kind of handlers: file, wnd, ...)
Task: context (->address-space) + threads that run in this context
Thread: state of the cpu (cpu regs, kernel structs like TCBs)
address-space: context that a thread runs in (mapped memory pages and I/O ports)

2) In paragraph #10 you state that "the same amount of work gets done in both (multiprocessor, ht) systems , but the HyperThreaded system uses a fraction of the resources and has a fraction of the waste of the SMP system". If you say so you must mention that it's only true when the tasks running on the two processors always execute instructions that use different parts of the processor (eg: proc1 - mem, proc2- add). Since this is never the case in real-life, the processor can't always execute two instructions at one and a HT system thus can't perform as good as a real multiprocessor. (You mentioned this in the following paragraph, but IMHO it's not totaly clear that these two belong together)

3) What you describe in paragraph #12 is only half of the story. In order to attain the best performance, the applications themselves also have to be rewritten to do their calculations in several threads that can then be scheduled on both processors. This is especially important for CPU demanding applications like games that normally run more or less alone on the system.

4) Paragraph #14: SMP stands for "Symetric Multiprocessor" and not "Symetric Multiprocessing". I know that this doesn't sound like a very important issue, but it does make a difference:
- Multiprocessing is the execution of several programms at the "same" time (m$: Multitasking)
- Multiprocessor systems have several processors that are all on the same machine, using the same ressources (eg mem, disk, ..)

5) Paragraph #16 is somewhat misleading because you still need a SMP system to run a HT processor. AFAIK there are also some special instructions (monitor?) that allow to optimize a HT processor's performace and that might have to be added to the SMP code.

regards,
gaf
  | | The administrator has disabled public write access.

A WebArticles site. Sponsored by Evoleto. Motorola V525 / Business Directory / Delaware Incorporation / Home Made Bazaar