If want to write a loadable module which "implements" a char device
("virtual", no real device present). How do I get the correct
"/dev/foo" to appear automaticly? What is the current recommended
solution (kernel 2.6.17 in Ubuntu and later).
static int major;
static int __init foo_init(void)
Aubrey Li wrote:
> On 1/25/07, Vaidyanathan Srinivasan <[EMAIL PROTECTED]> wrote:
>>
>> Christoph Lameter wrote:
>>> On Wed, 24 Jan 2007, Vaidyanathan Srinivasan wrote:
>>>
With your patch, MMAP of a file that will cross the pagecache limit hangs
the
system. As I mentioned in my
On Thu, Jan 25, 2007 at 03:25:29PM +1100, Nick Piggin wrote:
> David Chinner wrote:
> >On Thu, Jan 25, 2007 at 01:01:09PM +1100, Nick Piggin wrote:
> >
> >>David Chinner wrote:
>
> >>>No. The only thing that will happen here is that the direct read
> >>>will see _none_ of the write because the
Vladimir V. Saveliev wrote:
Hello
On Tuesday 23 January 2007 10:38, Vince wrote:
[...]
I don't know if it is related, but I've had the following BUG on
2.6.20-rc4-mm1 (+ hot-fixes patches applied) :
---
kernel BUG at fs/reiser4/plugin/item/extent_file_ops.c:973!
This is
Hi Pierre,
> HEAD has this fixed. Every spec I can get my hands on states that R1 and
> R6 have the same format. So it sounds like this controller is doing
> something stupid.
Apparently my HW is broken... I got a hold of a DB1200 demoboard and
the distributed version works fine there.
I'm very
On Thu, 25 Jan 2007, Aubrey Li wrote:
> But Vaidy - even with your patch, we are still using the existing
> reclaimer, that means we dont ensure that only page cache is
> reclaimed/limited. mapped pages will be hit also.
> I think we still need to add a new scancontrol field to lock mmaped
>
Dmitriy Monakhov <[EMAIL PROTECTED]> writes:
> Move common segments checks from __generic_file_aio_{read,write}_nolock()
> to separate helper function generic_segment_checks().
WOW my eyes
I'm realy sorry but this patch is litle bit broken. :(
I've forgot to check generic_segment_checks()
Rik van Riel wrote:
> Christoph Lameter wrote:
> > This is a patch using some of Aubrey's work plugging it in what is IMHO
> > the right way. Feel free to improve on it. I have gotten repeatedly
> > requests to be able to limit the pagecache.
>
> IMHO it's a bad hack.
>
> It would be better to
Hi, Kristian:
I only looked briefly at SBP-2, and at submit/callback paths it pulled,
because I do not understand most of the other issues.
Executive summary: please implement proper ORB cancellation. This is
how you verify that your locking model is worth anything: by interaction
of normal
* Daniel Walker <[EMAIL PROTECTED]> wrote:
> > Thomas' changes are more obviously purpose driven, and Daniel's
> > appear more like just cleanups. So given that, if it were me, I'd
> > put Thomas changes in first, and re-diff Daniel's non-redundant
> > changes on top.
>
> Seems backwards ,
On 1/25/07, Vaidyanathan Srinivasan <[EMAIL PROTECTED]> wrote:
Christoph Lameter wrote:
> On Wed, 24 Jan 2007, Vaidyanathan Srinivasan wrote:
>
>> With your patch, MMAP of a file that will cross the pagecache limit hangs the
>> system. As I mentioned in my previous mail, without subtracting
* john stultz <[EMAIL PROTECTED]> wrote:
> Although, to be fair, I do know that Daniel has future sched_clock
> related patches that need his cleanups [...]
btw., i dont find those sched_clock() changes really acceptable in their
present form, and i've pointed out my reasons for that in the
@@ -241,9 +241,9 @@ void radeonfb_engine_reset(struct radeon
INREG(HOST_PATH_CNTL);
OUTREG(HOST_PATH_CNTL, host_path_cntl);
- if (rinfo->family != CHIP_FAMILY_R300 ||
- rinfo->family != CHIP_FAMILY_R350 ||
- rinfo->family != CHIP_FAMILY_RV350)
+ if
Erik Andersen wrote:
On Sat Dec 16, 2006 at 01:42:11PM -0500, Mike Frysinger wrote:
On 11/30/06, Robert P. J. Day <[EMAIL PROTECTED]> wrote:
but there are a few other
cases which still contain compound preprocessor directives such as:
#if defined(__KERNEL__) || !defined(__GLIBC__) ||
* Daniel Walker <[EMAIL PROTECTED]> wrote:
> Only in so much as the high res changes parallel my own. That includes
> from my set the update_callback removal and the rating sorted list.
> thats about where the similarity stops, even those changes don't
> appear to have the breath of mine.
On Thu, 25 Jan 2007 00:40:54 -0500
Rik van Riel <[EMAIL PROTECTED]> wrote:
> KAMEZAWA Hiroyuki wrote:
> > On Wed, 24 Jan 2007 23:28:15 -0500
> > Rik van Riel <[EMAIL PROTECTED]> wrote:
> >
> >> KAMEZAWA Hiroyuki wrote:
> > I always says Linux is different from mainframes.
>
> It's not just
Rik van Riel wrote:
> Vaidyanathan Srinivasan wrote:
>
>> In my opinion, once a
>> file page is mapped by the process, then it should be treated at par
>> with anon pages. Application programs generally do not mmap a file
>> page if the reuse for the content is very low.
>
> Why not have the
KAMEZAWA Hiroyuki wrote:
On Wed, 24 Jan 2007 23:28:15 -0500
Rik van Riel <[EMAIL PROTECTED]> wrote:
KAMEZAWA Hiroyuki wrote:
FYI:
Because some customers are migrated from mainframes, they want to control
almost all features in OS, IOW, designing memory usages.
Don't you mean:
"Because some
On Wed, Jan 24, 2007 at 12:11:30PM +0100, S?bastien Dugu? wrote:
> > > + if (unlikely(!notify->sigq))
> > > + return -EAGAIN;
> >
> > Did this just leak a ref on the task_struct?
> >
>
> No, the ref is released in really_put_req() when we dispose of
> the iocb.
And the code really
Running 2.6.20-rc4 _WITH_ the following patch: (Shouldn't be the issue,
but just in case, I'm listing it here)
Date: Fri, 29 Dec 2006 21:03:57 +0100
From: Ingo Molnar <[EMAIL PROTECTED]>
Subject: [patch] remove MAX_ARG_PAGES
Message-ID: <[EMAIL PROTECTED]>
Linux fileserver 2.6.20-rc4MAX_ARGS
On 1/25/07, Eamonn Hamilton <[EMAIL PROTECTED]> wrote:
I've also just found bug #7820 on bugzilla which has a patch which may
address this issue from Ingo.
I'll give that a shot as well.
Yes, that patch workaround the problem. But it is just a workaround.
It would be much helpful to others
On Wed, 24 Jan 2007 23:28:15 -0500
Rik van Riel <[EMAIL PROTECTED]> wrote:
> KAMEZAWA Hiroyuki wrote:
>
> > FYI:
> > Because some customers are migrated from mainframes, they want to control
> > almost all features in OS, IOW, designing memory usages.
>
> Don't you mean:
>
> "Because some
One more... (sorry about the dribs-and-drabs approach)
NeilBrown
### Comments for Changeset
raid5_mergeable_bvec tries to ensure that raid5 never sees a read
request that does not fit within just one chunk. However as we
must always accept a single-page read, that is not always possible.
So
(Please CC me on replies, I'm not subscribed to LKML or the SPI list. Thanks.)
The SD/MMC SPI-based protocol isn't really duplex. In the
normal case there's either information transmitted or received,
not both simultaneously. The unused data is always 0xff; ones.
Unfortunately, the SPI
(Please CC me on replies, I'm not subscribed to LKML. Thanks.)
First, a small bug-fix for spi_bitbang: it must always call the
setup_transfer function via the overridable pointer, not assume
that its spi_bitbang_setup_transfer is sufficient. Otherwise,
if all options in the transfers are
On Wednesday 24 January 2007 17:52, Adrian Bunk wrote:
> On Wed, Jan 24, 2007 at 11:46:44PM +0100, Paweł Sikora wrote:
> > for 2.6.20rc5 i get an acpi related oops during x86-64 boot:
> > http://minus.ds14.agh.edu.pl/~pluto/2.6.20rc5-acpi-oops.jpg
> > disabling the "amd-k8 cool'n'quiet" option in
(Please CC me on replies, I'm not subscribed to LKML or the SPI list. Thanks.)
I'd like to assign NULL to kfree()d members of a structure. I
can't do that without ugly casting (see the PXA patch) when the
structure pointed to is const-qualified. I don't really see a
reason why the cleanup
In 2.6.19, support for splitting driver suspend and resume callbacks
into interrupt and non-interrupt contexts was added. Unfortunately, this
broke /sys/device/.../power/state support for all devices. In the long
run, this should be obsoleted by power management support in the
individual
(Please CC me on replies, I'm not subscribed to LKML. Thanks.)
Five SPI-related patches follow.
1: bugfix for spi_bitbang: always call the setup_transfer
function via the overridable pointer.
2: Allow clocking SPI with chip-select inactive.
3: Define the bit-value transmitted for SPI
(Please CC me on replies, I'm not subscribed to LKML or the SPI list. Thanks.)
There was a comment in the mmc_spi.c glue driver at
http://www.gossamer-threads.com/lists/linux/kernel/671939#671939>:
+* some cards seemed happier if they were initialized first
+* by
(Please CC me on replies, I'm not subscribed to LKML or the SPI list. Thanks.)
I see no signed-off-by line on
http://www.gossamer-threads.com/lists/linux/kernel/671939#671939>
or the linked message. I hope and believe that's just an
oversight. David Brownell and Mike Lavender, do you know if
Vaidyanathan Srinivasan wrote:
In my opinion, once a
file page is mapped by the process, then it should be treated at par
with anon pages. Application programs generally do not mmap a file
page if the reuse for the content is very low.
Why not have the VM measure this, instead of making wild
From: Trond Myklebust <[EMAIL PROTECTED]>
NFS can handle the case where invalidate_inode_pages2_range() fails, so the
premise behind commit 8258d4a574d3a8c01f0ef68aa26b969398a0e140 is now gone.
Remove the WARN_ON_ONCE() which is causing users grief as we can see from
On Tue, 23 Jan 2007 23:33:29 +0100
Blaisorblade <[EMAIL PROTECTED]> wrote:
> On Tuesday 23 January 2007 14:17, Johannes Stezenbach wrote:
> > On Tue, Jan 23, 2007 at 09:02:30AM +0100, Blaisorblade wrote:
> > > On Monday 22 January 2007 21:13, Johannes Stezenbach wrote:
> > > > I was playing with
KAMEZAWA Hiroyuki wrote:
FYI:
Because some customers are migrated from mainframes, they want to control
almost all features in OS, IOW, designing memory usages.
Don't you mean:
"Because some customers are migrating from mainframes, they are
used to needing to control all features in OS" ?
On Wed, Jan 24, 2007 at 08:50:06PM -0500, Christopher Monty Montgomery wrote:
> This patch was generated against 2.6.20-rc5; it fixes a bug that
> cropped up in a late 2.6.19-mm kernel.
>
> When ALSA's sysfs device creation was converted from using
> class_device_create() to device_create(), the
David Chinner wrote:
On Thu, Jan 25, 2007 at 01:01:09PM +1100, Nick Piggin wrote:
David Chinner wrote:
No. The only thing that will happen here is that the direct read
will see _none_ of the write because the mmap write occurred during
the DIO read to a different set of pages in memory.
Christoph Lameter wrote:
This is a patch using some of Aubrey's work plugging it in what is IMHO
the right way. Feel free to improve on it. I have gotten repeatedly
requests to be able to limit the pagecache.
IMHO it's a bad hack.
It would be better to identify the problem this "feature" is
On Mon, 22 Jan 2007 18:07:51 +0300
Evgeniy Dushistov <[EMAIL PROTECTED]> wrote:
> In blocks reallocation function sometimes does not update some
> of buffer_head::b_blocknr, which may and cause data damage.
>
> Signed-off-by: Evgeniy Dushistov <[EMAIL PROTECTED]>
>
> ---
>
> Index:
Another md patch suitable for 2.6.20.
Thanks,
NeilBrown
### Comments for Changeset
If a GFP_KERNEL allocation is attempted in md while the mddev_lock is
held, it is possible for a deadlock to eventuate.
This happens if the array was marked 'clean', and the memalloc triggers
a write-out to the
Another nfsd patch suitable for 2.6.20...
Thanks,
NeilBrown
### Comments for Changeset
nfsd defines a type 'encode_dent_fn' which is much like 'filldir_t'
except that the first pointer is 'struct readdir_cd *' rather than
'void *'. It then casts encode_dent_fn points to 'filldir_t' as
needed.
Christoph Lameter wrote:
> On Wed, 24 Jan 2007, Vaidyanathan Srinivasan wrote:
>
>> With your patch, MMAP of a file that will cross the pagecache limit hangs the
>> system. As I mentioned in my previous mail, without subtracting the
>> NR_FILE_MAPPED, the reclaim will infinitely try and fail.
Eventually we may bundle ACPI/PNP/PNPACPI, so the #else !CONFIG_PNPACPI part
here can go away.
Acked-by: Len Brown <[EMAIL PROTECTED]>
On Friday 05 January 2007 13:03, David Brownell wrote:
> Update ACPI to export its RTC extension information through platform_data
> to the PNPACPI or platform
On Thu, Jan 25, 2007 at 01:01:09PM +1100, Nick Piggin wrote:
> David Chinner wrote:
> >On Thu, Jan 25, 2007 at 11:47:24AM +1100, Nick Piggin wrote:
> >
> >>David Chinner wrote:
> >>
> >>>On Thu, Jan 25, 2007 at 11:12:41AM +1100, Nick Piggin wrote:
> >>But I'm just interested about DIO reads. I
Hi,
recently I got my hands on an ASUS A8Js notebook (Core 2 Duo T7200,
Intel 945 PM PCI-E Chipset, for details see attached log). After booting
the latest 2.6.20-rc5-git3 kernel (but the same behaviour occurs also with
the 2.6.19.2, didn't try any other), some strange behaviour can be
On Thu, 25 Jan 2007, Martin Drab wrote:
> All of this is clearly reproducible. I do not know whether this behaviour
> is somehow related to the ACPI detection problems stated at the beginning
> of the mail, or whether these are two different bugs. That's why I haven't
> reported it to bugzilla
> -Original Message-
> From: James Bottomley [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 24, 2007 9:00 AM
> To: Ed Lin
> Cc: linux-scsi; linux-kernel; jeff; Promise_Linux
> Subject: Re: [patch] scsi: use lock per host instead of per
> device forshared queue tag host
>
...
>
On Wed, 24 Jan 2007 18:41:27 -0800 (PST)
Christoph Lameter <[EMAIL PROTECTED]> wrote:
> > But I can't think of the way to show that.
> > ==
> > [EMAIL PROTECTED] src]$ free
> > total used free sharedbuffers cached
> > Mem:741604 724628 16976
> -Original Message-
> From: David Somayajulu [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 24, 2007 5:03 PM
> To: Ed Lin; Michael Reed
> Cc: linux-scsi; linux-kernel; james.Bottomley; jeff;
> Promise_Linux; Jens Axboe
> Subject: RE: [patch] scsi: use lock per host instead of
On Thu, 2007-01-25 at 00:50 +0100, Jan Engelhardt wrote:
> Hello list,
>
>
> I just don't know where else I could send this, it's sooo generic to
> Linux and UNIX (perhaps blame SUN for inventing portmap?)
> Well, here goes...
>
> As we all know, mountd and other SUNRPC (I question this
On Jan 24, 2007, at 5:45 PM, Chris Rankin wrote:
--- Mark Rustad <[EMAIL PROTECTED]> wrote:
Exactly. Halting use of a version of the kernel based on a single
incident provides no insight to the source of the problem. It could
be anything...
There is a world of difference between a polite
It's been more than a week since -rc5, but I blame everybody (including
me) being away for Linux.conf.au and then me waiting for a few days
afterwards to let everybody sync up.
So there it is, -rc6, hopefully the last -rc of the series.
I'd like everybody to take a really good look at any
Greg KH <[EMAIL PROTECTED]> writes:
> Or you can try it with any of the subsystems that have already been
> converted over to use the struct device code, like misc, mem, and many
> others. Just look for the symlinks in /sys/class/CLASS_NAME/ instead of
> real subdirectories.
>
> So I'd really
On Wed, 24 Jan 2007, Erik Andersen wrote:
> It would be far more useful if an application could hint to the
> pagecache as to which files are and which files as not worth
> caching, especially when the application knows a priori that data
> from a particular file will or will not ever be reused.
On Thu, 25 Jan 2007, KAMEZAWA Hiroyuki wrote:
> On Wed, 24 Jan 2007 14:15:10 +0900
> KAMEZAWA Hiroyuki <[EMAIL PROTECTED]> wrote:
>
> > And...some customers want to keep memory Free as much as possible.
> > 99% memory usage makes insecure them ;)
> >
> If there is a way that the "free"
I'm having two unexpected problems with LFS LiveCDs 6.2-3 and 6.2-4
that don't occure on lfslivecd-x86-6.1.1-4.iso. I've got a workaround
for the second problem but haven't found a solution yet for the second;
see 2. below.
1. The first is that I need to add a symbolic pointer from stage
to
On 1/24/07, Peter Zijlstra <[EMAIL PROTECTED]> wrote:
On Wed, 2007-01-24 at 22:22 +0800, Aubrey Li wrote:
> On 1/24/07, Peter Zijlstra <[EMAIL PROTECTED]> wrote:
> > On Tue, 2007-01-23 at 16:49 -0800, Christoph Lameter wrote:
> > > This is a patch using some of Aubrey's work plugging it in what
This patch adds an optional preemption kernel thread to the rcutorture
tests. This thread sets itself to a low RT priority and chews up
CPU in 10-second bursts, verifying that grace periods progress during
this 10-second interval. This has thus far passed about 30 hours of
RCU torture testing on
On Wed, Jan 24, 2007 at 04:12:18PM -0800, Tim Bird wrote:
> This patch provides a config option for preset lpj, which means
> the value can be easily preserved, and conveyed between developers
> in a config file.
>
This seems excessive, it's already possible to set the preset lpj on the
kernel
On Wed, 2007-01-24 at 19:30 -0500, Kristian Høgsberg wrote:
> The problem isn't packets that are too big, the problem is we can get
> unexpected / too many empty packets, which will then cause the DMA
> engine to move on to the next descriptor before the payload buffer has
> been completely
Here is the priority-boosting piece of the set. Very similar to the
earlier patch (http://lkml.org/lkml/2007/01/15/219).
Signed-off-by: Paul E. McKenney <[EMAIL PROTECTED]>
---
include/linux/init_task.h | 12 +
include/linux/rcupdate.h | 12 +
include/linux/rcupreempt.h | 19 +
Hello!
This is an update of the patch at http://lkml.org/lkml/2007/01/15/219.
This series contains (1) the RCU-boost patch itself and (2) some
rcutorture modifications to test it more thoroughly. This version is
getting quite close.
There is still no OOM tie-in. As before, dynamic adjustment
Often, it is useful to preserve the preset loops_per_jiffy
value for a machine in a config option. Right now, you can
specify a preset lpj value on the kernel command line. But this
means the value is preserved in the firmware, which is less
portable between developers.
This patch provides a
David Chinner wrote:
On Thu, Jan 25, 2007 at 11:47:24AM +1100, Nick Piggin wrote:
David Chinner wrote:
On Thu, Jan 25, 2007 at 11:12:41AM +1100, Nick Piggin wrote:
... so surely if you do a direct read followed by a buffered read,
you should *not* get the same data if there has been some
On Thu, Jan 25, 2007 at 11:47:24AM +1100, Nick Piggin wrote:
> David Chinner wrote:
> >On Thu, Jan 25, 2007 at 11:12:41AM +1100, Nick Piggin wrote:
>
> >>... so surely if you do a direct read followed by a buffered read,
> >>you should *not* get the same data if there has been some activity
>
On Wednesday 24 January 2007 4:03 pm, Oleg Verych wrote:
> Let me propose you to test this as solution, that need no awk, only shell:
Actually awk is one of the standard Single Unix Specification (version 3)
utilities and the kernel build uses it in a number of places, such as
This patch was generated against 2.6.20-rc5; it fixes a bug that
cropped up in a late 2.6.19-mm kernel.
When ALSA's sysfs device creation was converted from using
class_device_create() to device_create(), the fourth param from
class_device_create() [dev] was simply plugged into arg 2 of
Hello,
I would like to know what version of the kernel will||had embed(ed) the
r1000 driver.
Would you know?
Thank you.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Alan wrote:
This is quick rework of the patch Uwe proposed but using Kconfig not
ifdefs and user selection to sort out PATA support. Instead of ifdefs and
requiring the user to select both drivers the SATA driver selects the
PATA one.
For neatness I've also moved the extern into the function
Justin Piszcz wrote:
On Mon, 22 Jan 2007, Andrew Morton wrote:
On Sun, 21 Jan 2007 14:27:34 -0500 (EST) Justin Piszcz <[EMAIL PROTECTED]>
wrote:
Why does copying an 18GB on a 74GB raptor raid1 cause the kernel to invoke
the OOM killer and kill all of my processes?
Running with
On Thu, Jan 25, 2007 at 12:15:51PM +1100, Gordon Stanton wrote:
> Hi,
> I noticed that a common motherboard manufacturer Micro-Star was
> missing it's PCI_VENDOR_ID and so I have sent this patch in.
> Later on I will send a patch to pci/quirks.c to unhide the SMBus on
> the M510C laptop once I
Hi,
I noticed that a common motherboard manufacturer Micro-Star was
missing it's PCI_VENDOR_ID and so I have sent this patch in.
Later on I will send a patch to pci/quirks.c to unhide the SMBus on
the M510C laptop once I have investigated it a bit more. It hides the
SMBus the same as ASUS (and a
Ananth N Mavinakayanahalli wrote:
[snip]
>>> I get this warning:
>>>
>>> kernel/kprobes.c: In function ‘collect_garbage_slots’:
>>> kernel/kprobes.c:215: warning: comparison is always false due to limited
>>> range of data type
>>>
>>> when building 2.6.20-rc5 on powerpc. Not strange though, since
> It seems another driver(qla4xxx) is also using shared queue tag.
> It is natural to imagine there might be same symptom in that
> driver. But I don't know the driver and have no hardware so I
> can not say anything certain about it.
qla4xxx implements slightly differently, in the sense we don't
On Wed, Jan 24, 2007 at 11:45:57PM +, Chris Rankin wrote:
>
> There is a world of difference between a polite request for more information
> (although I gave you
> everything I had), and fobbing someone off with a story about cosmic rays.
>
Chris,
I doubt there was a single version of
On Thu, 25 Jan 2007, Pavel Machek wrote:
> Hi!
>
> > > Is it highmem-related? Can you try it with mem=256M?
> >
> > Bad idea, the kernel crashes & burns when I use mem=256, I had to boot
> > 2.6.20-rc5-6 single to get back into my machine, very nasty. Remember I
> > use an onboard graphics
Alan wrote:
When set_mode() changed ->set_mode didn't adapt. This makes the needed
changes and removes the relevant FIXME case.
Signed-off-by: Alan Cox <[EMAIL PROTECTED]>
applied
Please supply a less ambiguous subject line, per
Documentation/SubmittingPatches and
Alan wrote:
Signed-off-by: Alan Cox <[EMAIL PROTECTED]>
diff -u --new-file --recursive --exclude-from /usr/src/exclude
linux.vanilla-2.6.20-rc4-mm1/drivers/ata/pata_cmd64x.c
linux-2.6.20-rc4-mm1/drivers/ata/pata_cmd64x.c
--- linux.vanilla-2.6.20-rc4-mm1/drivers/ata/pata_cmd64x.c
Alan wrote:
Readability/typos etc
Signed-off-by: Alan Cox <[EMAIL PROTECTED]>
applied
-
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
David Chinner wrote:
On Thu, Jan 25, 2007 at 11:12:41AM +1100, Nick Piggin wrote:
... so surely if you do a direct read followed by a buffered read,
you should *not* get the same data if there has been some activity
to modify that part of the file in the meantime (whether that be a
buffered
On Wed, 24 Jan 2007 14:15:10 +0900
KAMEZAWA Hiroyuki <[EMAIL PROTECTED]> wrote:
> And...some customers want to keep memory Free as much as possible.
> 99% memory usage makes insecure them ;)
>
If there is a way that the "free" command can show "never used" memory,
they will not complain ;).
On Tue, 16 Jan 2007 07:15:17 +0100 [EMAIL PROTECTED] wrote:
> [PATCH 01/06]
>
> Defines the auto_tune structure: this is the structure that contains the
> information needed by the adjustment routine for a given tunable.
> Also defines the registration routines.
>
> The fork kernel component
Justin Piszcz wrote:
On Mon, 22 Jan 2007, Andrew Morton wrote:
After the oom-killing, please see if you can free up the ZONE_NORMAL memory
via a few `echo 3 > /proc/sys/vm/drop_caches' commands. See if you can
work out what happened to the missing couple-of-hundred MB from
ZONE_NORMAL.
On Thu, 25 Jan 2007, Pavel Machek wrote:
> Hi!
>
> > > Is it highmem-related? Can you try it with mem=256M?
> >
> > Bad idea, the kernel crashes & burns when I use mem=256, I had to boot
> > 2.6.20-rc5-6 single to get back into my machine, very nasty. Remember I
> > use an onboard graphics
On Wednesday January 17, [EMAIL PROTECTED] wrote:
> The 5th parameter of filldir_t function type used by vfs_readdir
> was changed from ino_t to u64 in October. Unfortunately the patch
> missed some files in fs/nfsd where functions pointers of type
> encode_dent_fn are passed around and finally
On Thu, Jan 25, 2007 at 11:12:41AM +1100, Nick Piggin wrote:
> David Chinner wrote:
> >On Thu, Jan 25, 2007 at 12:43:23AM +1100, Nick Piggin wrote:
>
> >>And why not just leave it in the pagecache and be done with it?
> >
> >
> >because what is in cache is then not coherent with what is on disk,
Soeren Sonnenburg wrote:
• Note that it might not be such a good idea to do the above on drivers
which don't implement the new EH yet. Those are as of January 2007:
sata_nv, sata_promise (getting there) and sata_sx4.
That should be sata_mv not sata_nv.
--
Robert Hancock Saskatoon, SK,
Hi!
> > Is it highmem-related? Can you try it with mem=256M?
>
> Bad idea, the kernel crashes & burns when I use mem=256, I had to boot
> 2.6.20-rc5-6 single to get back into my machine, very nasty. Remember I
> use an onboard graphics controller that has 128MB of RAM allocated to it
> and I
Hi Nick
On Wed, 24 Jan 2007, Nick Piggin wrote:
Paul Davies wrote:
This patch is a proposed cleanup of the current page table organisation.
Such a cleanup would be a logical first step towards introducing at least
a partial clean page table interface, geared towards providing enhanced
On 1/25/07, Jan Engelhardt <[EMAIL PROTECTED]> wrote:
There are a number of common ports in the 512-1023 range. All
obsolescence and meaninglessness aside, there _are_ rather "important"
services in that range, ldaps, rtsp, kerberos, rsync, ftps, imaps, just
to name a few from /etc/services.
I had a few questions about the linux scheduler and how it
interacts with in a 4 CPU system where the L2 cache is shared
between "pairs" (on same die) of processors.
Some of the later Core processors have 4MB of
L2cache/processor, and on a single chip, both processors have
access to the full 8MB
Jonathan M. McCune wrote:
Hello,
I have written a kernel module which introduces a new subsystem in
sysfs, and it contains several attributes, one of which is binary. So
far, I've been testing it using text. My problem is, attempting to read
data continues forever. For example:
# echo "test
David Chinner wrote:
On Thu, Jan 25, 2007 at 12:43:23AM +1100, Nick Piggin wrote:
And why not just leave it in the pagecache and be done with it?
because what is in cache is then not coherent with what is on disk,
and a direct read is supposed to read the data that is present
in the file
On Mon, 22 Jan 2007, Andrew Morton wrote:
> > On Sun, 21 Jan 2007 14:27:34 -0500 (EST) Justin Piszcz <[EMAIL PROTECTED]>
> > wrote:
> > Why does copying an 18GB on a 74GB raptor raid1 cause the kernel to invoke
> > the OOM killer and kill all of my processes?
>
> What's that? Software raid
On Wed, 2007-01-24 at 22:20 +1100, [EMAIL PROTECTED] wrote:
> From: Dave Airlie <[EMAIL PROTECTED]>
>
> This patch adds support to the radeonfb driver to use the new
> GPU layer to driver the radeon.
Unfortunately, that also massively collides with a giant radeonfb update
that's been simmering
Peter Zijlstra wrote:
On Thu, 2007-01-25 at 00:43 +1100, Nick Piggin wrote:
Have you seen the new launder_page() a_op? called from
invalidate_inode_pages2_range()
It would have been nice to make that one into a more potentially
useful generic callback.
That can still be done when the
Here is my second attempt at the serial driver patch for the
PMC-Sierra MSP71xx device.
There are three different fixes:
1. Fix for THRE errata
- I verified the UART_BUG_TXEN fix does not help with this erratum.
- I left our current fix in until I get our platform booting on
2.6.20-rc4 to try the
Hello list,
I just don't know where else I could send this, it's sooo generic to
Linux and UNIX (perhaps blame SUN for inventing portmap?)
Well, here goes...
As we all know, mountd and other SUNRPC (I question this invention too)
services are at a fixed RPC port number (/etc/rpc) which are
--- Mark Rustad <[EMAIL PROTECTED]> wrote:
> Exactly. Halting use of a version of the kernel based on a single
> incident provides no insight to the source of the problem. It could
> be anything...
There is a world of difference between a polite request for more information
(although I gave
On Wed, Jan 24, 2007 at 05:14:41PM +0300, Vitaly Bordug wrote:
>
> Keeps sysfs from creating link if device is already bound to driver.
> Similar behavior was before the rework;
Which "rework" caused this?
> now without this patch fixed PHY will complain about not been able to
> create file in
1 - 100 of 642 matches
Mail list logo
