linux.kernel Google Group

Re: Add PGM protocol support to the IP stack

2010-03-22T14:30:02Z

It is needed. PGM ports exist and work similarly to UDP and TCP ports.
PGM as provided by openpgm and other solutions avoids native PGM and
instead uses PGM over UDP. But the routers do not support PGM over UDP in
the same way as native PGM. So the NAK suppression and other advanced
features available in Juniper and Cisco switches cannot be used.

Re: Add PGM protocol support to the IP stack

2010-03-22T14:30:02Z

Not the only reason. There are also performance implications. NAKing and
other control messages from user space are a pain and the available
implementations add numerous threads just to control the timing of control
messages and the expiration of data etc. Its difficult to listen to a PGM
port from user space. You have to get all messages for the PGM protocol

Re: [RFC][PATCH] Convert alpha to use clocksource

2010-03-22T14:30:02Z

clocks_calc_mult_shift() is what you are looking for.
Thanks,
tglx

Re: [RFC] Unify KVM kernel-space and user-space code into a single project

2010-03-22T14:30:02Z

I think we don't need per-guest-file access control. Probably we could
apply the image-file permissions to all guestfs files. This would cover
the usecases:
* perf for reading symbol information (needs ro-access only
anyway)
* Desktop like host<->guest file copy
I have not looked into libguestfs yet but I guess this approach is

Re: [PATCH] staging: winbond: phy_calibration.c Coding style fixes 1/2.

2010-03-22T14:30:02Z

[ snip ]
I'm really happy that you're using my script. It feels more relaxing to
review these when I know that no bugs were introduced.
regard,
dan carpenter

Re: [RFC patch 2/3] tree/tiny rcu: Add debug RCU head objects (v3)

2010-03-22T14:30:01Z

Yes it is. astate is set to 0 upon activation, and STATE_RCU_HEAD_READY is 0.
This is the initial state of the state machine (and also the accepting state).
+/*
+ * Active state:
+ * - Set at 0 upon initialization.
+ * - Must return to 0 before deactivation.
+ */
+extern void
+debug_object_active_state(voi d *addr, struct debug_obj_descr *descr,

Re: [RFC] Unify KVM kernel-space and user-space code into a single project

2010-03-22T14:30:01Z

Frankly, Linux is mainly growing in the server space due to:
1) the server space is technically much simpler than the desktop space. It
is far easier to code up a server performance feature than to make
struggle through stupid (server-motivated) package boundaries and get
something done on the desktop. It is far easier to code up a server app

[PATCH] staging: winbond: phy_calibration.c Coding style fixes 1/2.

2010-03-22T14:20:02Z

Whitespace and indentation fixes. Removed "commented away"
code and revision comments.
Checked with Dan Carpenters strip_whitespace.pl and diff.
Compiles fine and .o file is identical before and after.
Signed-off-by: Lars Lindley <lind...@coyote.org>
---
drivers/staging/winbond/phy_ca libration.c | 1510 +++++++++++++----------------

Re: [PATCH v1 1/10] Move Macro W to insn.h

2010-03-22T14:20:01Z

Currently, we don't have any maps for this bit.
Other two bits are ok for me :)
Thank you,

Re: [RFC] Unify KVM kernel-space and user-space code into a single project

2010-03-22T14:20:02Z

Totally. That's not to say there is a definite plan, but we're very
open to doing this. We already wrote the daemon in such a way that it
doesn't require the appliance part, but could run inside any existing
guest (we've even ported bits of it to Windoze ...).
The only remaining issue is how access control would be handled. You

Re: [PATCH 05/10] x86: use vector_desc instead of vector_irq

2010-03-22T14:20:01Z

Hmm, I thought that was fixed, but I might be wrong as usual.

I really have a hard time to see how assigning a void pointer to a
struct irq_cfg pointer is anymore type safe than using the void
pointer as for the function argument right away.
You mean hysterical raisins. Ok, how about:
pr_emerg("irq: %d.d irq vector not assigned\n", ...);

[PATCH] staging: winbond: phy_calibration.c Coding style fixes 2/2

2010-03-22T14:20:02Z

I fixed the rest of the checkpatch.pl problems except long lines.
I removed () from returns and added () to a macro.
I removed a lot of unneccesary {}.
Generated .o file is still identical to before.
This patch applies after the 1/2 one.
Signed-off-by: Lars Lindley <lind...@coyote.org>
---
drivers/staging/winbond/phy_ca libration.c | 73 +++++++++++------------------

Re: locking problems: Btrfs: be more selective in the defrag ioctl

2010-03-22T14:10:03Z

Ahh yeah you are right, should probably just put a mutex_unlock before the break
in both cases. Thanks,
Josef

Re: [RFC] Unify KVM kernel-space and user-space code into a single project

2010-03-22T14:10:03Z

I think it would be a nice option to allow such guest-side "daemon's" to be
executed in the guest context without _any_ guest-side support.
This would be possible by building such minimal daemons that use vmchannel,
and which are built for generic x86 (maybe even built for 32-bit x86 so that
they can run on any x86 distro). They could execute as the init task of any

Re: [PATCH 05/10] x86: use vector_desc instead of vector_irq

2010-03-22T14:10:02Z

Well at least originally DECLARE_PER_CPU chocked when given a complex
type. Does:
DECLARE_PER_CPU(struct irq_desc *[NR_VECTORS], vector_desc);
work?
You want to deliberately loose a modicum of type safety?
Long evolution. Do you have a suggestion of better wording?
Eric