Difference between "threads" in single core and multi_core CPU ?

I just run into a tutorial describing processes run in multicore CPU as "threads". Not sure I buy that.

Hence what are the accepted terms of TECHNICAL descriptions / differences between

single code CPU running "threads" (used to be just "thread" )
multicore CPU running " ...what... in each core ?"
multicore CPU running in specific core " ...what... multi ... "

what is a basic "process " - in general terms or specifically in multicore CPU ?
Does "process " = "thread" ?

Originally Posted by jan128 I just run into a tutorial describing processes run in multicore CPU as "threads". Not sure I buy that. Hence what are the accepted terms of TECHNICAL descriptions / differences between single code CPU running "threads" (used to be just "thread" ) multicore CPU running " ...what... in each core ?" multicore CPU running in specific core " ...what... multi ... " what is a basic "process " - in general terms or specifically in multicore CPU ? Does "process " = "thread" ?

A "process" is the running instance of a program (eg. firefox, VLC, etc, etc). A "thread" is a part of a running "process", so one process might have many threads of execution.

Difference between Process and Thread

additional info:
https://www.thegeekstuff.com/2013/11...s-and-threads/
https://topic.alibabacloud.com/a/und..._30000800.html

Is this how this forum operates?
Collecting statistical data ?
Are you serious ?

With only ONE out of 3 posts actually addressing the question you all have the nerve to ask "is it solved "?

Are you writing a book ?

(PUT THIS IN THE BOOK...)

NO IT IS NOT SOLVED BY A LONG SHOT

Originally Posted by jan128 Is this how this forum operates? Collecting statistical data ? Are you serious ? With only ONE out of 3 posts actually addressing the question you all have the nerve to ask "is it solved "? NO IT IS NOT SOLVED BY A LONG SHOT

That is just a signature, automatically added to every post.

Anyway, if your problem was not correctly answered please give us more details, what do you need?

Originally Posted by jan128 Is this how this forum operates? Collecting statistical data ? Are you serious ? With only ONE out of 3 posts actually addressing the question you all have the nerve to ask "is it solved "? Are you writing a book ? (PUT THIS IN THE BOOK...) NO IT IS NOT SOLVED BY A LONG SHOT

So what is the actual reason for this post.?

The links posted in the 2 of 3 posts you seem to think did not address your question point to references that need no repetition.

You could easily have found the same links with a quick search, and those links probably have a better answer than most could provide without deep research.

BTW, the part about marking it solved (if solved) is in the poster's signature, not his post. Temperance in your responses please.

As in all things computing, the term is over-loaded. As well as software threads as above, there is also hardware threads. Quick search will fill you in on the basics - start with hyper-thread. In almost (?) all systems these days but was particularly contentious when first introduced as SMT.

Temperance in your responses please.

...and give some real answers , please.

Stupid (no) responses are irritating , ( yes I said stupid ) so are "automatic" requests for "mark as solved " .

BUMP


single code CPU running "threads" (used to be just "thread" )
Answer:
Single core can run multiple threads;


multicore CPU running " ...what... in each core ?"
multicore CPU running in specific core " ...what... multi ... "

Answer:
Each HARDWARE CPU core can run multiple threads.

SOLVED

Originally Posted by syg00 As in all things computing, the term is over-loaded. As well as software threads as above, there is also hardware threads. Quick search will fill you in on the basics - start with hyper-thread. In almost (?) all systems these days but was particularly contentious when first introduced as SMT.

The software threads are also named LWPs, light weight processes. They are a kernel feature.
The hardware threads (x86 names them hyper-threads) are different IDs but land on the same computation registers. This CPU feature can be used to preprocess/decode instructions in parallel and eventually change=optimize execution order.

Originally Posted by jan128 Temperance in your responses please. ...and give some real answers , please. Stupid (no) responses are irritating , ( yes I said stupid ) so are "automatic" requests for "mark as solved " . BUMP single code CPU running "threads" (used to be just "thread" ) Answer: Single core can run multiple threads; multicore CPU running " ...what... in each core ?" multicore CPU running in specific core " ...what... multi ... " Answer: Each HARDWARE CPU core can run multiple threads. SOLVED

Your answer is insufficient, does not cover the original post. So based on this it is definitely not solved.
You asked

what is a basic "process " - in general terms or specifically in multicore CPU ? Does "process " = "thread" ?

which was explained very well just you need to click on the links.

Originally Posted by jan128 Stupid (no) responses are irritating , ( yes I said stupid ) so are "automatic" requests for "mark as solved " .

Originally Posted by jan128 Is this how this forum operates? Collecting statistical data ? Are you serious ? With only ONE out of 3 posts actually addressing the question you all have the nerve to ask "is it solved "? Are you writing a book ? (PUT THIS IN THE BOOK...) NO IT IS NOT SOLVED BY A LONG SHOT

@jan128,

If you haven't already, you may benefit from reviewing information as to how the LQ forums work as well as information about user profiles and signatures.

This information can be found in the various links provided on the side of the page, but here are some of them:
Overall LQ FAQ
User profile features explained
Signatures, avatars, and profile pictures explained
Thread tools explained

Will note that for the Thread tools, the information describes the menu for Thread tools, but it appears out of date. A normal thread tool capability for the originating poster of a technical thread has the ability to "Mark the Thread as Solved".

WRT your concerns, it has already been explained that there is a point in the post where a user's signature is shown. This is designated by a short, straight line. And for my case, I added a line to explain that it is the start of my signature, because other new users have been confused, as you have, in thinking that it was part of my post.

Would also like to point out a few other items:

• No one in this thread has specifically asked you to mark the thread as solved, instead person's signatures offer the suggestion that IF your question is solved, that you may mark it as such so that someone who has the same question can see that the issue was resolved and evaluate if the answer works for them. And as such, if you have further questions about threads, please update us with those additional questions.
• Everyone on this site, including yourself, are volunteers who contribute to this site out of preference and an affinity for the Linux operating system. We welcome your questions as well as responses to help promote Linux understanding.
• The site does have a set of guidelines, also known as LQ Rules which are constructed to help promote a cordial and helpful atmosphere, and also to provide guidelines for what is deemed to be appropriate behavior.
• There also is a subforum LQ Suggestions & Feedback where you can ask questions about the site or open a thread to discuss the site and how it is structured.

Please familiarize yourself with how this site works and avoid responses as you've demonstrated in this thread or here, or here.

Sorry for any confusion where you misconstrued replies from people because of their signatures. Hopefully moving forwards you'll now understand that not all text is intended as the content of the response, but instead some of it is self-styled information that users may choose to have as part of their profile.

Originally Posted by Kory_roy Threads means the ability to read lines of code simultaneously.

AFAIK, this is true for multi-core- or multi-processor systems, only. PSE correct me with background and references, if need be.

Whatever you call “real” or “true” (or even "green"), there has been multitasking on single-processor systems and multi-threading, too. A thread is not an ability but a processing unit. The “at the same time” thing depends on a few factors which do not have to be present to allow that multiple threads and/or tasks are spawned from within the same original process. Time-slices were part of the explanations I had been given in the beginning, but there is more...

BTW. I remember that taks and threads were handled and named differently on MS-OSs, meaning that the expressions cannot be mixed with the same facts and events in Linux – if confusion is not the principal motivation.