I am not able to understand how the marked like skips the node n :
static inline void __hlist_del(struct hlist_node *n)
{
struct hlist_node *next = n-next;
struct hlist_node **pprev = n-pprev;
*pprev = next; ---
if (next)
Could anyone explain the significance of the BH_Boundary flag in a
buffer head. and when you should this flag be set or cleared?
What other effects does setting or clearing this flag have?
Thanks,
Joel
--
To unsubscribe from this list: send an email with
unsubscribe kernelnewbies to
Set if the block to be submitted after this one will not be adjacent to this
one.
On Thu, Apr 8, 2010 at 11:34 AM, Joel Fernandes agnel.j...@gmail.comwrote:
Could anyone explain the significance of the BH_Boundary flag in a
buffer head. and when you should this flag be set or cleared?
What
On Thu, Apr 8, 2010 at 11:34 AM, Joel Fernandes agnel.j...@gmail.com
wrote:
Could anyone explain the significance of the BH_Boundary flag in a
buffer head. and when you should this flag be set or cleared?
What other effects does setting or clearing this flag have?
Set if the block to be
On Thu, Apr 8, 2010 at 11:28 AM, Onkar Mahajan kern.de...@gmail.com wrote:
I am not able to understand how the marked like skips the node n :
static inline void __hlist_del(struct hlist_node *n)
{
struct hlist_node *next = n-next;
struct hlist_node **pprev = n-pprev;
*pprev =
Because the field pprev holds the address of the next field in the
previous node.
And *pprev = next; just like the prev-next = next; connect the two nodes
in forward direction.
Hope it's helpful for you.
On Thu, Apr 8, 2010 at 1:58 PM, Onkar Mahajan kern.de...@gmail.com wrote:
I am not able
2010/4/8 Onkar Mahajan kern.de...@gmail.com:
What is LIST_POISON1 and LIST_POISON2 ??
#define LIST_POISON1 ((void *) 0x00100100 + POISON_POINTER_DELTA)
#define LIST_POISON2 ((void *) 0x00200200 + POISON_POINTER_DELTA)
and why they are used ?
Regards,
Onkar
Hi Onkar,
A poison value
2010/4/8 Cédric Augonnet cedric.augon...@gmail.com:
2010/4/8 Onkar Mahajan kern.de...@gmail.com:
What is LIST_POISON1 and LIST_POISON2 ??
#define LIST_POISON1 ((void *) 0x00100100 + POISON_POINTER_DELTA)
#define LIST_POISON2 ((void *) 0x00200200 + POISON_POINTER_DELTA)
and why they are
Hi guys,
I am wondering how are you rebasing against linux-next each day, given the
fact that the code is so rapidly changing.
Is there any guide on how we should do this? I only know about this one (
http://lwn.net/Articles/289245/ ) which I am not sure it's still up to date
with the latest
On Thu, Apr 8, 2010 at 6:34 PM, vorad vorad.1...@gmail.com wrote:
Hi guys,
I am wondering how are you rebasing against linux-next each day, given the
fact that the code is so rapidly changing.
Is there any guide on how we should do this? I only know about this one
Elvis Y. Tamayo Moyares etmoya...@grm.uci.cu writes:
It's true. I managed to hook into the kernel 2.4 and 2.6 using LKM but
how can do it in 2.6.30 or higher, not let me change the syscall
table references ...
when I add the LKM to stdout I get 'Killed'.
and when I try to remove the LKM
On Thu, Apr 8, 2010 at 9:04 AM, vorad vorad.1...@gmail.com wrote:
Hi guys,
I am wondering how are you rebasing against linux-next each day, given the
fact that the code is so rapidly changing.
Is there any guide on how we should do this? I only know about this one
On Thu, Apr 8, 2010 at 7:53 AM, Nobin Mathew nobin.mat...@gmail.com wrote:
On Wed, Apr 7, 2010 at 10:44 PM, H. Peter Anvin h...@zytor.com wrote:
On 04/07/2010 09:48 AM, Himanshu Aggarwal wrote:
I think for some architectures, the position of highmem is constrained
by hardware as well. It
I have read that mmap/mmap2 system calls are more efficient than a read and
a write system call. I am unable to understand why is this so?
mmap/mmap2 always create a vm_area_struct which is inserted into the
process's userspace region. Given that this is the case, how is mmap/mmap2
more efficient
I wish we could use mmap in kernel space but I think its hard to implement
this, all kernel memory is directly and permanently mapped and not
swappable. You can vmalloc in kernel but you cannot mmap..
Sorry I went wrong there, what I meant was you cannot have a page fault
trigger on kernel
Hi Venkatram,
thanks for your wonderful explanation, I delayed asking further questions
till I read every ones posts, its much clearer now. :)
To make things clear, 896 MB is not a hardware limitation. The 3GB:1GB split
can be configured during the kernel build but the split cannot be changed
On Thu, Apr 8, 2010 at 1:29 PM, Joel Fernandes agnel.j...@gmail.com wrote:
Hi Venkatram,
thanks for your wonderful explanation, I delayed asking further questions
till I read every ones posts, its much clearer now. :)
To make things clear, 896 MB is not a hardware limitation. The 3GB:1GB
On Wed, Apr 7, 2010 at 1:49 PM, Onkar Mahajan kern.de...@gmail.com wrote:
Greg,
My intention is to learn to write a SATA driver with the hardware
that I have. I have a SATA hard drive from Western Digital (MDL :
WD800JD-75MSAS)
and SATA controller (Intel 82801 GB/GR/GH ( ICH7 family )
Thank you very much sir. That was a good advise.
I will try to do that. But , If I face difficulties is there
any mailing list wherein I can post SATA related questions.
Thanks regards,
Onkar
On Fri, Apr 9, 2010 at 8:59 AM, Peter Teoh htmldevelo...@gmail.com wrote:
On Wed, Apr 7, 2010 at 1:49
On Fri, Apr 9, 2010 at 11:54 AM, Onkar Mahajan kern.de...@gmail.com wrote:
Thank you very much sir. That was a good advise.
I will try to do that. But , If I face difficulties is there
any mailing list wherein I can post SATA related questions.
I found one link for WD:
20 matches
Mail list logo
