Hi,
We're working on a file system checker and have a question regarding what
sys_sync actually does. It appears to us that sys_sync should sync both
data and metadata, and wait until both data and metadata hit the disk
before it returns. Is this true for all the file systems (especially
ext2)
On Fri, Feb 11, 2005 at 01:58:47AM -0500, Dmitry Torokhov wrote:
> This series of patches adds a new "gameport" bus to the driver model.
> It is implemented very similarly to "serio" bus and also allows
> individual drivers to be manually bound/disconnected from a port
> by manipulating port's "dr
On Mon, 2005-02-07 at 15:46 -0800, Andrew Morton wrote:
> Guillaume Thouvenin <[EMAIL PROTECTED]> wrote:
> >
> > Hello,
> >
> >This module sends a signal to one or several processes (in user
> > space) when a fork occurs in the kernel. It relays information about
> > forks (parent and chil
* Matt Mackall <[EMAIL PROTECTED]> wrote:
> > > What happened to the RT rlimit code from Chris?
> >
> > I still have it, but I had the impression Ingo didn't like it as a long
> > term solution/hack (albeit small) to the scheduler. Whereas the rt-lsm
> > patch is wholly self-contained.
>
> I t
On Fri, Feb 11, 2005 at 09:14:22AM +0100, Ingo Molnar wrote:
> an "RT priorities rlimit" is still not adequate as a desktop solution,
> because it still allows the box to be locked up. Also, if it turns out
> to be a mistake then it's already codified into the ABI, while RT-LSM is
> much less 'pers
On Fri, Feb 11, 2005 at 08:54:17AM +0100, Ingo Molnar wrote:
>
> * Matt Mackall <[EMAIL PROTECTED]> wrote:
>
> > Eh? Chris Wright's original rlimits patch was very straightforward
> > [...]
>
> the problem is that it didnt solve the problem (unprivileged user can
> lock up the system) in any way
* Sven Dietrich <[EMAIL PROTECTED]> wrote:
> This patch adds a config option to allow you to select whether timer
> IRQ runs in thread or not.
this patch only changes xtime_lock back and forth - it does in no way
impact the 'threadedness' of the timer IRQ. (it does not move the timer
IRQ into an
On Thu, Feb 10, 2005 at 02:24:58PM -0500, Dmitry Torokhov wrote:
> On Thu, 10 Feb 2005 16:44:21 +0100, Stelian Pop <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > Over the last few weeks I've collected a few patches in my tree
> > coming from others and it's time to merge them upstream:
> >
> >
* George Anzinger wrote:
> Possibly from:
> define __raw_spin_is_locked(x)(*(volatile signed char *)(&(x)->lock)
> <= 0)
> #define __raw_spin_unlock_wait(x) \
> do { barrier(); } while(__spin_is_locked(x))
> in asm/spinlock.h
>
> should that be __raw_spin_is_locked(x) instead?
y
On Thu, Feb 10, 2005 at 08:34:37PM +0100, d.c wrote:
> El Thu, 10 Feb 2005 00:22:39 +0100 (CET),
> Roman Zippel <[EMAIL PROTECTED]> escribió:
>
> > To remind you the main problem was and is still, that the kernel history
> > is locked into bk. At this point I'm not really sure, whether all bk us
On Fri, Feb 11, 2005 at 09:14:22AM +0100, Ingo Molnar wrote:
>
> > I think it's important to recognize that we're trying to address an
> > issue that has a much wider potential audience than pro audio users,
> > and not very far off - what is high end audio performance today will
> > be expected d
* Matt Mackall <[EMAIL PROTECTED]> wrote:
> Here's Chris' patch for reference:
>
> http://groups-beta.google.com/group/linux.kernel/msg/6408569e13ed6e80
how does this patch solve the separation of 'negative nice values' and
'RT priority rlimits'? In one piece of code it handles the rlimit value
[Posted only on LKML, this has become humour.]
On Thu, Feb 10, 2005 at 09:03:00PM +0100, David Weinehall wrote:
> On Thu, Feb 10, 2005 at 04:21:49PM +0100, Ingo Molnar wrote:
> >
> > * Jakob Oestergaard <[EMAIL PROTECTED]> wrote:
> > > > PaX cannot be a 'little bit pregnant'. (you might argue t
On Fri, Feb 11, 2005 at 07:23:09AM +, Hugh Dickins wrote:
> And it's fine for the behaviour to be somewhat undefined in this
> peculiar case: the important thing is just that the page must not
> be freed and reused while I/O occurs, hence get_user_page raising
> the page_count - which I'm _not_
Guillaume Thouvenin <[EMAIL PROTECTED]> wrote:
>
> On Mon, 2005-02-07 at 15:46 -0800, Andrew Morton wrote:
> > Guillaume Thouvenin <[EMAIL PROTECTED]> wrote:
> > >
> > > Hello,
> > >
> > >This module sends a signal to one or several processes (in user
> > > space) when a fork occurs in the k
On Fri, Feb 11, 2005 at 09:48:43AM +0100, Ingo Molnar wrote:
>
> * Matt Mackall <[EMAIL PROTECTED]> wrote:
>
> > Here's Chris' patch for reference:
> >
> > http://groups-beta.google.com/group/linux.kernel/msg/6408569e13ed6e80
>
> how does this patch solve the separation of 'negative nice values
* Matt Mackall <[EMAIL PROTECTED]> wrote:
> > i disagree that desktop performance tomorrow will necessarily have to
> > utilize SCHED_FIFO. Today's desktop audio applications perform quite
> > good at SCHED_NORMAL priorities [with the 2.6.11 kernel that has more
> > interactivity/latency fixes su
hoi :)
I wanted to experiment with different docbook processors to speed up
documentation generation. Well, I haven't found a better way yet but
as a side-effect I now have a patch that moves all DocBook templates
to valid XML DocBook.
Please do a
bk pull bk://tali.bkbits.net/linux-doc
On Thu, Feb 10, 2005 at 01:17:00PM -0800, Larry McVoy wrote:
> So if we knew that doing this would hurt our business, which according
> you is the only thing we care about, then why would we do it? The usual
> response is the marketing value we get out of it. Yes, we certainly do
> get some posi
* Matt Mackall <[EMAIL PROTECTED]> wrote:
> Read more closely: there are two independent limits in the patch,
> RLIMIT_NICE and RLIMIT_RTPRIO. This lets us grant elevated nice
> without SCHED_FIFO.
ok, indeed.
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel
Hello,
I am running on a uniprocessor x86 with CONFIG_SMP disabled and
CONFIG_PREEMPT enabled.
The problem I have encountered is when using a timer in a module. The
timer is set to execute every 3 ticks, and does nothing but increment
a counter, and that works fine. However, when the module is
* Matt Mackall <[EMAIL PROTECTED]> wrote:
> So the comparison boils down to putting a magic gid in a sysfs
> file/module parameter or setting an rlimit with standard tools (PAM,
> etc). I'm really boggled that anyone could prefer the former,
> especially since we had almost this exact debate over
On Thu, Feb 10, 2005 at 08:39:37PM +0100, Bruno Ducrot wrote:
> On Thu, Feb 10, 2005 at 05:18:10PM +0100, Stelian Pop wrote:
> > Hi,
> >
> > +ACPI Sony Notebook Control Driver (SNC) Readme
> > +--
> > + Copyright (C) 2004 Stelian Pop <[EMAIL PROTECTED
Am Freitag, 21. Januar 2005 07:15 schrieb Klaus Muth:
> Every now and then (maybe twice a week) my server panics. [...]
> Any help will be appreciated.
Did help myself. Seems to work.
> ksymoops 2.4.5 on i686 2.4.26-msi1. Options used
Updated to 2.4.29, keeping my kernel config. No panic since
[ For those who have already reached a conclusion on this
subject, there is little that is new below. It's just
cast in a different light, as an analysis of how well
the CKRM cpuset/memset task class that Chandra describes
meets the needs of cpusets. The conclusion is: not well.
A pic
On Fri, Feb 11, 2005 at 10:04:19AM +0100, Ingo Molnar wrote:
>
> * Matt Mackall <[EMAIL PROTECTED]> wrote:
>
> > So the comparison boils down to putting a magic gid in a sysfs
> > file/module parameter or setting an rlimit with standard tools (PAM,
> > etc). I'm really boggled that anyone could p
Adrian Bunk wrote:
I didn't find any way how the drivers/media/dvb/frontends/at76c651.c
driver would do anything inside kernel 2.6.11-rc3-mm2. All it does is to
EXPORT_SYMBOL a function at76c651_attach that isn't used anywhere.
Is a patch to remove this driver OK or did I miss anything?
no, p
No, this is not in arm. Here is the patch.
Index: linux-2.6.10/include/asm-i386/spinlock.h
===
--- linux-2.6.10.orig/include/asm-i386/spinlock.h 2005-02-11
09:25:39.224240321 +
+++ linux-2.6.10/include/asm-i386/spinlock.h
On Fri, Feb 11, 2005 at 09:59:42AM +0100, Ingo Molnar wrote:
>
> think of SCHED_FIFO on the desktop as an ugly wart, a hammer, that
> destroys the careful balance of priorities of SCHED_OTHER tasks. Yes, it
> can be useful if you _need_ a scheduling guarantee due to physical
> constraints, and it
* Sven Dietrich <[EMAIL PROTECTED]> wrote:
> No, this is not in arm. Here is the patch.
>
> Index: linux-2.6.10/include/asm-i386/spinlock.h
what version do you have? The current released patch is
2.6.11-rc3-V0.7.38-10.
Ingo
-
To unsubscribe from this list: send the line "unsubscribe li
On Fri, Feb 11, 2005 at 02:11:17AM +0100, Mws wrote:
> FYI
>
> The atmel at76c651 frontend driver is used for the
> Sagem DBox2 Digital Cable Receiver.
>
> As all other parts of the dbox2 drivers are atm not hosted at kernel cvs but
> at
> cvs.tuxbox.org you won't find any components in mainl
Ingo wrote:
>
> * Sven Dietrich <[EMAIL PROTECTED]> wrote:
>
> > This patch adds a config option to allow you to select
> whether timer
> > IRQ runs in thread or not.
>
> this patch only changes xtime_lock back and forth - it does
> in no way impact the 'threadedness' of the timer IRQ. (it
On Thu, Feb 10, 2005 at 04:40:33PM -0800, Greg KH wrote:
> - autoload programs for usb, scsi, and pci modules. These
> programs determine what module needs to be loaded when the
> kernel emits a hotplug event for these types of devices. This
> works just like the exi
* Matt Mackall <[EMAIL PROTECTED]> wrote:
> On Fri, Feb 11, 2005 at 09:59:42AM +0100, Ingo Molnar wrote:
> >
> > think of SCHED_FIFO on the desktop as an ugly wart, a hammer, that
> > destroys the careful balance of priorities of SCHED_OTHER tasks. Yes, it
> > can be useful if you _need_ a sched
* Sven Dietrich <[EMAIL PROTECTED]> wrote:
> > this patch only changes xtime_lock back and forth - it does
> > in no way impact the 'threadedness' of the timer IRQ. (it
> > does not move the timer IRQ into an interrupt thread.)
> >
> > nor do we really want to make it configurable - it's
> >
Junfeng Yang <[EMAIL PROTECTED]> wrote:
>
>
> Hi,
>
> We're working on a file system checker and have a question regarding what
> sys_sync actually does. It appears to us that sys_sync should sync both
> data and metadata, and wait until both data and metadata hit the disk
> before it returns.
On Thu, 2005-02-10 at 16:11 -0800, Pete Zaitcev wrote:
> I entered a patch which adds "exclusive_access" lock into 2.4.29, to fix
> devices which cannot handle simultaneous accesses. This caused a regression
> with European ADSL modems. An ioctl USBDEVFS_REAPURB allows a process to enter
> the kern
Hi Stelian, all,
This driver has been submitted (almost unchanged) on lkml and
on acpi-devel twice, first on July 21, 2004, then again on
September 17, 2004. It has been quietly ignored.
Privately I've had many positive feedbacks from users of this driver
(and no negative feedback), including Lin
Err. I'm stupid. This isn't a bug.
On Fri, 11 Feb 2005 02:09:10 -0700, Tipp Moseley <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I am running on a uniprocessor x86 with CONFIG_SMP disabled and
> CONFIG_PREEMPT enabled.
>
> The problem I have encountered is when using a timer in a module. The
>
On Thu, 2005-02-10 at 16:39 -0200, Marcelo Tosatti wrote:
> What do you mean "adds another incompatibility" ?
>
> That users will have to switch to dmraid when upgrading to v2.6.x ?
which is a rather disruptive and incompatible change. device names
change etc etc.
> SATA is not the same case
On Thu, 10 Feb 2005 17:18:10 +0100, Stelian Pop <[EMAIL PROTECTED]> wrote:
> +static int sony_acpi_write_brt(struct file *file, const char __user *buffer,
> unsigned long count, void *data)
> +{
> + struct sony_snc *snc = (struct sony_snc *) data;
The casts for void pointer conversiosn are
On Fri, Feb 11, 2005 at 11:30:35AM +0100, Jean Delvare wrote:
> Hi Stelian, all,
>
> >This driver has been submitted (almost unchanged) on lkml and
> >on acpi-devel twice, first on July 21, 2004, then again on
> >September 17, 2004. It has been quietly ignored.
> >
> >Privately I've had many pos
On Thu, Feb 10, 2005 at 05:31:05PM +, Daniel K. wrote:
> > { SONYPI_DEVICE_MODEL_TYPE2, 0x08, SONYPI_HELP_MASK, sonypi_helpev },
> > + { SONYPI_DEVICE_MODEL_TYPE2, 0x21, SONYPI_HELP_MASK, sonypi_helpev },
>
> I suspect you should simply replace the '0x08' line as it was left over
> from
Based on feedback from Jean Delvare and Pekka Enberg, here is an
updated version.
Changes from the previous version include:
- do not initialize to 0 a static variable
- trim to 80 columns
- do not do spurious void * casts
- use c99 style struct initialization
- use simple_strtoul instead of sscan
On Thu, 2005-02-10 at 22:41 -0800, Greg KH wrote:
> On Fri, 2005-02-11 at 02:30 +0100, Kasper Sandberg wrote:
> > hey greg
> >
> > i remember for some months back, you posted something similar.. is this
> > a version thats ready for use? if it is! im gonna use it! :D
>
> Yes, this is that version
On Fri, 11 Feb 2005 12:36:37 +0100, Stelian Pop <[EMAIL PROTECTED]> wrote:
> +static int __init sony_acpi_add(struct acpi_device *device)
> +{
> + acpi_status status = AE_OK;
> + struct sony_snc *snc = NULL;
> + int result;
> +
> + snc = kmalloc(sizeof(struct sony_snc), GFP_
On Fri, 2005-02-11 at 10:36 +0100, Holger Waechtler wrote:
> Adrian Bunk wrote:
>
> >I didn't find any way how the drivers/media/dvb/frontends/at76c651.c
> >driver would do anything inside kernel 2.6.11-rc3-mm2. All it does is to
> >EXPORT_SYMBOL a function at76c651_attach that isn't used anywhe
On Fri, 2005-02-11 at 10:49 +0100, Adrian Bunk wrote:
> If I understand it correctly, there are several drivers that only make
> sense if they are used together. at76c651.c alone makes zero sense?
> This means it would be highly appreciated to have all parts inside the
> kernel at some time in th
On Fri, 2005-02-11 at 00:54 -0800, Andrew Morton wrote:
> > I tested this patch on a 2.6.11-rc3-mm2 kernel and there is a little
> > overhead when I compile a Linux kernel:
> >
> >#time sh -c 'make O=/home/guill/build/k2610 bzImage &&
> >make O=/home/guill/build/k2610 modules'
> >
> >
Junfeng Yang <[EMAIL PROTECTED]> writes:
> We're working on a file system checker and have a question regarding what
> sys_sync actually does. It appears to us that sys_sync should sync both
> data and metadata, and wait until both data and metadata hit the disk
> before it returns. Is this true
Hi,
On Thu, 10 Feb 2005 23:59:53 -0800 (PST), Junfeng Yang <[EMAIL PROTECTED]>
wrote:
>
> Hi,
>
> We're working on a file system checker and have a question regarding what
> sys_sync actually does. It appears to us that sys_sync should sync both
> data and metadata, and wait until both data an
On Fri, 11 Feb 2005, Andrea Arcangeli wrote:
>
> Ok, I'm quite convinced it's correct now. The only thing that can make
> mapcount go up without the lock on the page without userspace
> intervention (and userspace intervention would make it an undefined
> behaviour like in my example with fork), w
We are having major problems with the aacraid module under fedora core 2 on
Dell poweredge 2500. These use PERC3/Di controllers.
01:02.1 RAID bus controller: Dell Computer Corporation PowerEdge Expandable
RAID Controller 3 (rev 01)
01:0c.0 SCSI storage controller: Adaptec AHA-3960D / AIC-7899A
This patch adds the output interface control to VR41xx SIU driver.
And obsolete function for VR41xx SIU is removed.
Yoichi
Signed-off-by: Yoichi Yuasa <[EMAIL PROTECTED]>
diff -urN -X dontdiff a-orig/arch/mips/vr41xx/casio-e55/setup.c
a/arch/mips/vr41xx/casio-e55/setup.c
--- a-orig/arch/mips/vr
The attached patch fixes sigaltstack handling for RT signal return. It was
reading a userspace struct into kernel space and then passing the kernel copy
to a generic signalling routine which then assumed it had been passed a
userspace pointer...
Signed-Off-By: David Howells <[EMAIL PROTECTED]>
Si
This patch applies to the kernel 2.6.11-rc3 and removes
excess '~' before the bit masks.
Signed-off-by: Andrei Konovalov <[EMAIL PROTECTED]>
diff -uprN a/drivers/serial/cpm_uart/cpm_uart_cpm2.c
b/drivers/serial/cpm_uart/cpm_uart_cpm2.c
--- a/drivers/serial/cpm_uart/cpm_uart_cpm2.c 2005-02-11 17
Dear Linux Kernel,
We have visited your website spinics.net today , and would like to
request a link exchange between our websites.
You may visit our website at barretire.com. Our website contains
quality automotive content and tools that visitors of your website will
find useful.
Please
"Simon White" <[EMAIL PROTECTED]> writes:
> Hi,
>
> I've been writing a device driver for a piece of hardware that we recently
> found the pci bridge has an issue on software reset (kernel 2.6.8.1, hardware
> reset is fine). The bridge appears to corrupt the subvendor/device ids on
> next boot
On Fri, 2005-02-11 at 00:54 -0800, Andrew Morton wrote:
> > I tested this patch on a 2.6.11-rc3-mm2 kernel and there is a little
> > overhead when I compile a Linux kernel:
> >
> >#time sh -c 'make O=/home/guill/build/k2610 bzImage &&
> >make O=/home/guill/build/k2610 modules'
> >
> >
Port of the Genesys Logic 520SM sensor chip driver from linux 2.4
Signed-off-by: Maarten Deprez <[EMAIL PROTECTED]>
--- linux-2.6.11-rc3-mm2/drivers/i2c/chips/Kconfig.orig 2005-02-11
16:14:12.0 +0100
+++ linux-2.6.11-rc3-mm2/drivers/i2c/chips/Kconfig 2005-02-11
16:14:31.0 +
On Fri, 2005-02-11 at 14:28 +, Jonathan Knight wrote:
>
> We are having major problems with the aacraid module under fedora core 2 on
> Dell poweredge 2500. These use PERC3/Di controllers.
[ ... ]
>
> The systems run fine with no users, but as soon as the disks go under load
> we get the f
On Feb 10, 2005, [EMAIL PROTECTED] (Larry McVoy) wrote:
> It seems like you've made up your mind that we are operating out of pure
> self interest and have no desire to help you or anyone else unless we
> get something out of it. In other words, we're making our decisions
> based on the net posit
On Sun, 2005-01-30 at 20:19 -0500, Parag Warudkar wrote:
> Attached is the reworked patch to take care of Andrew's suggestions -
>
> 1) Allocate the work struct dynamically in struct ti_ohci during device
> probe, free it during device remove
> 2) In ohci1394_pci_remove, ensure queued work, if a
On Fri, Feb 11, 2005 at 01:30:22PM -0200, Alexandre Oliva wrote:
> > Can you offer any plausible explanation other than a good faith desire
> > to help the open source community, albeit in a non-traditional way?
>
> I don't see what you've done as helping the open source community.
So in your m
Hello again,
Thanks for the evtest.c program and the information about evtouch. After the
minor change from LONG(BTN_LEFT) to LONG(BTN_TOUCH), patch below, I
was able to then get touch on/off events. Also I tested this driver with the
"evtouch" Xwindows driver and it worked nicely.
Thanks,
Rick Koc
On Fri, Feb 11, 2005 at 01:01:46PM -0200, Alexandre Oliva wrote:
> I don't believe his claim, and I can prove it with a dumb example.
>
> Consider three patches, A, J and U, such that A and U are identical,
> and J is a patch that reverses them.
>
> You can determine the final state of the tree g
> A number of people have seen problems like this going from 2.4 to 2.6.
> Mark Salyzyn from Adaptec has suggested in those cases to make sure that
> the board firmware is up to date. I've copied Mark on this mail.
We think we're on the latest everything. The BIOS is A07 and the firmware
on the
On Fri, Feb 11, 2005 at 10:50:19AM -0500, Richard Koch wrote:
> Thanks for the evtest.c program and the information about evtouch. After the
> minor change from LONG(BTN_LEFT) to LONG(BTN_TOUCH), patch below, I
> was able to then get touch on/off events. Also I tested this driver with the
> "evtou
On Fri, 11 Feb 2005 07:39:47 -0800 (PST), Alexandre Oliva
<[EMAIL PROTECTED]> wrote:
> The bit I don't understand is that you've claimed you'd be willing to
> implement the code needed to export the additional information that
> Roman, myself and probably many others would like to have, if someone
The mails have started flowing in saying "I don't agree with Alexandre
and please don't pull the plug" so a point of clarification. We have
no intention of shutting down the BK free product. We are aware that
there are 10's of thousands of developers in the open source world
who do not agree with
On Friday 11 February 2005 07:46, Greg KH wrote:
> And finally, even if you do use udevstart to manager /sbin/hotplug
> events, you still need a module autoloader program. This package
> provides executables for that problem, if you don't want to (or you
> can't) use the existing linux-hotplug scr
Dave Jones wrote:
probably you have selected IOMMU, which is dependant on it.
Yes, thanks. Sorry my fault. I had it not deactivated, arggg.
This surprises me, especially considering the in-kernel nvidia-agp driver
was actually written by NVidia. Are there any agp error messages in
your dmesg / X lo
In fs/Kconfig,
See "Documentation/filesystems/fscache.txt for more information." and
"See Documentation/filesystems/cachefs.txt for more information."
Should be changed to:
"See Documentation/filesystems/caching/fscache.txt for more
information." and "See Documentation/filesystems/caching/cachef
Before I'm getting flamed to death:
This patch contains possible cleanups. If parts of this patch conflict
with pending changes these parts of my patch have to be dropped.
This patch contains the following possible cleanups:
- make needlessly global code static
- remove the following EXPORT_SYMBO
Then turn off both read and write cache on the card ...
You should contact Dell Technical support as there are many reasons for
the adapter to fail ranging from bad power supply, cables, drives etc.
Sincerely -- Mark Salyzyn
-Original Message-
From: Jonathan Knight [mailto:[EMAIL PROTECT
This patch removes kernel 2.2 code from pm3fb.{c,h}.
It also removes KERNEL_2_4 and KERNEL_2_5 since all places where this
was used had a
#if (defined KERNEL_2_4) || (defined KERNEL_2_5)
(Yes, I know the driver is marked as BROKEN.)
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
This pa
On Feb 11, 2005, [EMAIL PROTECTED] (Larry McVoy) wrote:
> On Fri, Feb 11, 2005 at 01:30:22PM -0200, Alexandre Oliva wrote:
>> > Can you offer any plausible explanation other than a good faith desire
>> > to help the open source community, albeit in a non-traditional way?
>> I don't see what you'v
On Fri, Feb 11, 2005 at 05:19:22PM +0100, Christian Borntr?ger wrote:
> On Friday 11 February 2005 07:46, Greg KH wrote:
> > And finally, even if you do use udevstart to manager /sbin/hotplug
> > events, you still need a module autoloader program. This package
> > provides executables for that pro
I found some points during schedule when interrupts are off for
long periods . These two patches seem to help. One enables interrupts
inside schedule() , so that interrupts are enabled after each
need-resched loop, then disabled again before __schedule() is called.
The other patch
On Fri, Feb 11, 2005 at 12:47:07PM +0100, Kasper Sandberg wrote:
> On Thu, 2005-02-10 at 22:41 -0800, Greg KH wrote:
> > On Fri, 2005-02-11 at 02:30 +0100, Kasper Sandberg wrote:
> > > hey greg
> > >
> > > i remember for some months back, you posted something similar.. is this
> > > a version that
On Fri, Feb 11, 2005 at 10:52:37AM +0100, Olivier Galibert wrote:
> On Thu, Feb 10, 2005 at 04:40:33PM -0800, Greg KH wrote:
> > - autoload programs for usb, scsi, and pci modules. These
> > programs determine what module needs to be loaded when the
> > kernel emits a hotplug event
On Thu, Feb 10, 2005 at 07:31:14PM +0100, Pavel Machek wrote:
> Try also acpi=off.
i was hoping for a test that's a bit more granular. might it be
possible to disable suspect bits of the acpi code instead of all of it?
i'm open to applying and testing patches.
disabling all of acpi for a week or
On Thursday, February 10, 2005 6:46 pm, Chandra Seetharaman wrote:
> On Wed, Feb 09, 2005 at 09:59:28AM -0800, Chandra Seetharaman wrote:
> > On Tue, Feb 08, 2005 at 12:42:34PM -0800, Paul Jackson wrote:
>
> --stuff deleted---
>
> > memset_controller would be similar to this, before pitching it I w
The core device-mapper multipath and path-selector code.
Paths are grouped into an ordered list of Priority Groups.
Each Priority Group has a Path Selector which chooses which
of the Priority Group's paths is to be used for each bio
e.g. according to some load-balancing algorithm.
If a bio genera
Each multipath instance can use a Hardware Handler with
hooks for the particular hardware you're using.
This patch provides the hw_handler infrastructure.
So far 3 hooks are available:
A status function invoked by device-mapper table and
status requests.
An initialisation function called
A very basic path selector: round-robin.
It uses in turn each path that has not been disabled.
By default, it instructs core multipath to use each path it supplies
for 1000 bios, but a different repeat_count can be set against
any path to provide primitive load-balancing across unequal paths.
Si
On Feb 11, 2005, Jon Smirl <[EMAIL PROTECTED]> wrote:
> It's not Larry choosing not to have you do the work, you are self
> selecting not to do it because you won't sign the contracts.
No. We don't want access to the BK software. We want access to the
data that is stored in the repository, that
MailEnable: MailEnable Message Scan intercepted the delivery of this message.
Reason: (Allegato non permesso per questioni di sicurezza
)
Message headers follow:
Received: from skill-net.com ([82.57.185.197]) by s2.gestinweb.it with
MailEnable ESMTP; Fri, 11 Feb 2005 18:15:23 +0100
From: linu
Outline Hardware Handler for EMC CLARiiON AX/CX-series.
Signed-Off-By: Alasdair G Kergon <[EMAIL PROTECTED]>
From: Lars Marowsky-Bree <[EMAIL PROTECTED]>
--- diff/drivers/md/Kconfig 2005-02-09 14:41:52.0 +
+++ source/drivers/md/Kconfig 2005-02-09 14:42:24.0 +
@@ -233,
* Daniel Walker <[EMAIL PROTECTED]> wrote:
> I found some points during schedule when interrupts are off
> for long periods . These two patches seem to help. One enables
> interrupts inside schedule() , so that interrupts are enabled after
> each need-resched loop, then disabled again bef
> +#include "dm.h"
> +#include "dm-path-selector.h"
> +
> +#include
private after public again. Also it kinda looks to me like dm headers
pull in far too much kernel headers?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
On Fri, 2005-02-11 at 09:30, Ingo Molnar wrote:
>
> i'm wondering what the best approach would be. Right now if
> DIRECT_PREEMPT is enabled [it's disabled currently] and a higher-prio
> task has been woken up we switch to it without ever enabling interrupts
> again. Re-enabling interrupts during s
> +#include "dm.h"
> +#include "dm-path-selector.h"
> +#include "dm-bio-list.h"
> +#include "dm-bio-record.h"
> +
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
Always include private headers after public ones.
> +MODULE_DESCRI
On Fri, Feb 11, 2005 at 01:07:08AM -0600, Al Borchers wrote:
>
>
> On Thursday 10 February 2005 9:39 am, Nishanth Aravamudan wrote:
> >> It came up on IRC that the wait_cond*() functions from
> >> usb/serial/gadget.c could be useful in other parts of the kernel. Does
> >> the following patch make
>introduced. See devfs. And I think the adoption barrier thing is a red
>herring as well: the current users are by and large compiling their
>own RT-tuned kernels.
not true. most people are using kernels built for specialized distros
or addons, such as CCRMA, Demudi, Ubuntu, or dyne:bolic.
--p
-
On Feb 11, 2005, [EMAIL PROTECTED] (Larry McVoy) wrote:
> You are also right that figuring out the merges is a pain. So what?
> We never said that we'd figure out how to do all this well and then
> teach you how to do it well.
We're not asking for you to teach us how to do it. We're just aski
* Matt Mackall <[EMAIL PROTECTED]> wrote:
> > > Yes. There's also the whole soft limit thing.
> >
> > i'm curious, how does this 'per-app' rlimit thing work? If a user has
> > jackd installed and runs it from X unprivileged, how does it get the
> > elevated rlimit?
>
> It needs a setuid launche
On Fri, Feb 11, 2005 at 10:53:27AM +0100, Ingo Molnar wrote:
>
> * Matt Mackall <[EMAIL PROTECTED]> wrote:
>
> > On Fri, Feb 11, 2005 at 09:59:42AM +0100, Ingo Molnar wrote:
> > >
> > > think of SCHED_FIFO on the desktop as an ugly wart, a hammer, that
> > > destroys the careful balance of prior
>RT-LSM introduces architectural problems in the form of bogus API. And
that may be true of LSM, but not RT-LSM in particular. RT-LSM doesn't
introduce *any* API whatsoever - it simply allows software to call
various existing APIs (mostly from POSIX) and have them not fail as
result of not being r
> > This surprises me, especially considering the in-kernel nvidia-agp driver
> > was actually written by NVidia. Are there any agp error messages in
> > your dmesg / X log ?
> With the nVidia own nv_agp it appears directly in all apps, very fast
> under GNOME 2.8.1. Why, I do not know. Also gam
1 - 100 of 218 matches
Mail list logo
