> > In a previous post I incorrectly stated that my serial port is a
> > TI16750, as this is what /proc/tty/... revealed to me. After
> > re-reading the product manual, I see that this is actually a 16550.
> > Since Linux is seeing this port as a 16750, could that explain why I'm
> > seeing missin
On Wed, Feb 14, 2007 at 03:32:04PM -0500, Lee Schermerhorn wrote:
> On Tue, 2007-02-13 at 07:09 +0100, Nick Piggin wrote:
> > Hi,
> >
> > Just tinkering around with this and got something working, so I'll see
> > if anyone else wants to try it.
> >
> > Not proposing for inclusion, but I'd be inte
On Wed, 14 Feb 2007, Benjamin LaHaise wrote:
> On Wed, Feb 14, 2007 at 03:17:59PM -0800, Davide Libenzi wrote:
> > > That's an incorrect assumption. Every task/thread in the system has FPU
> > > state associated with it, in part due to the fact that glibc has to
> > > change
> > > some of the
On Thu, 15 Feb 2007, Nick Piggin wrote:
> But no arguments, this doesn't aim to do replication of the same virtual
> address. If you did come up with such a scheme, however, you would still
> need a replicated pagecache for it as well.
Well there is always the manual road. Trigger something that
On Thu, Feb 08, 2007 at 09:13:36PM +0100, Miklos Szeredi wrote:
> Strangely enough after continuing in gdb, UML is back to normal, and I
> can't make it hang any more. It must be something timing related.
Can you see if the patch below fixes it?
Jeff
--
Work emai
On Wednesday 14 February 2007 3:20 pm, Len Brown wrote:
> >
> > I still need to resubmit the patch, for X86_PC, which defines the platform
> > device in the (common) case where PNPACPI isn't defined.
>
> CONFIG_PNPACPI=y is not the common case?
It's certainly not in the defconfig for x86-64. An
Eric W. Biederman wrote:
> Ok. If that is all this may be a difference that makes no difference.
> binutils has a bad habit of looking at sections (which are fully
> optional) instead of segments on ET_EXEC and ET_DYN objects. Only
> ET_REL objects (.o files) are required to have sections.
>
On Wed, Feb 14, 2007 at 11:00:02AM -0800, Christoph Lameter wrote:
> On Tue, 13 Feb 2007, Nick Piggin wrote:
>
> > This is a scheme for page replication replicates read-only pagecache pages
> > opportunistically, at pagecache lookup time (at points where we know the
> > page is being looked up for
Eric W. Biederman wrote:
> Jeremy Fitzhardinge <[EMAIL PROTECTED]> writes:
>
>
>> Add Xen interface header files. These are taken fairly directly from
>> the Xen tree and hence the style is not entirely in accordance with
>> Linux guidelines. There is a tension between fitting with Linux coding
Davide Libenzi wrote:
>> Would this work?
>>
>
> Hopefully the API will simplify enough so that emulation will becomes
> easier.
>
The big question in my mind is how all this stuff interacts with
signals. Can a blocked syscall atom be interrupted by a signal? If so,
what thread does it
On Wed, Feb 14, 2007 at 10:57:00AM -0800, Christoph Lameter wrote:
> On Tue, 13 Feb 2007, Nick Piggin wrote:
>
> > Just tinkering around with this and got something working, so I'll see
> > if anyone else wants to try it.
> >
> > Not proposing for inclusion, but I'd be interested in comments or r
* Ingo Molnar <[EMAIL PROTECTED]> wrote:
> > You are not counting the whole setup cost there, then, because your
> > setup cost is going to be at a minimum more expensive than the null
> > system call.
>
> hm, this one-time cost was never on my radar. [ It's really dwarved by
> other startup
Jan Engelhardt <[EMAIL PROTECTED]> writes:
>>I checked, and looking at offset 0x497 seems to work fine on a couple of
>>systems with USB keyboards.
>
> Probably just because legacy mode was enabled. Plus I wonder what 0x497 will
> return when there is actually more than one USB keyboard connected
Dmitry Torokhov <[EMAIL PROTECTED]> wrote:
> On 2/14/07, Németh Márton <[EMAIL PROTECTED]> wrote:
> >
> >
> > Dmitry Torokhov <[EMAIL PROTECTED]> írta:
> >
> > > On 2/11/07, Németh Márton <[EMAIL PROTECTED]> wrote:
> > > >
> > > > Extend EV_LED handling code so that it can handle not
> > > > onl
* Linus Torvalds <[EMAIL PROTECTED]> wrote:
> > case. (but with some crazier hacks i got the one-shot atom overhead
> > [compared to a simple synchronous null syscall] to below 10 nsecs,
> > so there's room in there for further optimizations. Our current null
> > syscall latency is around ~150
Rafael J. Wysocki wrote:
>> Why a new flag?
>
> For example, there are drivers that define .suspend() and .resume() which
> do not work correctly and we can use the flag to mark them.
Depending on how serious the problems with these .suspend/.resume()s
are, you could also put a printk in them or
On Wed, Feb 14, 2007 at 03:17:59PM -0800, Davide Libenzi wrote:
> > That's an incorrect assumption. Every task/thread in the system has FPU
> > state associated with it, in part due to the fact that glibc has to change
> > some of the rounding mode bits, making them different than the default fr
Jan Kara <[EMAIL PROTECTED]> writes:
> Yes I see some correlation. Again it seems there is a problem with buffers
> attached to a page which got truncated but Private flag of the page stayed.
> It's probably not important but just out of curiosity - do you have
> CONFIG_LBD (large block device)
On Wed, 14 Feb 2007 13:53:08 -0800
Zachary Amsden <[EMAIL PROTECTED]> wrote:
> > IDE on several platforms has performance critical paths that use
> > ndelay(400) or failing that udelay(1)
>
> Ok, I buy that. A 486DX / 33 Mhz processor takes 10 cycles to issue a
> CALL / RET pair. This is about
On Wed, 14 Feb 2007 22:58:42 +0100 (MET)
Jan Engelhardt <[EMAIL PROTECTED]> wrote:
> Probably just because legacy mode was enabled. Plus I wonder what 0x497 will
> return when there is actually more than one USB keyboard connected at boot.
The BIOS initial numlock value which is a singular value.
> users I'd rather try to convince the IDE maintainer to use a
> "real_hardware_mdelay()" or something here.
The IDE/ATA layer has a single function which decides what non PCI
probing to do so could learn to spot virtualisation easily enough. In the
case of libata ISA is now obscure enough that yo
On Wed, 14 Feb 2007 16:11:14 -0700
[EMAIL PROTECTED] wrote:
> In a previous post I incorrectly stated that my serial port is a
> TI16750, as this is what /proc/tty/... revealed to me. After
> re-reading the product manual, I see that this is actually a 16550.
> Since Linux is seeing this port as
On Wednesday 14 February 2007 14:55, David Brownell wrote:
> On Wednesday 14 February 2007 10:09 am, Dave Jones wrote:
> > This option is useful for all of the X86 subarchs afaik (and especially
> > X86_GENERICARCH).
>
> You're right ... _potentially_ useful, which is the same standard used
> in
Hi,
I've got this in the resume-during-suspend phase of suspend to disk with
2.6.20-git10 on HPC nx6325:
PCI: Setting latency timer of device :00:06.0 to 64
sata_sil :00:12.0: resuming
BUG: at drivers/pci/pci.c:817 pcim_enable_device()
Call Trace:
[] pcim_enable_device+0x93/0xb3
[] ata
On Wed, 14 Feb 2007, Benjamin LaHaise wrote:
> On Wed, Feb 14, 2007 at 01:06:59PM -0800, Davide Libenzi wrote:
> > Bear with me Ben, and let's follow this up :) If you are in the middle of
> > an MMX copy operation, inside the syscall, you are:
> >
> > - Userspace, on task A, calls sys_async_exe
In a previous post I incorrectly stated that my serial port is a
TI16750, as this is what /proc/tty/... revealed to me. After
re-reading the product manual, I see that this is actually a 16550.
Since Linux is seeing this port as a 16750, could that explain why I'm
seeing missing characters in the
On Wed, 14 Feb 2007, Ingo Molnar wrote:
>
> i think you are banging on open doors. That async_stat() call is very
> much what i'd like to see glibc to provide, not really the raw syslet
> interface.
Right. Which is why I wrote (and you removed) the rest of my email.
If the "raw" interfaces a
Linus,
I'm tired of seeing a warning every time jfs is compiled. A similar patch
has been in jgarzik's misc-2.6.git#gccbug for a while now.
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/shaggy/jfs-2.6.git for-linus
This will update the following files:
fs/jfs/jfs_txnmgr.c |
Will,
On Wed, Feb 14, 2007 at 12:05:31PM -0500, William Cohen wrote:
> >The oprofile patch should be made against the oprofile cvs rather than
> >the 0.9.2 tarball. There are some files that the patch touches that are
> >created by the autogen.sh.
> >
> >The oprofile patch doesn't build if thin
On Thu, 2007-02-15 at 00:57 +1100, Herbert Xu wrote:
> On Wed, Feb 14, 2007 at 03:47:55PM +1100, Rusty Russell wrote:
> >
> > It's also used to generate dma structs for outgoing packets. In that
> > case, skb_headlen() == 0:
>
> I see, in that case you're guaranteed to have no fragments.
> Still
On Wednesday 14 February 2007 11:39, Andreas Gruenbacher wrote:
> On Wednesday 14 February 2007 07:37, Linus Torvalds wrote:
> > We could prepend another '/' (so that you'd have a path that starts with
> > "//"). That's still a legal path, but it's also somethign that even POSIX
> > says is valid t
> We've beat this almost to death... just need some patch merged.
Sorry, missed the discussion I guess...
-
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
Plea
On Wed, 14 Feb 2007 14:41:05 -0800 Roland Dreier wrote:
> Commit 42da9cbd ("mm: mincore anon") breaks CONFIG_SWAP=n builds with:
>
> mm/built-in.o: In function `sys_mincore':
> (.text+0xe2c4): undefined reference to `swapper_space'
>
> because swapper_space is used unconditionally in mm/
On Mon, 2007-02-05 at 19:53 -0800, Zachary Amsden wrote:
> Failure to use real-time delay here causes the keyboard to become demonically
> possessed in the event of a kernel crash, with wildly blinking lights and
> unpredictable behavior. This has resulted in several injuries.
The problem is the
On Wednesday 14 February 2007 22:54, Dave Jones wrote:
> Without this, building drivers/serial/of_serial.c as a module fails.
>
> WARNING: ".of_find_property" [drivers/serial/of_serial.ko] undefined!
>
> Signed-off-by: Dave Jones <[EMAIL PROTECTED]>
Acked-by: Arnd Bergmann <[EMAIL PROTECTED]>
S
Commit 42da9cbd ("mm: mincore anon") breaks CONFIG_SWAP=n builds with:
mm/built-in.o: In function `sys_mincore':
(.text+0xe2c4): undefined reference to `swapper_space'
because swapper_space is used unconditionally in mm/mincore.c but only
defined in swap_state.c, which isn't built if CONF
* Alan <[EMAIL PROTECTED]> wrote:
> >this "AIO atom" in the first place, WHICH WE KNOW IS INCORRECT,
> >since current users use "aio_read()" that simply doesn't have
> >that and doesn't build up any such data structures.
>
> Do current users do this because that is all they have, b
> @@ -332,7 +333,7 @@ int ehca_destroy_cq(struct ib_cq *cq)
> spin_lock_irqsave(&ehca_cq_idr_lock, flags);
> while (my_cq->nr_callbacks) {
> spin_unlock_irqrestore(&ehca_cq_idr_lock, flags);
> - yield();
> + wait_for_completion(&my_cq->zer
Hi-
A few high level comments, then some really insignificant ones.
First, is there a reason why we shouldn't have a sysfs entry/kobject for
each logical port? How is it possible to determine, from the adapter
sysfs directory, the current number of ports for that adapter? A port
sysfs directory
hello,
I just got a new motherboard with an MCP51. The kernel detects it but then
I have no eth0 device.
from lspci:
00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3)
dmesg shows:
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.59.
ACPI: PCI Interrupt Link
On Wed, Feb 14, 2007 at 09:59:37PM +, David Howells wrote:
> Michael Halcrow <[EMAIL PROTECTED]> wrote:
>
> > Right now, eCryptfs just delegates its modular exponentiation
> > operations to a userspace daemon. If RSA ever finds its way into the
> > kernel, I might tweak eCryptfs to use that in
* Linus Torvalds <[EMAIL PROTECTED]> wrote:
> Or how would you do the trivial example loop that I explained was a
> good idea:
>
> struct one_entry *prev = NULL;
> struct dirent *de;
>
> while ((de = readdir(dir)) != NULL) {
> struct one_entry *entry = m
On Wed, 2007-02-14 at 17:04 -0500, Benjamin LaHaise wrote:
> On Wed, Feb 14, 2007 at 10:49:44PM +0100, Ingo Molnar wrote:
> > this can very much be done, with a straightforward extension of how we
> > handle FPU state. That makes sense independently of syslets/async as
> > well, so find below the
On Wednesday 14 February 2007 10:09 am, Dave Jones wrote:
> This option is useful for all of the X86 subarchs afaik (and especially
> X86_GENERICARCH).
You're right ... _potentially_ useful, which is the same standard used
in most of the other cases. The "X86_PC" is debris from an early version
Looks fine but this patch at least has serious whitespace
damage... please resend a fixed version.
- R.
-
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
Michael Halcrow <[EMAIL PROTECTED]> wrote:
> Right now, eCryptfs just delegates its modular exponentiation
> operations to a userspace daemon. If RSA ever finds its way into the
> kernel, I might tweak eCryptfs to use that instead for some of the
> public key operations.
Am I right in thinking th
On Wed, Feb 14, 2007 at 10:49:44PM +0100, Ingo Molnar wrote:
> this can very much be done, with a straightforward extension of how we
> handle FPU state. That makes sense independently of syslets/async as
> well, so find below the standalone patch from Arjan. It's in my current
> syslet queue an
Val,
Maybe it is not only our (FS people) problem. We probably need to
bring the kernel people judge as ext2 and ext3 are the base Linux FS.
I add the kernel list for opinion.
/Sorin
On Wed, 14 Feb 2007 14:54:54 -0500, Valerie Henson
<[EMAIL PROTECTED]> wrote:
Just some quick notes on poss
Without this, building drivers/serial/of_serial.c as a module fails.
WARNING: ".of_find_property" [drivers/serial/of_serial.ko] undefined!
Signed-off-by: Dave Jones <[EMAIL PROTECTED]>
--- linux-2.6.20.noarch/arch/powerpc/kernel/prom.c~ 2007-02-14
16:52:47.0 -0500
+++ linux-2.6.20.n
Is this of any interest?
[ 141.713801] ===
[ 141.713891] [ INFO: possible circular locking dependency detected ]
[ 141.713937] 2.6.20 #2
[ 141.713980] ---
[ 141.714025] tor/5534 is trying t
Hi,
On Feb 14 2007 14:34, Dax Kelson wrote:
>
>I checked, and looking at offset 0x497 seems to work fine on a couple of
>systems with USB keyboards.
Probably just because legacy mode was enabled. Plus I wonder what 0x497 will
return when there is actually more than one USB keyboard connected at
On Mon, 12 Feb 2007 23:43:38 -0800
Trond Myklebust <[EMAIL PROTECTED]> wrote:
> From: Trond Myklebust <[EMAIL PROTECTED]>
>
> invalidate_inode_pages2() should not try to fix races between direct_IO and
> mmap(). It should only be trying to clear out pages that were dirty before
> the direct_IO wr
On Mon, 12 Feb 2007 23:43:35 -0800
Trond Myklebust <[EMAIL PROTECTED]> wrote:
> From: Trond Myklebust <[EMAIL PROTECTED]>
>
> Fix invalidate_inode_pages2_range() so that it does not immediately exit
> just because a single page in the specified range could not be removed.
>
One man's "fix" is a
On Feb 14 2007 16:10, sfaibish wrote:
>>
>> 1. DualFS has only one copy of every meta-data block. This copy is
>> in the meta-data device,
Where does this differ from typical filesystems like xfs?
At least ext3 and xfs have an option to store the log/journal
on another device too.
>> The DualFS
Alan wrote:
??? I fail to see the code bloat and also the fast paths. Which fast
paths use udelay?
IDE on several platforms has performance critical paths that use
ndelay(400) or failing that udelay(1)
Ok, I buy that. A 486DX / 33 Mhz processor takes 10 cycles to issue a
CALL / RET p
* Benjamin LaHaise <[EMAIL PROTECTED]> wrote:
> On Wed, Feb 14, 2007 at 12:14:29PM -0800, Davide Libenzi wrote:
> > I think you may have mis-interpreted my words. *When* a schedule
> > would block a synco execution try, then you do have a context
> > switch. Noone argue that, and the code is cl
Hi,
On Wednesday, 14 February 2007 15:40, Gautham R Shenoy wrote:
> Hello Everybody,
>
> This is an experiment towards process_freezer based implementation
> of cpu-hotplug. This is mainly based on ideas of Andrew Morton,
> Ingo Molnar and Paul Mckenney featured in the discussion
> http://lkml.o
On Wednesday, 14 February 2007 16:41, Igor Stoppa wrote:
> On Tue, 2007-02-13 at 10:47 +1100, ext Nigel Cunningham wrote:
> > Hi.
> >
> > On Tue, 2007-02-13 at 00:23 +0100, Rafael J. Wysocki wrote:
> > > Hi,
> > >
> > > Here's my attempt to document the requirements with respect to the basic
> >
* Linus Torvalds <[EMAIL PROTECTED]> wrote:
> - it fundamentally is based on a broken notion that everything would
>use this "AIO atom" in the first place, WHICH WE KNOW IS INCORRECT,
>since current users use "aio_read()" that simply doesn't have that
>and doesn't build up any such
On Tue, 13 Feb 2007 17:11:19 +1100
Nick Piggin <[EMAIL PROTECTED]> wrote:
> NeilBrown wrote:
> > Another nfsd patch for 2.6.21...
> >
> > ### Comments for Changeset
> >
> > When NFSD receives a write request, the data is typically in a number
> > of 1448 byte segments and writev is used to colle
On Wed, Feb 14, 2007 at 01:06:59PM -0800, Davide Libenzi wrote:
> Bear with me Ben, and let's follow this up :) If you are in the middle of
> an MMX copy operation, inside the syscall, you are:
>
> - Userspace, on task A, calls sys_async_exec
>
> - Userspace in _not_ doing any MMX stuff before t
> - it assumes we are going to make these complex state machines (which I
>don't believe for a second that a real program will do)
They've not had the chance before and there are certain chains of them
which make huge amounts of sense because you don't want to keep taking
completion hits. No
Bill Davidsen wrote:
Greg Trounson wrote:
At the risk of sounding like a "me too" post:
I also have an Asus P5W-DH, with the following drives connected:
SATA: ST3250820AS, connected to sata1
PATA: HL-DT-ST GSA-H12N, ATAPI DVD Writer, Primary master
On bootup of 2.6.19 and 2.6.20, the kernel s
On Sat, 10 Feb 2007 22:06:37 -0500, Sorin Faibish <[EMAIL PROTECTED]> wrote:
Introducing DualFS
File System developers played with the idea of separation of
meta-data from data in file systems for a while. The idea was
lately revived by a small group of file system enthusiasts
from Spain (from
Time for a little bit of dead horse flogging.
On Mon, Mar 06, 2006 at 05:05:52PM -0800, Andrew Morton wrote:
> > --- a/include/asm-generic/unaligned.h
> > +++ b/include/asm-generic/unaligned.h
> > @@ -78,7 +78,7 @@ static inline void __ustw(__u16 val, __u
> >
> > #define __get_unaligned(ptr, s
* Linus Torvalds <[EMAIL PROTECTED]> wrote:
> But the whole point is that the notion of a "register" is wrong in the
> first place. [...]
forget about it then. The thing we "register" is dead-simple:
struct async_head_user {
struct syslet_uatom __user **completion_ring;
On Wed, 2007-02-14 at 11:32 -0800, Linus Torvalds wrote:
>
> On Wed, 14 Feb 2007, Jean Delvare wrote:
> >
> > On x86, the BIOS led state can be read from byte 0x97 the BIOS RAM. The
> > BIOS RAM is mapped at 0x400 so all we need to do is to one byte from
> > RAM (offset 0x497). This is how Suse's
On Wed, 14 Feb 2007, Jeremy Fitzhardinge wrote:
> Are there any special semantics that result from running the syslet
> atoms in kernel mode? If I wanted to, could I write a syslet emulation
> in userspace that's functionally identical to a kernel-based
> implementation? (Obviously the performan
On Wed, Feb 14, 2007 at 07:40:57PM +, David Howells wrote:
> Hashing, yes; encryption, yes; signature checking: no from what I
> can see.
>
> It's possible that I can share code with eCryptFS, though at first
> sight that doesn't seem to overlap with what I want to do.
Right now, eCryptfs jus
On Wed, 14 Feb 2007, Ingo Molnar wrote:
>
> hm, there must be some misunderstanding here. That mlock is /only/ once
> per the lifetime of the whole 'head' - i.e. per sys_async_register().
> (And you can even forget i ever did it - it's 5 lines of code to turn
> the completion ring into a swap
The IPMI driver used enable_irq and disable_irq when it got into
situations where it couldn't allocate memory; it did this to avoid
having the interrupt just lock the machine when it couldn't get
memory to perform the transaction to disable the interrupt.
This patch modifies the driver to not use
On Wed, 2007-02-14 at 19:17 +0900, Paul Mundt wrote:
> On Wed, Feb 14, 2007 at 11:02:06AM +0100, Geert Uytterhoeven wrote:
> > On Wed, 14 Feb 2007, Paul Mundt wrote:
> > > This would seem like a reasonable candidate for a 'depends on' instead of
> > > a select..
> >
> > That's what we originally h
On Wed, 2007-02-14 at 18:17 -0200, Marcelo Tosatti wrote:
> On Wed, Feb 14, 2007 at 02:55:46PM -0500, Dave Jones wrote:
> > On Wed, Feb 14, 2007 at 05:08:39PM -0200, Marcelo Tosatti wrote:
> > >
> > > movntq instruction is supported by Geode CPU's, so use
> > > fast_clear_page/fast_copy_page ve
> ??? I fail to see the code bloat and also the fast paths. Which fast
> paths use udelay?
IDE on several platforms has performance critical paths that use
ndelay(400) or failing that udelay(1)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message t
ACK - the patch is fine for lpfc
-- james s
Linas Vepstas wrote:
James,
Please review and forward upstream. This is a patch I'd previously
submitted, and reworked by [EMAIL PROTECTED] in January.
Not clear if I need to also nag James Smart (who is listed as the
maintainer) for an Acked-b
* Ingo Molnar <[EMAIL PROTECTED]> wrote:
> * Linus Torvalds <[EMAIL PROTECTED]> wrote:
>
> > And the whole "lock things down in memory" approach is bad. It's
> > doing expensive things like mlock(), making the overhead for
> > _single_ system calls much more expensive. [...]
>
> hm, there mus
On Wed, 14 Feb 2007, Linus Torvalds wrote:
>
>
> On Tue, 13 Feb 2007, Ingo Molnar wrote:
> >
> > the core syslet / async system calls infrastructure code.
>
> Ok, having now looked at it more, I can say:
>
> - I hate it.
>
> I dislike it intensely, because it's so _close_ to being usable. B
Jeremy Fitzhardinge <[EMAIL PROTECTED]> writes:
> Eric W. Biederman wrote:
>> Well I did a little by hand parsing and the not I parsed looked ok.
>>
>> How does the output differ from a what you get when xen-head.S is
>> included?
>>
> Ah!
>
> The .notes section gets SHT_NOTE in vmlinux when xe
On Wed, 14 Feb 2007, Benjamin LaHaise wrote:
> On Wed, Feb 14, 2007 at 12:14:29PM -0800, Davide Libenzi wrote:
> > I think you may have mis-interpreted my words. *When* a schedule would
> > block a synco execution try, then you do have a context switch. Noone
> > argue that, and the code is clea
* Linus Torvalds <[EMAIL PROTECTED]> wrote:
> And the whole "lock things down in memory" approach is bad. It's doing
> expensive things like mlock(), making the overhead for _single_ system
> calls much more expensive. [...]
hm, there must be some misunderstanding here. That mlock is /only/ on
On Wed, 14 Feb 2007 17:08:39 -0200
Marcelo Tosatti <[EMAIL PROTECTED]> wrote:
>
> movntq instruction is supported by Geode CPU's, so use
> fast_clear_page/fast_copy_page versions that have it.
Is it actually faster for macro performance not just microbenchmarking ?
Alan
-
To unsubscribe from th
On 2/13/07, Kay Sievers <[EMAIL PROTECTED]> wrote:
On Tue, 2007-02-13 at 17:04 +0100, Marcel Holtmann wrote:
> > kernel BUG at lib/iomap.c:254!
> > invalid opcode: [#1]
> > ...
> >
> > The screen picture is here:
> > http://vrfy.org/pci_iounmap.jpg
> >
> > It's a Thinkpad T43p.
> >
> > 2.6
On Tue, 2007-02-13 at 07:09 +0100, Nick Piggin wrote:
> Hi,
>
> Just tinkering around with this and got something working, so I'll see
> if anyone else wants to try it.
>
> Not proposing for inclusion, but I'd be interested in comments or results.
>
> Thanks,
> Nick
I've included a small patch
Ingo Molnar wrote:
> Syslets consist of 'syslet atoms', where each atom represents a single
> system-call. These atoms can be chained to each other: serially, in
> branches or in loops. The return value of an executed atom is checked
> against the condition flags. So an atom can specify 'exit on
On Wed, Feb 14, 2007 at 06:17:36PM -0200, Marcelo Tosatti wrote:
> On Wed, Feb 14, 2007 at 02:55:46PM -0500, Dave Jones wrote:
> > On Wed, Feb 14, 2007 at 05:08:39PM -0200, Marcelo Tosatti wrote:
> > >
> > > movntq instruction is supported by Geode CPU's, so use
> > > fast_clear_page/fast_
Hi!
>
> >>>I have (had?) code that 'exploits' this. I believe I could eat 90% of cpu
> >>>without being noticed.
> >>
> >>Slightly changed version of hog(around 3 lines in total changed) does that
> >>easily on 2.6.18.3 on PPC.
> >>
> >>http://www.boblycat.org/~malc/apc/load-hog-ppc.png
> >
> >I g
Jeremy Fitzhardinge <[EMAIL PROTECTED]> writes:
> Add Xen interface header files. These are taken fairly directly from
> the Xen tree and hence the style is not entirely in accordance with
> Linux guidelines. There is a tension between fitting with Linux coding
> rules and ease of maintenance.
>
>
Eric W. Biederman wrote:
> Jeremy Fitzhardinge <[EMAIL PROTECTED]> writes:
>
> There need to be alignment directives for the page aligned chunks.
>
OK.
> Placing the page aligned chunks in a special section is nice in that
> it ensures the linker packs everything tightly but should be
> comple
Jeremy Fitzhardinge <[EMAIL PROTECTED]> writes:
> +++ b/drivers/xen/Kconfig.net
> @@ -0,0 +1,14 @@
> +menu "Xen network device drivers"
> +depends on NETDEVICES && XEN
> +
> +config XEN_NETDEV_FRONTEND
> + tristate "Network-device frontend driver"
> + depends on XEN
> + default
Eric W. Biederman wrote:
> Well I did a little by hand parsing and the not I parsed looked ok.
>
> How does the output differ from a what you get when xen-head.S is
> included?
>
Ah!
The .notes section gets SHT_NOTE in vmlinux when xen-head.S is included;
PROGBITS when linked. I tried putting
On Tue, 13 Feb 2007, Ingo Molnar wrote:
>
> the core syslet / async system calls infrastructure code.
Ok, having now looked at it more, I can say:
- I hate it.
I dislike it intensely, because it's so _close_ to being usable. But the
programming interface looks absolutely horrid for any "cas
Over the last few years, page replacement problems in the Linux VM
have been getting resolved as they cropped up, but sometimes the same
kind of bug has been getting fixed and reincroduced over and over
again.
This has convinced me that it is time to take a look at the actual
requirements of a pa
On Wed, Feb 14, 2007 at 12:14:29PM -0800, Davide Libenzi wrote:
> I think you may have mis-interpreted my words. *When* a schedule would
> block a synco execution try, then you do have a context switch. Noone
> argue that, and the code is clear. The sys_async_exec thread will block,
> and a newl
Jeremy Fitzhardinge <[EMAIL PROTECTED]> writes:
There need to be alignment directives for the page aligned chunks.
Placing the page aligned chunks in a special section is nice in that
it ensures the linker packs everything tightly but should be
completely unnecessary if the alignment is correct.
James,
Please review and forward upstream. This is a patch I'd previously
submitted, and reworked by [EMAIL PROTECTED] in January.
Not clear if I need to also nag James Smart (who is listed as the
maintainer) for an Acked-by (which I am lead to beleive should be
forthcoming? Ahh the joys of indi
Linus,
Please pull the hwmon subsystem updates for Linux 2.6.21 from:
git://jdelvare.pck.nerim.net/jdelvare-2.6 hwmon-for-linus
There is one new hardware monitoring driver (adm1029, for the
relatively rare Analog Devices ADM1029 chip), support for one new chip
(Winbond W83627DHG), PWM clock freq
On 02/14, Srivatsa Vaddagiri wrote:
>
> On Wed, Feb 14, 2007 at 08:13:05PM +0530, Gautham R Shenoy wrote:
> > + switch (action) {
> > + case CPU_UP_PREPARE:
> > + /* Create a new workqueue thread for it. */
> > + list_for_each_entry(wq, &workqueues, list) {
>
> Its probably
On 02/14, Gautham R Shenoy wrote:
>
> o Splits CPU_DEAD into two events namely
> - CPU_DEAD: which will be handled while the processes are still
> frozen.
>
> - CPU_DEAD_KILL_THREADS: To be handled after we thaw_processes.
Imho, this is not right. This change the meaning of CPU
On Wed, Feb 14, 2007 at 02:55:46PM -0500, Dave Jones wrote:
> On Wed, Feb 14, 2007 at 05:08:39PM -0200, Marcelo Tosatti wrote:
> >
> > movntq instruction is supported by Geode CPU's, so use
> > fast_clear_page/fast_copy_page versions that have it.
>
> it's supported, but is it a win ?
> The sa
On Wed, 14 Feb 2007, Benjamin LaHaise wrote:
> On Wed, Feb 14, 2007 at 11:45:23AM -0800, Davide Libenzi wrote:
> > Sort of, except that the whole thing can complete syncronously w/out
> > context switches. The real point of the whole fibrils/syslets solution is
> > that kind of optimization. The
101 - 200 of 374 matches
Mail list logo
