-Original Message-
From: Rock Lee [mailto:rocklee_...@outlook.com]
Sent: Tuesday, April 07, 2015 7:09 PM
To: Jeff Haran
Cc: kernelnewbies
Subject: Re: maybe dumb question about RCU
>
> 256 If you are going to be fetching multiple fields from the
>
> 257 RCU-protected struc
>
> 256 If you are going to be fetching multiple fields from the
>
> 257 RCU-protected structure, using the local variable is of
>
> 258 course preferred. Repeated rcu_dereference() calls look
>
> 259 ugly and incur unnecessary overhead on Alpha CPUs.”
>
> From lin
On April 7, 2015 1:05:42 PM EDT, David Legault wrote:
>Hello,
>
>Now that we have O_TMPFILE and O_BENEATH added to the openat flags,
>there
>is no space left to add more flags since the flags variable is a 32 bit
>int. How does one resolve this issue and extend this? A new syscall
>with a
>64bit
Hi all,
I've been trying to understand the usage of RCU and am struggling a bit with
one issue.
Let's say one intends to use "classic RCU" as described in whatisRCU.txt where
readers use
sequences of rcu_read_lock(), rcu_dereference(), rcu_read_unlock) and updaters
use
rcu_assign_pointer()/sync
Hello,
Now that we have O_TMPFILE and O_BENEATH added to the openat flags, there
is no space left to add more flags since the flags variable is a 32 bit
int. How does one resolve this issue and extend this? A new syscall with a
64bit wide flags support?
http://www.spinics.net/lists/fstests/msg010
Hi Mark,
[add some possible interested developer in CC]
> Mark Rutland hat am 7. April 2015 um 13:29 geschrieben:
>
>
> On Sat, Apr 04, 2015 at 10:40:13PM +0100, Stefan Wahren wrote:
> > Hi,
>
> Hi,
>
> > i'm currently working on drivers (regulator and power switch) for a power
> > subsystem of
So I found the issue (it was a PIBKAC issue :/)
I was using sudo to try and build the kernel (this was due to a messed
up setup where the whole kernel src tree ended up being written by
root). When copy-pasting my command here, I missed copying the sudo
part and that was precisely the reason for t
On Mon, Apr 6, 2015 at 11:50 PM, Mandeep Sandhu
wrote:
> Hi All,
>
> I'm having trouble compiling my kernel using a 32-bit toolchain (for
> ARM) on a 64-bit host (Ubuntu 14.10). The kernel version is 3.14.17.
>
> I understand that 32-bit binaries require "ia32-libs" (or equivalent)
> for compiling
> Edit .config and set CONFIG_CROSS_COMPILE to the path where your cross
> compiler is located.
This doesn't help either! :/ I'll start afresh. Maybe my setup got
messed-up somehow.
Thanks anyway!
___
Kernelnewbies mailing list
Kernelnewbies@kernelnew
On Mon, Apr 6, 2015 at 5:27 PM, John de la Garza wrote:
> On Mon, Apr 06, 2015 at 03:50:41PM -0700, Mandeep Sandhu wrote:
>>
>> I'm having trouble compiling my kernel using a 32-bit toolchain (for
>> ARM) on a 64-bit host (Ubuntu 14.10). The kernel version is 3.14.17.
>>
>> Any hints on how to get
On Mon, 06 Apr 2015 23:12:34 -0400, nick said:
(Replying mostly for the edification of those who can learn learn without
having to be spoon-fed)
> After reading through the code for the usb and vfs core infrastructure, I was
> wondering if
> after reading it if I am correct in my notion of there
Malte Vesper wrote:
>
> On 07/04/15 05:06, Anupam Kapoor wrote:
>>> [2015-04-07T00:08:10+0530]: "Mike Thompson" (mike-thompson):
>> ,[ mike-thompson ]
>> | As others mention, using the Linux kernel to come up to speed with C is the
>> | wrong approach. If you have a strong desire to learn
On 07/04/15 05:06, Anupam Kapoor wrote:
>> [2015-04-07T00:08:10+0530]: "Mike Thompson" (mike-thompson):
> ,[ mike-thompson ]
> | As others mention, using the Linux kernel to come up to speed with C is the
> | wrong approach. If you have a strong desire to learn kernel programming
> | con
Hi, guys:
I am reading function scull_init_module() in scull driver.I found that
scull_init_module() doesn't check scull_setup_cdev()'s return value.If
there will be a probem when scull_setup_cdev() failed, and then, others
call scull_cleanup_module()?
for (i = 0; i < scull_nr_devs; i+
14 matches
Mail list logo
