[Subject Prev][Subject Next][Thread Prev][Thread Next][Subject Index][Thread Index]
Re: [LI] struct task
Hello there,
If this mail was off-topic, then what do you call something
on-topic. ;-) Basically, yours is a perfectly valid on-topic
question . ;-) And as for the answer, I think I will get back to
you after some days. ;-)
Regards
Khader
Syed Khader Vali skhader@xxxxxxxxxx
Associate Technical Executive # 91-80-5262355 Extn:2527
IBM Global Services India (P) Ltd.
sudheer@xxxxxxxxxxxxx on 11/25/99 02:12:42 PM
Please respond to linux-india@xxxxxxxxxxxxxxxxxxxxx
To: linux-india@xxxxxxxxxxxxxxxxxxxxx
cc: (bcc: Khader V Syed/India/IBM)
Subject: [LI] struct task
*Please pardon me if it's off topic
Hi,
We know that in unix for copying back and forth between kernel
and user space, we use "struct user" defined in sys/user.h. There we get
the base offset for IO.
Could anyone please tell me what's it's analogous struct in Linux.
Is it "struct task". Though i'm trying i don't get the complete idea
of what's happening. I don't understand from where it get's the offset
for IO operation.
Any pointers on this is highly appreciated. where can i find the relevant
code in source tree.
sudheer
------------------------------------------------------------------------
Think you're ready for Dreamcast? Get all the news, previews and
prices at CNET.com. It?s your source for the latest and greatest
in gaming! http://clickhere.egroups.com/click/1609
eGroups.com Home: http://www.egroups.com/group/linux-india-programmers/
http://www.egroups.com - Simplifying group communications
--------------------------------------------------------------------
The Linux India Mailing List Archives are now available. Please search
the archive at http://lists.linux-india.org/ before posting your question
to avoid repetition and save bandwidth.
--------------------------------------------------------------------
The Linux India Mailing List Archives are now available. Please search
the archive at http://lists.linux-india.org/ before posting your question
to avoid repetition and save bandwidth.