That is very important for computer forensics. Esp. in saving your ass!
Ok, now back again to making that fast :-)
Best Regards
Ingo Oeser
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
and why does this
help scalability?
Many thanks and Best Regards
Ingo Oeser, puzzled a bit :-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
your ass!
Ok, now back again to making that fast :-)
Best Regards
Ingo Oeser
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
elaborate, why this is needed and put more info about
this requirement into this patch description?
People worked hard to push data allocation from stack to heap to make
THREAD_ORDER of 0 and 1 possible. So why increase it again and why does this
help scalability?
Many thanks and Best Regards
Ingo
of it. The only thing really missing for me
is LVM support. Debian (?) did a evil hack to make it work.
Maybe one day this itches soo much, I'll even scratch it :-)
Then I'll be able to test kernels on a standard LVM installation again.
So please keep up the good work!
Best Regards
Ingo Oeser
to make it work.
Maybe one day this itches soo much, I'll even scratch it :-)
Then I'll be able to test kernels on a standard LVM installation again.
So please keep up the good work!
Best Regards
Ingo Oeser
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
uot;soft" panic better, where you still can operate the
kernel debugging features, but just have no user space supporting it.
One better hopes, that keyboards never need external firmware to be loaded
at this stage :-)
Best Regards
Ingo Oeser, who just hit the same problem yesterday...
--
To u
better hopes, that keyboards never need external firmware to be loaded
at this stage :-)
Best Regards
Ingo Oeser, who just hit the same problem yesterday...
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
Hi Bernd,
CC'ed hpa, since I'm sure he can give useful advise on that :-)
On Sunday 06 January 2008, Bernd Schubert wrote:
> On Sunday 06 January 2008, Ingo Oeser wrote:
> > Hi Bernd,
> >
> > On Sunday 06 January 2008, you wrote:
> > > Index: zd12
msleep(60 * 1000);
ssleep(60);
> panic("VFS: Unable to mount root fs on %s", b);
> }
Better would be for this and similiar panic()s
(fatal user/admin errors on boot) to NOT print a stack trace+registers,
since it is useless and actually hides useful information.
root fs on %s, b);
}
Better would be for this and similiar panic()s
(fatal user/admin errors on boot) to NOT print a stack trace+registers,
since it is useless and actually hides useful information.
Best Regards
Ingo Oeser
--
To unsubscribe from this list: send the line unsubscribe linux
Hi Bernd,
CC'ed hpa, since I'm sure he can give useful advise on that :-)
On Sunday 06 January 2008, Bernd Schubert wrote:
On Sunday 06 January 2008, Ingo Oeser wrote:
Hi Bernd,
On Sunday 06 January 2008, you wrote:
Index: zd1211rw.git.beno/init/do_mounts.c
er lists
ARE internal variables) to modules.
What do you think?
Best Regards
Ingo Oeser
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
.
What do you think?
Best Regards
Ingo Oeser
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
that it is rounding and make the unit arbitrary.
That reduces the ABI requirements.
Best Regards
Ingo Oeser
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Regards
Ingo Oeser
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
ares here? That shouldn't be
killed by the OOM killer in that situation, should it?
Am I missing sth.?
Best Regards
Ingo Oeser
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/
be
killed by the OOM killer in that situation, should it?
Am I missing sth.?
Best Regards
Ingo Oeser
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please
).
So I'm fine either way, since I see you point.
Best Regards
Ingo Oeser
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
linux/leds.h under include/
Since you explicitly WANT user space to control these, that should
be the right API.
Richard, what do YOU think?
Best Regards
Ingo Oeser
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PR
include/
Since you explicitly WANT user space to control these, that should
be the right API.
Richard, what do YOU think?
Best Regards
Ingo Oeser
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
way, since I see you point.
Best Regards
Ingo Oeser
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
nd cached in
> the task_struct.
Why not make it a task flag, since according to your code, you are only
interested whether this is <= 1 or > 1. Since !(x <= 1) <=> (x > 1)
for any given unsigned integer x, the required data structure is
a "boolean" or a flag.
Best Regards
Ingo Oes
.
Why not make it a task flag, since according to your code, you are only
interested whether this is = 1 or 1. Since !(x = 1) = (x 1)
for any given unsigned integer x, the required data structure is
a boolean or a flag.
Best Regards
Ingo Oeser
-
To unsubscribe from this list: send the line
eady. So kbuild is just lacking an "else"
clause here.
Best Regards
Ingo Oeser
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Regards
Ingo Oeser
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
(see the kerneldoc).
^
So why not name it path_walk_put_pair() then?
Rationale: "_both" is just counting, "_pair"
means they are related somehow.
Best regards
Ingo Oeser
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
rther split that into -debug-y and -optimize-y flags,
but that was just for my own convenience.
Best Regards
Ingo Oeser
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordom
,
but that was just for my own convenience.
Best Regards
Ingo Oeser
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org
why not name it path_walk_put_pair() then?
Rationale: _both is just counting, _pair
means they are related somehow.
Best regards
Ingo Oeser
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
t;, 0644, NULL);
> + pe = create_proc_entry("root_user_cpu_share", 0644, NULL);
> if (!pe)
> return -ENOMEM;
What about moving this debug stuff under debugfs?
Please consider using the functions in .
They compile into nothing, if DEBUGFS is not compiled in
and have already
this debug stuff under debugfs?
Please consider using the functions in linux/debugfs.h .
They compile into nothing, if DEBUGFS is not compiled in
and have already useful functions for reading/writing integers
and booleans.
Best Regards
Ingo Oeser
-
To unsubscribe from this list: send the line
dows
tool. Linux people not always (want to) have access to Windows :-)
I reported the all the problems (starting 2001), no developer
seemed interested.
I can report them against the latest RC6 kernel tomorrow and put them
into bugzilla, if we now REALLY care.
Best Regards
Ingo Oeser
-
T
interested.
I can report them against the latest RC6 kernel tomorrow and put them
into bugzilla, if we now REALLY care.
Best Regards
Ingo Oeser
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
[PATCH] crypto: cleanup: Use max() in blkcipher_get_spot() to state the
intention.
Signed-off-by: Ingo Oeser <[EMAIL PROTECTED]>
---
Hi Herbert,
here is the requested patch against Linus' latest tree.
It at least compiles.
Best Regards
Ingo Oeser
crypto/blkcipher.c |2 +-
1
[PATCH] crypto: cleanup: Use max() in blkcipher_get_spot() to state the
intention.
Signed-off-by: Ingo Oeser [EMAIL PROTECTED]
---
Hi Herbert,
here is the requested patch against Linus' latest tree.
It at least compiles.
Best Regards
Ingo Oeser
crypto/blkcipher.c |2 +-
1 files changed
static inline u8 *blkcipher_get_spot(u8 *start, unsigned int len)
{
u8 *end_page = (u8 *)(((unsigned long)(start + len - 1)) & PAGE_MASK);
return max(start, end_page);
}
Best Regards
Ingo Oeser
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel&quo
().
NOTES
The value -1 for tid is reserved for future extension
(e.g. meaning ALL other threads).
This call might be restricted to the main thread.
-
Any opinions?
Best Regards
Ingo Oeser
-
To unsubscribe from this list: send the line "unsubscribe linux-kern
The value -1 for tid is reserved for future extension
(e.g. meaning ALL other threads).
This call might be restricted to the main thread.
-
Any opinions?
Best Regards
Ingo Oeser
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
rn (void *)p;
}
return NULL;
}
Now the compiler should see the loop more clearly.
Best Regards
Ingo Oeser
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo
;
}
return NULL;
}
Now the compiler should see the loop more clearly.
Best Regards
Ingo Oeser
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ
Hi Neil,
> +static struct limit_names lnames[RLIM_NLIMITS] = {
static const ...
may be better here.
Best Regards
Ingo Oeser
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vg
Hi Neil,
+static struct limit_names lnames[RLIM_NLIMITS] = {
static const ...
may be better here.
Best Regards
Ingo Oeser
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org
is in lib/genalloc.c, if you like to take a look.
Memory for MANAGING free/allocated space is NOT taken
from your on-card memory! That allocator is explicitly developed
for such use cases.
Happy hacking!
Best regards
Ingo Oeser
-
To unsubscribe from this list: send the line "unsubscribe
/genalloc.c, if you like to take a look.
Memory for MANAGING free/allocated space is NOT taken
from your on-card memory! That allocator is explicitly developed
for such use cases.
Happy hacking!
Best regards
Ingo Oeser
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
kfree(ff);
}
This will also fix the missing smp_barriers, is very simple, saves code,
makes your life easier and is a well known known kernel infrastructure :-)
BTW: FUSE rocks! :-)
You can add my "Signed-off-by: Ingo Oeser <[EMAIL PROTECTED]>",
if you want to use that sug
the missing smp_barriers, is very simple, saves code,
makes your life easier and is a well known known kernel infrastructure :-)
BTW: FUSE rocks! :-)
You can add my Signed-off-by: Ingo Oeser [EMAIL PROTECTED],
if you want to use that suggestion.
Best Regards
Ingo Oeser
-
To unsubscribe from this list
_MAX);
}
static inline bool ext4_dir_link_empty(const struct inode *dir)
{
#ifdef FOOBAR
return dir->i_nlink == 2 || dir->i_nlink == 1;
#else
return dir->i_nlink == 2;
#endif
}
FOOBAR is the define, which enables ext4_is_dx().
That is not in the patch, so left as an ex
}
FOOBAR is the define, which enables ext4_is_dx().
That is not in the patch, so left as an exercise to the reader :-)
Best Regards
Ingo Oeser
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
e the
damn fast change rate of Linux possible by keeping the base clean
and neat.
Best Regards
Ingo oeser
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Hi,
On Friday 08 June 2007, Nadia Derbey wrote:
> Ingo Oeser wrote:
> > ... together with this means 4*256 -> 1k of precious stack space used.
> > Please consider either lowering IPCS_MAX_SCAN_ENTRIES or kmalloc() that.
> You're completely right, but trying to lower the
Hi,
On Friday 08 June 2007, Nadia Derbey wrote:
Ingo Oeser wrote:
... together with this means 4*256 - 1k of precious stack space used.
Please consider either lowering IPCS_MAX_SCAN_ENTRIES or kmalloc() that.
You're completely right, but trying to lower the extraction size, I'm
afraid
Regards
Ingo oeser
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
nnot sleep, try to lower that constant (e.g. 16-32).
The current users use much smaller numbers.
If you can sleep and performance goes down after lowering that constant,
try to kmalloc these arrays (since kmalloc() of that small amount
should succeed easily).
Regards
Ingo Oeser
-
To unsubscrib
after lowering that constant,
try to kmalloc these arrays (since kmalloc() of that small amount
should succeed easily).
Regards
Ingo Oeser
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
s much more readable, more documented and doesn't contain a condition
monster :-)
@Patrick: Could you check, wether the PPPoE case is correct?
What do you think? Should I submit a patch for that?
Best Regards
Ingo Oeser
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
ocess or thread pool to scale beyond that.
Pool size is typically related to the amount of CPU cores in the system.
Regards
Ingo Oeser
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info a
to scale beyond that.
Pool size is typically related to the amount of CPU cores in the system.
Regards
Ingo Oeser
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo
);
else
return br_dev_queue_push_xmit(skb);
}
which is much more readable, more documented and doesn't contain a condition
monster :-)
@Patrick: Could you check, wether the PPPoE case is correct?
What do you think? Should I submit a patch for that?
Best Regards
Ingo Oeser
> keep sub-second sleep granularity?
No, I'm just overworked and getting sloppy :-/
Sorry for the noise...
Best regards
Ingo Oeser
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at h
t imagine a surveillance camera triggered by door entrance.
Yes, these things might run Linux (e.g. on "cris" architecture).
Or your VCR.
Yes, these devices might sleep more than they are awake,
if you are not a TV junkie :-)
Best regards
Ingo Oeser
-
To unsubscribe from this lis
VCR.
Yes, these devices might sleep more than they are awake,
if you are not a TV junkie :-)
Best regards
Ingo Oeser
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo
granularity?
No, I'm just overworked and getting sloppy :-/
Sorry for the noise...
Best regards
Ingo Oeser
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
magic.
Don't worry, we have __packed predefined for this.
Just look in include/linux/compiler-gcc.h
I love it, because I always forget at least one brace or undescore level :-)
Regards
Ingo Oeser
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
predefined for this.
Just look in include/linux/compiler-gcc.h
I love it, because I always forget at least one brace or undescore level :-)
Regards
Ingo Oeser
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
gt; is
Ok, what about debugfs then? If it is just for debugging blobs -> debugfs,
if it is crucial for operation -> sysfs and representation of one value
per file.
Regards
Ingo Oeser
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
t
blobs - debugfs,
if it is crucial for operation - sysfs and representation of one value
per file.
Regards
Ingo Oeser
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo
a feature to be a module on a kernel without
module support, it will effectivly be disabled.
And if it is so simple to do the same in userspace like you suggest,
than that's much better.
Best Regards
Ingo Oeser
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
on a kernel without
module support, it will effectivly be disabled.
And if it is so simple to do the same in userspace like you suggest,
than that's much better.
Best Regards
Ingo Oeser
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
.g. I don't want
to
mlseep() twice on the same reset timeout).
But we usually use locking to order that.
Do I miss anything fundamental here?
Regards
Ingo Oeser
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Mo
driver/subsystem
to actually queue work into a thread.
And when there is a close(), socket-destruction, service completion
or whatever these threads can be marked for destruction and destroyed
by a timer or even immediately.
Regards
Ingo Oeser
--
If something is getting cheap, it is getting waste
to actually queue work into a thread.
And when there is a close(), socket-destruction, service completion
or whatever these threads can be marked for destruction and destroyed
by a timer or even immediately.
Regards
Ingo Oeser
--
If something is getting cheap, it is getting wasted just
to
mlseep() twice on the same reset timeout).
But we usually use locking to order that.
Do I miss anything fundamental here?
Regards
Ingo Oeser
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
these counters quiete easy, since most of them are
the hamming weight (or population count) of some bitmaps.
Does this sound like a proper hacky solution? :-)
Regards
Ingo Oeser
pgpeUyaLE4v0G.pgp
Description: PGP signature
are
the hamming weight (or population count) of some bitmaps.
Does this sound like a proper hacky solution? :-)
Regards
Ingo Oeser
pgpeUyaLE4v0G.pgp
Description: PGP signature
Hi Randy,
On Monday 19 March 2007, Randy Dunlap wrote:
> Were there any patches written after this? If so, I missed them.
> If not, does this patch help any?
How is division by zero avoided? Maybe one can avoid setting it to zero.
Regards
Ingo Oeser
-
To unsubscribe from this list
Hi Randy,
On Monday 19 March 2007, Randy Dunlap wrote:
Were there any patches written after this? If so, I missed them.
If not, does this patch help any?
How is division by zero avoided? Maybe one can avoid setting it to zero.
Regards
Ingo Oeser
-
To unsubscribe from this list: send
hores aren't good "busy/ready flags", as you might have already noticed.
Many Thanks and Best Regards
Ingo Oeser, the down{_interruptible,}_timeout() implementation of Linux :-)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message t
Ingo Oeser, the down{_interruptible,}_timeout() implementation of Linux :-)
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
>vm_end : mm->mmap_base;
> mm->unmap_area(mm, addr);
> mm->mmap_cache = NULL; /* Kill the cache. */
> }
Please comment, why you think this is necessary.
Thanks & Regards
Ingo Oeser
-
To unsubscribe from this list: send the line "unsubscribe linux
. */
}
Please comment, why you think this is necessary.
Thanks Regards
Ingo Oeser
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ
On Monday, 5. February 2007, Linus Torvalds wrote:
> So thank God for the few selects we have, and we should add a whole lot
> more!
But "select" is not fine grained enough.
I would like to have "require", "recommend", "suggest" for feature A.
require X
does not work without X, but X
On Monday, 5. February 2007, Linus Torvalds wrote:
So thank God for the few selects we have, and we should add a whole lot
more!
But select is not fine grained enough.
I would like to have require, recommend, suggest for feature A.
require X
does not work without X, but X is way down
unsigned long seg_limit;
size_t nr_bytes;
};
That will enable resizeable iodescs with partial completion state and
will enable successive filling of an iodesc with iovs.
This will be needed anyway. I built an complete short userspace
module for that already. I can post an
.data = NULL,
> + .maxlen = 0,
> + .mode = 0600,
> + .proc_handler = _do_freq
> + },
> + {}
> };
dito
Regards
Ingo Oeser
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel&qu
,
> + .procname = "autoprobe0",
> + .data = NULL,
> + .maxlen = 0,
> + .maxlen = 0444,
> + .proc_handler = _autoprobe
> + },
Typo here?
completion state and
will enable successive filling of an iodesc with iovs.
This will be needed anyway. I built an complete short userspace
module for that already. I can post and GPLv2 it somewhere, if people
are interested.
Regards
Ingo Oeser
-
To unsubscribe from this list: send the line unsubscribe
= NULL,
+ .maxlen = 0,
+ .maxlen = 0444,
+ .proc_handler = do_autoprobe
+ },
Typo here? .mode = 0444 makes mor sense.
Regards
Ingo Oeser
-
To unsubscribe from this list: send the line
= pm_do_freq
+ },
+ {}
};
dito
Regards
Ingo Oeser
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Monday, 1. January 2007 17:25, Andreas Schwab wrote:
> Ingo Oeser <[EMAIL PROTECTED]> writes:
> > Then this works, because the side effect (+20) is evaluated only once.
>
> It's not a side effect, it's a non-lvalue, and you can't take the address
> of a non-lvalue.
Hi,
On Monday, 1. January 2007 07:37, Amit Choudhary wrote:
> --- Ingo Oeser <[EMAIL PROTECTED]> wrote:
> > #define kfree_nullify(x) do { \
> > if (__builtin_constant_p(x)) { \
> > kfree(x); \
> > } else { \
> > typeof
Hi,
On Monday, 1. January 2007 07:37, Amit Choudhary wrote:
--- Ingo Oeser [EMAIL PROTECTED] wrote:
#define kfree_nullify(x) do { \
if (__builtin_constant_p(x)) { \
kfree(x); \
} else { \
typeof(x) *__addr_x = x; \
Ok, I should change that line
On Monday, 1. January 2007 17:25, Andreas Schwab wrote:
Ingo Oeser [EMAIL PROTECTED] writes:
Then this works, because the side effect (+20) is evaluated only once.
It's not a side effect, it's a non-lvalue, and you can't take the address
of a non-lvalue.
Just verified this. So If we
#define kfree_nullify(x) do { \
if (__builtin_constant_p(x)) { \
kfree(x); \
} else { \
typeof(x) *__addr_x = \
kfree(*__addr_x); \
*__addr_x = NULL; \
} \
} while (0)
Regards
Ingo Oeser
-
To unsubscribe from this lis
case MSR_IA32_P5_MC_TYPE:
> case MSR_IA32_MC0_CTL:
What about just defining constants for these?
Then you can rip out these comments.
Same for linux-2.6/drivers/kvm/vmx.c
Regards
Ingo Oeser
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the b
MSR_IA32_MC0_CTL:
What about just defining constants for these?
Then you can rip out these comments.
Same for linux-2.6/drivers/kvm/vmx.c
Regards
Ingo Oeser
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
{ \
if (__builtin_constant_p(x)) { \
kfree(x); \
} else { \
typeof(x) *__addr_x = x; \
kfree(*__addr_x); \
*__addr_x = NULL; \
} \
} while (0)
Regards
Ingo Oeser
-
To unsubscribe from this list: send the line unsubscribe linux
PV6) || defined(CONFIG_IPV6_MODULE)
> + case AF_INET6:
> + do {
> + struct in6_pktinfo *pki =
> + (struct in6_pktinfo *) CMSG_DATA(cmh);
> +
No casting needed, so:
struct in6_pktinfo *pki = CMSG
et rid of it? (Seems to apply to other places as well.)
Because if done properly that often exceeds the 80 column limit.
The intermediate variable should be optimized away from the compiler.
But kcalloc() is better for another reason: Overflow checking.
Regards
Ingo Oeser
-
To unsubscribe from this
exceeds the 80 column limit.
The intermediate variable should be optimized away from the compiler.
But kcalloc() is better for another reason: Overflow checking.
Regards
Ingo Oeser
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
1 - 100 of 443 matches
Mail list logo