wait and waitpid would not work because a Process A would wait for process
B(which is a parent of the daemon), process B immediately exits and process
A would be notified.
In my case, I want to query the status of process C(which is child of
process B) / grandchild of process A which is a child of
On Wed, Jan 7, 2015 at 12:57 AM, Nizam Haider nizamhaider...@gmail.com wrote:
Anuz Pratap Singh Tomar chambilkethakur at gmail.com writes:
On Tue, Jan 6, 2015 at 3:22 PM, Yash Jain yash2learn at gmail.com
wrote:Hello All,I have one dumb question,
I wanted to write a process which monitors
hi all:
The job of pskb_may_pull is to make sure that the area pointed to by
skb-data contains a block of
data at least as big as the IP header, since each IP packet (fragments
included) must include a complete IP
header.When we receive a packet , the kernel will call the pkb_may_pull(),
it
Hello all,
There is following definition at arch/x86/realmode/rm/Makefile:
KBUILD_CFLAGS:= $(LINUXINCLUDE) $(REALMODE_CFLAGS) -D_SETUP -D_WAKEUP \
-I$(srctree)/arch/x86/boot
Is it used now? I'm asking because _WAKEUP definition everywhere
undefined in the code.
Thank you.
On Sun, Jan 04, 2015 at 04:50:58PM -0800, Greg KH wrote:
On Sun, Jan 04, 2015 at 06:43:22PM -0500, John de la Garza wrote:
I assume it is a bad idea to depend on true being 1, right? I mean, I
should assume that true could be changed to any non 0 value in the
future,
right?
Why would
On Sun, Jan 04, 2015 at 08:17:15PM -0500, valdis.kletni...@vt.edu wrote:
On Sun, 04 Jan 2015 18:43:22 -0500, John de la Garza said:
On Sat, Jan 03, 2015 at 11:20:29PM -0500, valdis.kletni...@vt.edu wrote:
On Sat, 03 Jan 2015 18:54:00 -0500, John de la Garza said:
It should not be
hi Alberto:
I'm confused with paging skbs is a technique meant to ease the
work
of drivers.A driver might choose to page too much data., please give
more explain.
Thank you.
2015-01-07 23:35 GMT+08:00 Alberto Leiva ydah...@gmail.com:
I think in theory whatever random driver for
On Wed, Jan 07, 2015 at 08:46:52PM -0800, John de la Garza wrote:
On Sun, Jan 04, 2015 at 04:50:58PM -0800, Greg KH wrote:
On Sun, Jan 04, 2015 at 06:43:22PM -0500, John de la Garza wrote:
I assume it is a bad idea to depend on true being 1, right? I mean, I
should assume that true could
On Mit, 2015-01-07 at 14:40 +0530, Yash Jain wrote:
wait and waitpid would not work because a Process A would wait for process
B(which is a parent of the daemon), process B immediately exits and process
A would be notified.
In my case, I want to query the status of process C(which is child of
On Wed, 2015-01-07 at 20:12 +0600, Alexander Kuleshov wrote:
There is following definition at arch/x86/realmode/rm/Makefile:
KBUILD_CFLAGS:= $(LINUXINCLUDE) $(REALMODE_CFLAGS) -D_SETUP -D_WAKEUP \
-I$(srctree)/arch/x86/boot
Is it used now? I'm asking because _WAKEUP
On Wed, 2015-01-07 at 17:54 +0100, Paul Bolle wrote:
On Wed, 2015-01-07 at 20:12 +0600, Alexander Kuleshov wrote:
There is following definition at arch/x86/realmode/rm/Makefile:
KBUILD_CFLAGS:= $(LINUXINCLUDE) $(REALMODE_CFLAGS) -D_SETUP -D_WAKEUP \
On Wed, 2015-01-07 at 23:59 +0600, Alexander Kuleshov wrote:
Yes i saw video-*.c files, but i can't understand how compilation of
these video-*.c files depends on _WAKEUP macro...
For example if'd remove -D_WAKEUP, i get errors during realmode.elf linking:
arch/x86/realmode/rm/video-vga.o:
On Thu, 2015-01-08 at 00:02 +0600, Alexander Kuleshov wrote:
As i understood correctly we compile wakeup-objs only if
CONFIG_ACPI_SLEEP is 'y', but than why we pass -D_WAKEUP everytime,
even CONFIG_ACPI_SLEEP is not y?
I really don't know whether wakeup-objs is compiled only for the 'y'
case.
Seems that finally i got point of this.
Thank you Paul for the help.
8 янв. 2015 г. 1:10 пользователь kuleshovm...@gmail.com написал:
8 янв. 2015 г. 0:57 пользователь Paul Bolle pebo...@tiscali.nl написал:
On Wed, 2015-01-07 at 23:59 +0600, Alexander Kuleshov wrote:
Yes i saw video-*.c
8 янв. 2015 г. 0:57 пользователь Paul Bolle pebo...@tiscali.nl написал:
On Wed, 2015-01-07 at 23:59 +0600, Alexander Kuleshov wrote:
Yes i saw video-*.c files, but i can't understand how compilation of
these video-*.c files depends on _WAKEUP macro...
For example if'd remove -D_WAKEUP, i
Hello Paul, thank you for answer.
Yes i saw video-*.c files, but i can't understand how compilation of
these video-*.c files depends on _WAKEUP macro...
For example if'd remove -D_WAKEUP, i get errors during realmode.elf linking:
arch/x86/realmode/rm/video-vga.o: In function `vga_probe':
As i understood correctly we compile wakeup-objs only if
CONFIG_ACPI_SLEEP is 'y', but than why we pass -D_WAKEUP everytime,
even CONFIG_ACPI_SLEEP is not y?
2015-01-07 23:59 GMT+06:00 Alexander Kuleshov kuleshovm...@gmail.com:
Hello Paul, thank you for answer.
Yes i saw video-*.c files, but i
I think in theory whatever random driver for whatever random hardware
might create this situation. It's not illegal. Anyone can create a
driver outside of the kernel tree, after all. In practice, of course,
this is not the case, because anyone can tell it creates a significant
amount of overhead
18 matches
Mail list logo
