Re: Need help understanding memory models, cpu modes and address translation

2011-07-17 Thread Joel A Fernandes
On Sun, Jul 17, 2011 at 1:24 AM, Vaibhav Jain  wrote:
> Thanks a lot Joel! This is a great explanation.
> Just one more question. I used to think that the compiler always
> assigns/generates starting from 0 as Mulyadi has also mentioned.
> In the case when Segmentation(intel-style) is being used how does the
> compiler assigns
> addresses?
>

The compiler just generates code as if segmentation is not being
used.I'm not familiar with segmentation in x86 Protected mode. Further
because Linux doesn't uses segmentation (the logical addresses are
one-to-one mapped to virtual addresses) so neither have I really cared
about how it works ;) The compiler just generates code as if
segmentation is not being used. But I'd say some google searches on
"Global Descriptor Table" would give you some pointers.

You shouldn't worry about segmentation too much because virtual
addressing achieves everything it does and is more flexible. I'd say
ignore segmentation and focus on paging. :)

Thanks,
Joel

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


Re: interview question how does application connects to device

2011-07-17 Thread Greg Freemyer
On Sun, Jul 17, 2011 at 1:34 PM, Bond  wrote:
> On Sun, Jul 17, 2011 at 9:36 PM, Mulyadi Santosa
>  wrote:
>> On Sun, Jul 17, 2011 at 22:52, Bond  wrote:
>>> Let me know what do you understand from this.
>>
>>
>> And Greg already kindly answer that for you too. Didn't you see his
>> answer? And why do you rant here anyway? Simply getting an answer
>> here, you already lucky and you should be thankful.
>>
>> --
> Let me know which part of answer answered as how application connects
> to particular driver.I see answer explaining finer details of device
> driver mehcanism but I did not see any where answer to original
> question or if it has been answered I probably have been stupid enough
> not to be able to
> follow it.

Bond,

Here's a trivial userspace example.

What is the official userspace method for determining if a harddrive
is a traditional rotating disk, or a SSD?

I suspect you won't believe it, but it is just:

cat /sys/block/sda/queue/rotational.

What is the official userspace method for informing the kernel you
want to override its determination of rotating and set it to the SSD
setting?

echo 0 > /sys/block/sda/queue/rotational

Obviously you can code the userspace app for the above in any language you want.

The big thing is that the above is a simple userspace example of
userspace interfacing with the kernel via a formal abi.  Note I say
ABI not API.  ioctl changes in different architectures, so while it
can make a fine API, it is not a very good ABI.  That lack of
consistency in its ABI is one of the reasons it is discouraged.

sysfs is now the preferred solution for most basic userspace / kernel
interaction due to its simplicity and consistent ABI regardless of
platform / architecture.  You can see how almost trivially easy the
userspace side of the interface is.  You can also see that it is
exactly the same for a 32-bit app and for a 64-bit app.

You as a future kernel developer need to know how to write the kernel
side of the above.

As you do that, you will see that sysfs is designed for passing single
parameters back and forth.  If you have a need to pass multiple
parameters in a single atomic block, the sysfs is not the right
choice.  netlink sockets would be the most common recommended
interface for sending a collection of parameters at one time.  ie.
ioctl does the same by passing a structure pointer, but as I said
before ioctl is now discouraged.

Greg

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


Re: interview question how does application connects to device

2011-07-17 Thread Anuz Pratap Singh Tomar
On Sun, Jul 17, 2011 at 6:34 PM, Bond  wrote:

> On Sun, Jul 17, 2011 at 9:36 PM, Mulyadi Santosa
>  wrote:
> > On Sun, Jul 17, 2011 at 22:52, Bond  wrote:
> >> Let me know what do you understand from this.
> >
> >
> > And Greg already kindly answer that for you too. Didn't you see his
> > answer? And why do you rant here anyway? Simply getting an answer
> > here, you already lucky and you should be thankful.
> >
> > --
> Let me know which part of answer answered as how application connects
> to particular driver.I see answer explaining finer details of device
> driver mehcanism but I did not see any where answer to original
> question or if it has been answered I probably have been stupid enough
> not to be able to
> follow it.
>
>
There have been a lot of discussion on udev and VFS and someone even
explained path of data flow from user space to kernel to end device.
you need to read more and read carefully. Besides your question is more
related to linux application programming and interface. Robert love's other
book(Linux system programming) should help you, there is one more book
Advanced linux programming, new riders publication.

P.S. And I really don't like tone of your mails.
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


Re: interview question how does application connects to device

2011-07-17 Thread Bond
On Sun, Jul 17, 2011 at 9:36 PM, Mulyadi Santosa
 wrote:
> On Sun, Jul 17, 2011 at 22:52, Bond  wrote:
>> Let me know what do you understand from this.
>
>
> And Greg already kindly answer that for you too. Didn't you see his
> answer? And why do you rant here anyway? Simply getting an answer
> here, you already lucky and you should be thankful.
>
> --
Let me know which part of answer answered as how application connects
to particular driver.I see answer explaining finer details of device
driver mehcanism but I did not see any where answer to original
question or if it has been answered I probably have been stupid enough
not to be able to
follow it.

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


Re: interview question how does application connects to device

2011-07-17 Thread Bond
On Sun, Jul 17, 2011 at 9:44 PM, Anuz Pratap Singh Tomar
 wrote:
>
>
> On Sun, Jul 17, 2011 at 4:52 PM, Bond  wrote:
>>
>> On Sun, Jul 17, 2011 at 9:17 PM, Anuz Pratap Singh Tomar
>>  wrote:
>> >
>> >
>> > On Sun, Jul 17, 2011 at 4:40 PM, Bond  wrote:
>> >>
>> >> On Sun, Jul 17, 2011 at 9:04 PM, Anuz Pratap Singh Tomar
>> >>  wrote:
>> >> >
>> >> >
>> >> > On Sun, Jul 17, 2011 at 4:10 PM, Bond 
>> >> > wrote:
>> >> >>
>> >> >> On Tue, Jul 5, 2011 at 11:13 AM, Prashant Shah
>> >> >> 
>> >> >> wrote:
>> >> >> > Hi,
>> >> >> >
>> >> >> > On Tue, Jul 5, 2011 at 9:45 AM, Bond 
>> >> >> > wrote:
>> >> >> >> This is an interview question.
>> >> >> >> My answer was
>> >> >> >> In unix it simply opens the device node as a file and
>> >> >> >> sends/receives
>> >> >> >> data and commands from it.
>> >> >> >>
>> >> >> >
>> >> >> > A little more detailed method :
>> >> >> >
>> >> >> > Userland read/write to the file -> Calls C Library read/write
>> >> >> > functions -> Makes System Calls for read/write -> (now inside
>> >> >> > kernel)
>> >> >> > -> Process the system calls (check parameter, etc) -> Refer the
>> >> >> > file_operations structure for that file -> Call the corresponding
>> >> >> > read/write function.
>> >> >> >
>> >> >>
>> >> >> This is not correct.If you answer this in interview which I faced as
>> >> >> I
>> >> >> did not get that job even you will not.
>> >> >> The answers on this mailing list did not helped.If you would have
>> >> >> been
>> >> >> in the interview and given these answers it will not work.
>> >> >> Initially I posted the question on list I was expecting I missed
>> >> >> some
>> >> >> thing or interviewer was blabbering more.But I gave 2-3 more
>> >> >> interviews
>> >> >> and all of them asked me same and I gave the answers which I learned
>> >> >> in this thread but I was not selected.
>> >> >>
>> >> >> --
>> >> >
>> >> >
>> >> > This list is not an interview question answering mailing list.
>> >> > Not getting selected have nothing to do with answers being right or
>> >> > wrong.
>> >> > Being selected in an interview has a lot of other factors.
>> >> >
>> >> >
>> >> Why do not you understand that this has nothing to my selection what I
>> >> wanted to know is how does the app gets connected to device.And your
>> >> rant does not help to understand.The answers given on this list are of
>> >> very poor quality as usual.
>> >> As an example you rather than answering some thing meaningful
>> >> reproduced
>> >> rant.
>> >
>> > Greg Freemyer answered your question with fine details. And the
>> > discussion
>> > that followed elaborated the point.
>> > But you say all that is NOT correct? on what basis did you say that?
>>
>> I am reproducing what he answered
>>
>> And the interviewer was right! You fell short.  And so did everyone
>> else in this thread.  I'm very surprised at the poor answers this
>> thread generated.  Maybe everyone should get a 20+ year old UNIX book
>> an read it so they know the basic and classic mechanisms.
>>
>> My personal favorite old book was
>>
>>  "The Magic Garden Explained: The Internals of Unix System V Release 4"
>>
>> To my surprise Amazon has some copies.  New and used.  It's 20 years
>> old, but it will give some historical pre-linux context.  Remember
>> your interviewer is likely to be an old timer, so you need to be
>> familiar with classical UNIX, not just bleeding edge Linux.   (Not
>> that the answers showed familiarity with either, but the classic stuff
>> should pop of people's minds without thought.)
>>
>> Back to the question
>>
>> read / write are "data" paths, not control/status/command paths. Yes,
>> there are drivers that abuse read/write to handle commands, but they
>> are the exception, not the rule.
>>
>> In general, read/write are termed in-band communications and using
>> them to communicate with ta driver is discouraged.  The Linux kernel
>> encourages out-of-band communications.
>>
>> Let me simplify the question.
>>
>> 1) What are the FIVE classic system calls for interfacing with a
>> character device.  (ie. If it did not exist in 1970, don't list it).
>>
>> 2) Which of the 5 is still heavily used in the kernel but is
>> discouraged for new drivers being accepted into the linux kernel?
>>
>> 3) Name at least 3 alternatives that have been routinely used for
>> out-of-band communication in the Linux kernel since 2000.
>>
>> Personally, anyone that can't answer those basic questions has failed
>> a job interview in my mind.
>>
>>
>> Let me know what do you understand from this.
>>
>> --
>
>
> For one he is pointing out that there are more mechanism to interact with
> devices than just read/write.
> When you open a device node, you do not have to necessarily read or write.
> In most cases its not ever required
> The drivers implement many methods like proc, ioctls, the new sysfs each of
> which can be directly read from or write to or pass some control/command.
> For example network drivers don't have device nodes, netlink interf

Re: interview question how does application connects to device

2011-07-17 Thread Anuz Pratap Singh Tomar
On Sun, Jul 17, 2011 at 4:52 PM, Bond  wrote:

> On Sun, Jul 17, 2011 at 9:17 PM, Anuz Pratap Singh Tomar
>  wrote:
> >
> >
> > On Sun, Jul 17, 2011 at 4:40 PM, Bond  wrote:
> >>
> >> On Sun, Jul 17, 2011 at 9:04 PM, Anuz Pratap Singh Tomar
> >>  wrote:
> >> >
> >> >
> >> > On Sun, Jul 17, 2011 at 4:10 PM, Bond 
> wrote:
> >> >>
> >> >> On Tue, Jul 5, 2011 at 11:13 AM, Prashant Shah <
> pshah.mum...@gmail.com>
> >> >> wrote:
> >> >> > Hi,
> >> >> >
> >> >> > On Tue, Jul 5, 2011 at 9:45 AM, Bond 
> >> >> > wrote:
> >> >> >> This is an interview question.
> >> >> >> My answer was
> >> >> >> In unix it simply opens the device node as a file and
> sends/receives
> >> >> >> data and commands from it.
> >> >> >>
> >> >> >
> >> >> > A little more detailed method :
> >> >> >
> >> >> > Userland read/write to the file -> Calls C Library read/write
> >> >> > functions -> Makes System Calls for read/write -> (now inside
> kernel)
> >> >> > -> Process the system calls (check parameter, etc) -> Refer the
> >> >> > file_operations structure for that file -> Call the corresponding
> >> >> > read/write function.
> >> >> >
> >> >>
> >> >> This is not correct.If you answer this in interview which I faced as
> I
> >> >> did not get that job even you will not.
> >> >> The answers on this mailing list did not helped.If you would have
> been
> >> >> in the interview and given these answers it will not work.
> >> >> Initially I posted the question on list I was expecting I missed some
> >> >> thing or interviewer was blabbering more.But I gave 2-3 more
> >> >> interviews
> >> >> and all of them asked me same and I gave the answers which I learned
> >> >> in this thread but I was not selected.
> >> >>
> >> >> --
> >> >
> >> >
> >> > This list is not an interview question answering mailing list.
> >> > Not getting selected have nothing to do with answers being right or
> >> > wrong.
> >> > Being selected in an interview has a lot of other factors.
> >> >
> >> >
> >> Why do not you understand that this has nothing to my selection what I
> >> wanted to know is how does the app gets connected to device.And your
> >> rant does not help to understand.The answers given on this list are of
> >> very poor quality as usual.
> >> As an example you rather than answering some thing meaningful reproduced
> >> rant.
> >
> > Greg Freemyer answered your question with fine details. And the
> discussion
> > that followed elaborated the point.
> > But you say all that is NOT correct? on what basis did you say that?
>
> I am reproducing what he answered
>
> And the interviewer was right! You fell short.  And so did everyone
> else in this thread.  I'm very surprised at the poor answers this
> thread generated.  Maybe everyone should get a 20+ year old UNIX book
> an read it so they know the basic and classic mechanisms.
>
> My personal favorite old book was
>
>  "The Magic Garden Explained: The Internals of Unix System V Release 4"
>
> To my surprise Amazon has some copies.  New and used.  It's 20 years
> old, but it will give some historical pre-linux context.  Remember
> your interviewer is likely to be an old timer, so you need to be
> familiar with classical UNIX, not just bleeding edge Linux.   (Not
> that the answers showed familiarity with either, but the classic stuff
> should pop of people's minds without thought.)
>
> Back to the question
>
> read / write are "data" paths, not control/status/command paths. Yes,
> there are drivers that abuse read/write to handle commands, but they
> are the exception, not the rule.
>
> In general, read/write are termed in-band communications and using
> them to communicate with ta driver is discouraged.  The Linux kernel
> encourages out-of-band communications.
>
> Let me simplify the question.
>
> 1) What are the FIVE classic system calls for interfacing with a
> character device.  (ie. If it did not exist in 1970, don't list it).
>
> 2) Which of the 5 is still heavily used in the kernel but is
> discouraged for new drivers being accepted into the linux kernel?
>
> 3) Name at least 3 alternatives that have been routinely used for
> out-of-band communication in the Linux kernel since 2000.
>
> Personally, anyone that can't answer those basic questions has failed
> a job interview in my mind.
>
>
> Let me know what do you understand from this.
>
> --
>


For one he is pointing out that there are more mechanism to interact with
devices than just read/write.
When you open a device node, you do not have to necessarily read or write.
In most cases its not ever required
The drivers implement many methods like proc, ioctls, the new sysfs each of
which can be directly read from or write to or pass some control/command.
For example network drivers don't have device nodes, netlink interface or
sockets is used to interact with them.
Secondly he is pointing out the fact that some of the interfaces are being
deprecated like sysfs will be used for most purpose as compared to proc.
In between this discussion, it was also p

Re: interview question how does application connects to device

2011-07-17 Thread Mulyadi Santosa
On Sun, Jul 17, 2011 at 22:52, Bond  wrote:
> Let me know what do you understand from this.


And Greg already kindly answer that for you too. Didn't you see his
answer? And why do you rant here anyway? Simply getting an answer
here, you already lucky and you should be thankful.

-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


Re: interview question how does application connects to device

2011-07-17 Thread Bond
On Sun, Jul 17, 2011 at 9:17 PM, Anuz Pratap Singh Tomar
 wrote:
>
>
> On Sun, Jul 17, 2011 at 4:40 PM, Bond  wrote:
>>
>> On Sun, Jul 17, 2011 at 9:04 PM, Anuz Pratap Singh Tomar
>>  wrote:
>> >
>> >
>> > On Sun, Jul 17, 2011 at 4:10 PM, Bond  wrote:
>> >>
>> >> On Tue, Jul 5, 2011 at 11:13 AM, Prashant Shah 
>> >> wrote:
>> >> > Hi,
>> >> >
>> >> > On Tue, Jul 5, 2011 at 9:45 AM, Bond 
>> >> > wrote:
>> >> >> This is an interview question.
>> >> >> My answer was
>> >> >> In unix it simply opens the device node as a file and sends/receives
>> >> >> data and commands from it.
>> >> >>
>> >> >
>> >> > A little more detailed method :
>> >> >
>> >> > Userland read/write to the file -> Calls C Library read/write
>> >> > functions -> Makes System Calls for read/write -> (now inside kernel)
>> >> > -> Process the system calls (check parameter, etc) -> Refer the
>> >> > file_operations structure for that file -> Call the corresponding
>> >> > read/write function.
>> >> >
>> >>
>> >> This is not correct.If you answer this in interview which I faced as I
>> >> did not get that job even you will not.
>> >> The answers on this mailing list did not helped.If you would have been
>> >> in the interview and given these answers it will not work.
>> >> Initially I posted the question on list I was expecting I missed some
>> >> thing or interviewer was blabbering more.But I gave 2-3 more
>> >> interviews
>> >> and all of them asked me same and I gave the answers which I learned
>> >> in this thread but I was not selected.
>> >>
>> >> --
>> >
>> >
>> > This list is not an interview question answering mailing list.
>> > Not getting selected have nothing to do with answers being right or
>> > wrong.
>> > Being selected in an interview has a lot of other factors.
>> >
>> >
>> Why do not you understand that this has nothing to my selection what I
>> wanted to know is how does the app gets connected to device.And your
>> rant does not help to understand.The answers given on this list are of
>> very poor quality as usual.
>> As an example you rather than answering some thing meaningful reproduced
>> rant.
>
> Greg Freemyer answered your question with fine details. And the discussion
> that followed elaborated the point.
> But you say all that is NOT correct? on what basis did you say that?

I am reproducing what he answered

And the interviewer was right! You fell short.  And so did everyone
else in this thread.  I'm very surprised at the poor answers this
thread generated.  Maybe everyone should get a 20+ year old UNIX book
an read it so they know the basic and classic mechanisms.

My personal favorite old book was

 "The Magic Garden Explained: The Internals of Unix System V Release 4"

To my surprise Amazon has some copies.  New and used.  It's 20 years
old, but it will give some historical pre-linux context.  Remember
your interviewer is likely to be an old timer, so you need to be
familiar with classical UNIX, not just bleeding edge Linux.   (Not
that the answers showed familiarity with either, but the classic stuff
should pop of people's minds without thought.)

Back to the question

read / write are "data" paths, not control/status/command paths. Yes,
there are drivers that abuse read/write to handle commands, but they
are the exception, not the rule.

In general, read/write are termed in-band communications and using
them to communicate with ta driver is discouraged.  The Linux kernel
encourages out-of-band communications.

Let me simplify the question.

1) What are the FIVE classic system calls for interfacing with a
character device.  (ie. If it did not exist in 1970, don't list it).

2) Which of the 5 is still heavily used in the kernel but is
discouraged for new drivers being accepted into the linux kernel?

3) Name at least 3 alternatives that have been routinely used for
out-of-band communication in the Linux kernel since 2000.

Personally, anyone that can't answer those basic questions has failed
a job interview in my mind.


Let me know what do you understand from this.

--

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


Re: interview question how does application connects to device

2011-07-17 Thread Anuz Pratap Singh Tomar
On Sun, Jul 17, 2011 at 4:40 PM, Bond  wrote:

> On Sun, Jul 17, 2011 at 9:04 PM, Anuz Pratap Singh Tomar
>  wrote:
> >
> >
> > On Sun, Jul 17, 2011 at 4:10 PM, Bond  wrote:
> >>
> >> On Tue, Jul 5, 2011 at 11:13 AM, Prashant Shah 
> >> wrote:
> >> > Hi,
> >> >
> >> > On Tue, Jul 5, 2011 at 9:45 AM, Bond 
> wrote:
> >> >> This is an interview question.
> >> >> My answer was
> >> >> In unix it simply opens the device node as a file and sends/receives
> >> >> data and commands from it.
> >> >>
> >> >
> >> > A little more detailed method :
> >> >
> >> > Userland read/write to the file -> Calls C Library read/write
> >> > functions -> Makes System Calls for read/write -> (now inside kernel)
> >> > -> Process the system calls (check parameter, etc) -> Refer the
> >> > file_operations structure for that file -> Call the corresponding
> >> > read/write function.
> >> >
> >>
> >> This is not correct.If you answer this in interview which I faced as I
> >> did not get that job even you will not.
> >> The answers on this mailing list did not helped.If you would have been
> >> in the interview and given these answers it will not work.
> >> Initially I posted the question on list I was expecting I missed some
> >> thing or interviewer was blabbering more.But I gave 2-3 more
> >> interviews
> >> and all of them asked me same and I gave the answers which I learned
> >> in this thread but I was not selected.
> >>
> >> --
> >
> >
> > This list is not an interview question answering mailing list.
> > Not getting selected have nothing to do with answers being right or
> wrong.
> > Being selected in an interview has a lot of other factors.
> >
> >
> Why do not you understand that this has nothing to my selection what I
> wanted to know is how does the app gets connected to device.And your
> rant does not help to understand.The answers given on this list are of
> very poor quality as usual.
> As an example you rather than answering some thing meaningful reproduced
> rant.
>

Greg Freemyer answered your question with fine details. And the discussion
that followed elaborated the point.
But you say all that is NOT correct? on what basis did you say that?
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


Re: interview question how does application connects to device

2011-07-17 Thread Bond
On Sun, Jul 17, 2011 at 9:04 PM, Anuz Pratap Singh Tomar
 wrote:
>
>
> On Sun, Jul 17, 2011 at 4:10 PM, Bond  wrote:
>>
>> On Tue, Jul 5, 2011 at 11:13 AM, Prashant Shah 
>> wrote:
>> > Hi,
>> >
>> > On Tue, Jul 5, 2011 at 9:45 AM, Bond  wrote:
>> >> This is an interview question.
>> >> My answer was
>> >> In unix it simply opens the device node as a file and sends/receives
>> >> data and commands from it.
>> >>
>> >
>> > A little more detailed method :
>> >
>> > Userland read/write to the file -> Calls C Library read/write
>> > functions -> Makes System Calls for read/write -> (now inside kernel)
>> > -> Process the system calls (check parameter, etc) -> Refer the
>> > file_operations structure for that file -> Call the corresponding
>> > read/write function.
>> >
>>
>> This is not correct.If you answer this in interview which I faced as I
>> did not get that job even you will not.
>> The answers on this mailing list did not helped.If you would have been
>> in the interview and given these answers it will not work.
>> Initially I posted the question on list I was expecting I missed some
>> thing or interviewer was blabbering more.But I gave 2-3 more
>> interviews
>> and all of them asked me same and I gave the answers which I learned
>> in this thread but I was not selected.
>>
>> --
>
>
> This list is not an interview question answering mailing list.
> Not getting selected have nothing to do with answers being right or wrong.
> Being selected in an interview has a lot of other factors.
>
>
Why do not you understand that this has nothing to my selection what I
wanted to know is how does the app gets connected to device.And your
rant does not help to understand.The answers given on this list are of
very poor quality as usual.
As an example you rather than answering some thing meaningful reproduced rant.

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


Re: interview question how does application connects to device

2011-07-17 Thread Anuz Pratap Singh Tomar
On Sun, Jul 17, 2011 at 4:10 PM, Bond  wrote:

> On Tue, Jul 5, 2011 at 11:13 AM, Prashant Shah 
> wrote:
> > Hi,
> >
> > On Tue, Jul 5, 2011 at 9:45 AM, Bond  wrote:
> >> This is an interview question.
> >> My answer was
> >> In unix it simply opens the device node as a file and sends/receives
> >> data and commands from it.
> >>
> >
> > A little more detailed method :
> >
> > Userland read/write to the file -> Calls C Library read/write
> > functions -> Makes System Calls for read/write -> (now inside kernel)
> > -> Process the system calls (check parameter, etc) -> Refer the
> > file_operations structure for that file -> Call the corresponding
> > read/write function.
> >
>
> This is not correct.If you answer this in interview which I faced as I
> did not get that job even you will not.
> The answers on this mailing list did not helped.If you would have been
> in the interview and given these answers it will not work.
> Initially I posted the question on list I was expecting I missed some
> thing or interviewer was blabbering more.But I gave 2-3 more
> interviews
> and all of them asked me same and I gave the answers which I learned
> in this thread but I was not selected.
>
> --
>


This list is not an interview question answering mailing list.
Not getting selected have nothing to do with answers being right or wrong.
Being selected in an interview has a lot of other factors.



> ___
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


Re: interview question how does application connects to device

2011-07-17 Thread Bond
On Tue, Jul 5, 2011 at 11:13 AM, Prashant Shah  wrote:
> Hi,
>
> On Tue, Jul 5, 2011 at 9:45 AM, Bond  wrote:
>> This is an interview question.
>> My answer was
>> In unix it simply opens the device node as a file and sends/receives
>> data and commands from it.
>>
>
> A little more detailed method :
>
> Userland read/write to the file -> Calls C Library read/write
> functions -> Makes System Calls for read/write -> (now inside kernel)
> -> Process the system calls (check parameter, etc) -> Refer the
> file_operations structure for that file -> Call the corresponding
> read/write function.
>

This is not correct.If you answer this in interview which I faced as I
did not get that job even you will not.
The answers on this mailing list did not helped.If you would have been
in the interview and given these answers it will not work.
Initially I posted the question on list I was expecting I missed some
thing or interviewer was blabbering more.But I gave 2-3 more
interviews
and all of them asked me same and I gave the answers which I learned
in this thread but I was not selected.

--

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


Re: why backtiks for a word?

2011-07-17 Thread zeal
On Sun, Jul 17, 2011 at 7:50 PM, Robert P. J. Day  wrote:
> On Sun, 17 Jul 2011, zeal wrote:
>
>> On Sun, Jul 17, 2011 at 6:29 PM, Mulyadi Santosa
>>  wrote:
>> > On Sun, Jul 17, 2011 at 07:49, zeal  wrote:
>> >> Hi list,
>> >>
>> >> We often see that `a word what you like'. But i get confused on it.
>> >> Why is it `word' but not 'word' or what else?
>> >
>> > in which context do you ask above? bash? C? else? or something
>> > unrelated to programming?
>>
>> Hmm, not in bash. In some documents, or comments in the source code.
>> eg. I love `linux'. A reverse quotation (`) and a quotation (').
>
>  there's not much point speculating on what the original poster meant
> until he clarifies it.  the connection to the linux kernel here is
> still entirely unclear.
>

Maybe it's related to unix / linux world.  Sorry for the noise.


-- 
Cheers

- zeal

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


Re: why backtiks for a word?

2011-07-17 Thread Robert P. J. Day
On Sun, 17 Jul 2011, zeal wrote:

> On Sun, Jul 17, 2011 at 6:29 PM, Mulyadi Santosa
>  wrote:
> > On Sun, Jul 17, 2011 at 07:49, zeal  wrote:
> >> Hi list,
> >>
> >> We often see that `a word what you like'. But i get confused on it.
> >> Why is it `word' but not 'word' or what else?
> >
> > in which context do you ask above? bash? C? else? or something
> > unrelated to programming?
>
> Hmm, not in bash. In some documents, or comments in the source code.
> eg. I love `linux'. A reverse quotation (`) and a quotation (').

  there's not much point speculating on what the original poster meant
until he clarifies it.  the connection to the linux kernel here is
still entirely unclear.

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday


___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


Re: why backtiks for a word?

2011-07-17 Thread zeal
On Sun, Jul 17, 2011 at 6:29 PM, Mulyadi Santosa
 wrote:
> On Sun, Jul 17, 2011 at 07:49, zeal  wrote:
>> Hi list,
>>
>> We often see that `a word what you like'. But i get confused on it.
>> Why is it `word' but not 'word' or what else?
>
> in which context do you ask above? bash? C? else? or something
> unrelated to programming?
>

Hmm, not in bash. In some documents, or comments in the source code.
eg. I love `linux'. A reverse quotation (`) and a quotation (').


-- 
Cheers

- zeal

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


Re: why backtiks for a word?

2011-07-17 Thread Mulyadi Santosa
On Sun, Jul 17, 2011 at 07:49, zeal  wrote:
> Hi list,
>
> We often see that `a word what you like'. But i get confused on it.
> Why is it `word' but not 'word' or what else?

in which context do you ask above? bash? C? else? or something
unrelated to programming?

-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies