2005/7/14, Christoph Hellwig [EMAIL PROTECTED]:
On Thu, Jul 14, 2005 at 04:50:01PM +0300, Yura Pakhuchiy wrote:
2005/7/14, Nathan Scott [EMAIL PROTECTED]:
On Wed, Jul 13, 2005 at 06:22:28PM +0300, Yura Pakhuchiy wrote:
I found patch by Greg Ungreger to fix this problem, but why it's
Roman Zippel writes:
Hi,
On Mon, 11 Jul 2005, Andrew Morton wrote:
Hi Andrew, can you please merge relayfs? It provides a low-overhead
logging and buffering capability, which does not currently exist in
the kernel.
While the code is pretty nicely in shape it
On Thu, 14 Jul 2005, Lee Revell wrote:
On Thu, 2005-07-14 at 10:38 +0200, Ingo Molnar wrote:
- there are real-time applications (robotic environments: fast rotating
tools, media and mobile/phone applications, etc.) that want 10
usecs precision. If such users increased HZ to 100,000
On Thu, Jul 14, 2005 at 09:21:07AM -0500, [EMAIL PROTECTED] wrote:
On July 8 I sent out a patch which re-implemented the rcu-refcounting
of the LSM list in stacker for the sake of supporting safe security
module unloading. (patch reattached here for convenience) Here are
some performance
On Thu, 2005-07-14 at 08:02 -0700, Christoph Lameter wrote:
I doubt that increasing the timer frequency is the way to go to solve
these issues. HZ should be as low as possible and we should strive for
a tickless system.
Agreed. Most of those applications are driven by their own interrupt
On Thu, 2005-07-14 at 07:23 +0200, Ingo Molnar wrote:
* Daniel Walker [EMAIL PROTECTED] wrote:
The whole point of using a semaphore in the pagebuf is because there
is no tracking of who owns the lock so we can actually release it
in a different context. Semaphores were invented for
Take a look at FUSE, it should be able to do all you need
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Thu, 2005-07-14 at 06:18, Andi Kleen wrote:
Daniel McNeil [EMAIL PROTECTED] writes:
This patch relaxes the direct i/o alignment check so that user addresses
do not have to be a multiple of the device block size.
The original reason for this limit was that lots of drivers
(not only
It was always effectual for IO where the mask is 0x.
Okay, point taken :) So for cases of base == maxbase, why would we ever
want to return a nonzero value? What is the intended purpose of the
second part of that conditional?
-
To unsubscribe from this list: send the line unsubscribe
Hello!
The attached patch passed about 36 hours of torture test on each of two
4-CPU x86 machines (about 100 passes through the torture-test script), so
am officially declaring it to be semi-sane. That said, on eight runs of
kernbench+LTP (also on 4-CPU x86 machines), only six passed, and the
Hi kernel.
* kernel [EMAIL PROTECTED] dixit:
First 446 bytes are boot code and all
Next 64 bytes are for 4 partition records, 16 bytes each
Last 2 bytes are signature
And that's right, but only for the MBR. If you set up an extended
partition in the MBR, the partition table for that
Hi Willy,
I think at least I can remove the LOCK instruction when the lock is already
held by someone else and enter the spinning wait directly, right?
0: cmpb $0, slp
jle 2f# lock is not available, then spinning
directly without locking the bus
1: lock; decb
Hello,
I would like to get some feedback on this patch for the kernel. It's sole
purpose is to help in reducing boot time by not waiting to synchronize the
clock edge with the hardware clock. This when combined with other boot
reduction patched can bring the kernel boot time to well under 10
On Thu, Jul 14, 2005 at 08:56:58AM -0700, Daniel Walker wrote:
This reminds me of Documentation/stable_api_nonsense.txt . That no one
should really be dependent on a particular kernel API doing a particular
thing. The kernel is play dough for the kernel hacker (as it should be),
including
Hello,
I didn't find any useful answer anywhere so far, hope it's ok to ask here.
I'm currently trying to get a 2.4.31 up and running on an IBM
BladeCenter HS20/8843. (base system is a stripped down RH9)
When booting the kernel the console is spammmed with:
pc_keyb: controller jammed (0xA7)
I know this is a broken record, but the development process within the LKML
isn't resulting in more stable and better code. Some process change could be
a good thing.
Why does my alps mouse pad have to stop working every time I test a new
STABLE kernel?
Why does swsup have to start hanging
Attached patch fixes the recent C-state based on FADT regression reported by
Kevin.
Please apply.
Thanks,
Venki
Fix the regression with c1_default_handler on some systems where C-states come
from FADT.
Thanks to Kevin Radloff for identifying the issue and also root causing on
exact line of
Quoting Paul E. McKenney ([EMAIL PROTECTED]):
On Thu, Jul 14, 2005 at 09:21:07AM -0500, [EMAIL PROTECTED] wrote:
On July 8 I sent out a patch which re-implemented the rcu-refcounting
of the LSM list in stacker for the sake of supporting safe security
module unloading. (patch reattached
On Thu, 14 Jul 2005, Vojtech Pavlik wrote:
A note on the relaive timer API: There needs to be a way to say
x milliseconds from the time this timer should have triggered instead
of x milliseconds from now, to avoid skew in timers that try to be
strictly periodic.
I disagree.
There should
On Thu, Jul 14, 2005 at 08:44:50AM -0500, [EMAIL PROTECTED] wrote:
Quoting Paul E. McKenney ([EMAIL PROTECTED]):
My guess is that the reference count is indeed costing you quite a
bit. I glance quickly at the patch, and most of the uses seem to
be of the form:
increment ref count
On Thu, 2005-07-14 at 09:37 -0700, Linus Torvalds wrote:
There should be an _absolute_ interface
I'm not arguing there shouldn't be an absolute interface. I'm arguing
that *most* uses are relative, and as such a relative interface makes
sense for those cases.
Btw, this is exactly why the
System:
Motherboard = Tyan K8WE
Processor = 2x Opteron 250
Memory = 8GB ECC Registered
On all of the recent release candidates except for
2.6.13-rc2-git2 the kernel panics while booting. These
versions include 2.6.13-rc2-git* (* != 2 ) and 2.6.13-rc3.
I also want to mention that I am using gcc
When you start merging DRM and fbdev you will be able to use relative
paths that are closer together. For example #include
../char/drm/drmP.h versus #include drm/drmP.h for internal
headers.
No. Using relative include paths is not good. I will most probarly
not work with make O=.
Linus Torvalds wrote:
There's absolutely nothing wrong with jiffies, and anybody who thinks
that
msleep(20);
is fundamentally better than
timeout = jiffies + HZ/50;
just doesn't realize that the latter is a bit more complicated exactly
because the latter is a hell of a lot
Adam Belay [EMAIL PROTECTED] :
[...]
Some nits + a suspect error branch. It seems nice otherwise.
--- a/drivers/pci/bus/bus.c 1969-12-31 19:00:00.0 -0500
+++ b/drivers/pci/bus/bus.c 2005-07-10 22:32:53.0 -0400
[...]
+struct pci_bus * pci_alloc_bus(void)
+{
+ struct
Quoting Paul E. McKenney ([EMAIL PROTECTED]):
On Thu, Jul 14, 2005 at 08:44:50AM -0500, [EMAIL PROTECTED] wrote:
Quoting Paul E. McKenney ([EMAIL PROTECTED]):
My guess is that the reference count is indeed costing you quite a
bit. I glance quickly at the patch, and most of the uses seem
-Original Message-
From: Russell King
Sent: Thursday, July 14, 2005 1:27 AM
To: karl malbrain
Cc: [EMAIL PROTECTED] Kernel. Org
Subject: Re: 2.6.9: serial_core: uart_open
On Wed, Jul 13, 2005 at 10:53:19AM -0700, karl malbrain wrote:
I've also noticed that the boot sequence
You can also look about some methods of function redirection
hooks... add some opcodes at the start of the hooked function
(something like to add a CALL or JMP pointing to the address of your
function). There are docs about this subject, but unfortunately I
couldn't find anything now
On Thu, 14 Jul 2005, Arjan van de Ven wrote:
I *will* argue that for relative delays in drivers, msleep() is better.
Oh, I agree.
I think we should continue the simplification of the simple stuff. If
somebody just wants to sleep a while, do it.
But if somebody is doing this because they
On Thu, 7 Jul 2005, David Gibson wrote:
Now that the hugepage code has been consolidated across the
architectures, it becomes much easier to implement copy-on-write.
Hugepage COW is of limited utility of itself, however, it is
essentially a prerequisite for any of a number of methods of
On Thu, 14 Jul 2005, Chris Friesen wrote:
But if all I really want is to sleep for 20ms, what does the additional
power actually buy me?
If you _only_ want to sleep for 20ms, it doesn't buy you anything.
But the sleep is often part of a bigger picture, where the 20ms might be
part of a
tor 2005-07-14 klockan 10:10 -0700 skrev Paul Vander Griend:
System:
Motherboard = Tyan K8WE
Processor = 2x Opteron 250
Memory = 8GB ECC Registered
On all of the recent release candidates except for
2.6.13-rc2-git2 the kernel panics while booting. These
versions include 2.6.13-rc2-git* (*
This is actually the accumulation of everything we've been saving for
2.6.12, but I was away for a bit and missed 2.6.12 when it came out ...
The patch is available from
http://www.kernel.org/pub/scm/linux/kernel/git/jejb/scsi-for-
linus-2.6.git/
The short changelog is:
Andrew Morton:
o
On Thu, 2005-07-14 at 09:37 -0700, Linus Torvalds wrote:
There's absolutely nothing wrong with jiffies, and anybody who
thinks that
msleep(20);
is fundamentally better than
timeout = jiffies + HZ/50;
What's wrong with structured programming?
-
To unsubscribe from this
I use a Belkin F5D6020 wifi card, (version one), and a belkin f5d6000 pci
adapter for it. A while ago, it was working flawlessly, though I
didn't use it that much after the wife's laptop died.
I've rolled through some kernel upgrades... and it appears my wifi does not
work anymore.
here's the
On Thu, Jul 14, 2005 at 04:58:12PM +0200, Stefan Seyfried wrote:
Andy Isaacson wrote:
Yesterday I booted my laptop to 2.6.13-rc2-mm1, suspended to swsusp,
and
[snip]
and got a panic along the lines of Unable to find swap space, try
a panic? it should only be an error message, but the
I always thought;
First 446 bytes are boot code and all
Right, of course. Otherwise it won't sum up to 512 bytes.
Jan Engelhardt
--
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Thu, 14 Jul 2005, Jan Engelhardt wrote:
What does Windows do here?
windows xp base rate is 100Hz... but multimedia apps can ask for almost
83Hz
Well, Windoes 98 (vmmon) shows very different ones:
Wow. Windows has been doing this since *98*?
...since Windows does multitask
That is exactly why I made this a separate patch, so that we
can test and find out where the problems are and work to fix
them.
That's pretty hard because there are a lot of block drivers.
And might not very nice for people's data.
Are there problems only with odd sizes, or do drivers
Andy Isaacson wrote:
Perhaps the image should be more rigorously checked? I'm wishing that
it would verify that the header and the image matched, after it finishes
in your case, the header and the image matched. There was no new image
on disk. And no new header.
reading the image. For
This is part [0/7] of the v9fs-2.0.2 patch against Linux 2.6.13-rc2-mm2.
The changes in this patch-set are primarily motivated by comments from
Chistoph Hellwig (hch):
there's a few issues with the code still I'd like to see fixed:
- there's three sparse warnings still. Two of them are easily
Someone mentioned that NUMA support for dual core opteron need acpi
support in LinuxBIOS.
there may be some other solution for that.
1. PowerPC already support dual core and it should support NUMA, So
the Open Firmware must have some NUMA entry definition.
Can we make x86-64 kernel support
On Thu, 2005-07-14 at 10:58 -0700, yhlu wrote:
Someone mentioned that NUMA support for dual core opteron need acpi
support in LinuxBIOS.
there may be some other solution for that.
1. PowerPC already support dual core and it should support NUMA, So
the Open Firmware must have some NUMA entry
This is part [2/7] of the v9fs-2.0.2 patch against Linux 2.6.13-rc2-mm2
This part of the patch contains the VFS file, dentry, directory interface
changes related to hch's comments.
Signed-off-by: Eric Van Hensbergen [EMAIL PROTECTED]
--
fs/9p/vfs_file.c | 35
This is part [1/7] of the v9fs-2.0.2 patch against Linux 2.6.13-rc2-mm2
This part of the patch contains Documentation, Makefiles,
and configuration file changes related to hch's comments.
Signed-off-by: Eric Van Hensbergen [EMAIL PROTECTED]
--
fs/9p/Makefile |1 -
1 files
This is part [4/7] of the v9fs-2.0.2 patch against Linux 2.6.13-rc2-mm2.
This part of the patch contains VFS superblock and mapping code changes
related to hch's comments.
Signed-off-by: Eric Van Hensbergen [EMAIL PROTECTED]
--
v9fs.c | 103
--- Peter Staubach [EMAIL PROTECTED] wrote:
Vlad C. wrote:
--- Hans Reiser [EMAIL PROTECTED] wrote:
Please treat at greater length how your proposal
differs from NFS.
I think NFS is not flexible enough because:
1) NFS requires synchronization of passwd files or
NIS/LDAP
On Thu, Jul 14, 2005 at 12:13:57PM -0500, [EMAIL PROTECTED] wrote:
Quoting Paul E. McKenney ([EMAIL PROTECTED]):
On Thu, Jul 14, 2005 at 08:44:50AM -0500, [EMAIL PROTECTED] wrote:
Quoting Paul E. McKenney ([EMAIL PROTECTED]):
My guess is that the reference count is indeed costing you
This is part [3/7] of the v9fs-2.0.2 patch against Linux 2.6.13-rc2-mm2.
This part of the patch contains the VFS inode interfaces changes related
to hch's comments.
Signed-off-by: Eric Van Hensbergen [EMAIL PROTECTED]
--
fs/9p/vfs_inode.c | 69
This is part [5/7] of the v9fs-2.0.2 patch against Linux 2.6.13-rc2-mm2.
This part of the patch contains the 9P protocol function changes related
to hch's comments.
Signed-off-by: Eric Van Hensbergen [EMAIL PROTECTED]
--
fs/9p/9p.c |2 +-
fs/9p/conv.c| 54
This is part [7/7] of the v9fs-2.0.2 patch against Linux 2.6.13-rc2-mm2.
This part of the patch contains debug and other misc routine changes related
to hch's comments.
Signed-off-by: Eric Van Hensbergen [EMAIL PROTECTED]
--
fs/9p/error.c|3 +--
fs/9p/error.h|3 +++
Thanks, Paul, that's a great idea!
The approach I'm testing right now just does a module_get(mod), which
is released when you manually disable the module by echoing it's name
into /sys/kernel/security/stacker/unload, so that must be done before
you can rmmod. This way no refcounting is actually
[closed mailing list dropped. Sorry I have no plans to argue with
your mailbots]
On Thu, Jul 14, 2005 at 01:00:01PM -0600, Ronald G. Minnich wrote:
if there is any chance of getting along without ACPI entries that is best.
Linux did do this once already, for SMP K8: K8 can boot and run NUMA
On Thu, Jul 14, 2005 at 10:21:41AM -0700, Linus Torvalds wrote:
In other words, the _right_ way to do this is literally
unsigned long timeout = jiffies + HZ/2;
for (;;) {
if (ready())
return 0;
if (time_after(timeout, jiffies))
On Thu, 2005-07-14 at 09:37 -0700, Linus Torvalds wrote:
On Thu, 14 Jul 2005, Vojtech Pavlik wrote:
A note on the relaive timer API: There needs to be a way to say
x milliseconds from the time this timer should have triggered instead
of x milliseconds from now, to avoid skew in timers
AFIAK, for x86_64 kernel, it will try to read NUMA configuration from
HW directory. We don't have to export any ACPI table.
It doesn't work for dual core or 8 sockets for some reason. Since the SRAT
code works fine and is in general more future proof we never tracked down
why. Patches welcome.
For S2895, with 1Gx8 Installed and E stepping dual core opteron with
1G mem hole emable, got
Bootdata ok (command line is apic=debug ramdisk_size=65536
root=/dev/ram0 rw console=tty0 console=ttyS0,115200n8 )
Linux version 2.6.12-rc5 ([EMAIL PROTECTED]) (gcc version 3.3.3 (SuSE
Linux)) #26 SMP Thu
P.S.: It is very nasty to cc closed mailing lists when posting
to open ones. Please don't do that in the future.
-Andi
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
FYI in Tyan S4881 (8 ways dual core 875 cpu ) with LinuxBIOS I got
also the 1G mem hole is enabled.
So the kernel should be OK with read NUMA directly from HW.
YH
Firmware type: LinuxBIOS
old bootloader convention, maybe loadlin?
Bootdata ok (command line is apic=debug ramdisk_size=65536
On Thu, 14 Jul 2005, Andi Kleen wrote:
However you'll likely need ACPI for other reasons anyways, e.g. for
better power saving.
bummer. What the BIOS vendors are doing (to lock in proprietary BIOS, some
say) is making ACPI tables copyright the BIOS vendor, not the motherboard
vendor. So
if there is any chance of getting along without ACPI entries that is best.
Linux did do this once already, for SMP K8: K8 can boot and run NUMA
without an SRAT table. What more is needed for dual core, and could Linux
support in this area be extended?
ron
-
To unsubscribe from this list: send
From: Nishanth Aravamudan [EMAIL PROTECTED]
Description: The mod_timer() statement mistakenly has a comma at the end
of the line instead of a semicolon.
Signed-off-by: Nishanth Aravamudan [EMAIL PROTECTED]
---
vt.c |2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -urpN
On Thu, Jul 14, 2005 at 07:10:14PM +0200, Francois Romieu wrote:
Adam Belay [EMAIL PROTECTED] :
[...]
Some nits + a suspect error branch. It seems nice otherwise.
If I'm correct, this patch only moves the code into different files, it
doesn't change any of it, so your comments apply to the
On Mon, Jul 04, 2005 at 09:57:02AM +0100, Russell King wrote:
On Mon, Jul 04, 2005 at 12:15:00PM +0400, Andrey Panin wrote:
Me too, but I can confirm that my SIIG single port serial card still works
with the patch, so at least SIIG quirk table cleanup didn't broke anything.
Thanks for
On Thu, Jun 23, 2005 at 02:23:35PM +0100, Russell King wrote:
+
+---
+
+What:register_serial/unregister_serial
+When:December 2005
+Why: This interface does not allow serial ports to be registered against
+ a struct device, and as such does not
On Thu, Jul 14, 2005 at 04:55:12AM -0400, Adam Belay wrote:
+EXPORT_SYMBOL(pci_add_bus);
This doens't need to be exported, right? No module uses it. But if
they do, I suggest EXPORT_SYMBOL_GPL() instead, is that ok?
thanks,
greg k-h
-
To unsubscribe from this list: send the line unsubscribe
On Thu, 2005-07-14 at 19:02 +0200, Arjan van de Ven wrote:
On Thu, 2005-07-14 at 09:37 -0700, Linus Torvalds wrote:
just doesn't realize that the latter is a bit more complicated exactly
because the latter is a hell of a lot more POWERFUL. Trying to get rid of
jiffies for some religious
On Thu, 14 Jul 2005, Karsten Wiese wrote:
Have I corrected the other path of ioapic early initialization, which had lacked
virtual-address setup before ioapic_data[ioapic] was to be filled in -51-28?
Please test attached patch on top of -51-29 or later.
Also on Systems that liked -51-28.
On Sun, Jul 17, 2005 at 08:53:59AM -0500, [EMAIL PROTECTED] wrote:
This is part [7/7] of the v9fs-2.0.2 patch against Linux 2.6.13-rc2-mm2.
This part of the patch contains debug and other misc routine changes related
to hch's comments.
Here a few if( instead if ( formatting sneaked in.
-
To
+static inline void buf_check_size(struct cbuf *buf, int len)
+{
+ if (buf-p+len buf-ep) {
+ if (buf-p buf-ep) {
+ eprintk(KERN_ERR, buffer overflow\n);
+ buf-p = buf-ep + 1;
+ }
+ }
+}
handling a buffer
@@ -383,9 +379,10 @@ v9fs_file_write(struct file *filp, const
return -ENOMEM;
ret = copy_from_user(buffer, data, count);
- if (ret)
+ if (ret) {
dprintk(DEBUG_ERROR, Problem copying from user\n);
- else
+ return -EFAULT;
+ }
On Wednesday 13 Jul 2005 16:30, Ingo Molnar wrote:
* Ingo Molnar [EMAIL PROTECTED] wrote:
it worked upon the first try, and indeed my testbox crashed within 10
seconds:
BUG: Unable to handle kernel NULL pointer dereference
BUG: Unable to handle kernel NULL pointer dereference at
On Thu, 2005-07-14 at 12:33 -0700, Greg KH wrote:
On Thu, Jul 14, 2005 at 04:55:12AM -0400, Adam Belay wrote:
+EXPORT_SYMBOL(pci_add_bus);
This doens't need to be exported, right? No module uses it. But if
they do, I suggest EXPORT_SYMBOL_GPL() instead, is that ok?
thanks,
greg k-h
On Thu, 2005-07-14 at 12:30 -0700, Greg KH wrote:
On Thu, Jul 14, 2005 at 07:10:14PM +0200, Francois Romieu wrote:
Adam Belay [EMAIL PROTECTED] :
[...]
Some nits + a suspect error branch. It seems nice otherwise.
If I'm correct, this patch only moves the code into different files, it
On Wed, Jul 13, 2005 at 01:23:24PM -0500, Eric Van Hensbergen wrote:
Sorry I didn't get to these quicker - was on vacation and basically
off-line for the past week and a half. I've made 90% of the changes
suggested and committed them to my git tree, I'll combine the changes
into a single
On Thu, 14 Jul 2005, Russell King wrote:
Umm. Except, according to your description of what it's supposed to
do, the above code can have an accumulating error.
No. It can have a local drift, but the point is, the error never gets
worse - it _stays_ local.
There's no point in polling
On Thu, 14 Jul 2005, john stultz wrote:
We'll I'd probably put it as: they do care about absolute time, but
they do not care about ticks or timer interrupt frequency
Well, the thing is, you have to count time some sane way.
You can do it by having very expensive data structures that say
Jesse Brandeburg [EMAIL PROTECTED] wrote:
On 7/13/05, Mikhail Kshevetskiy [EMAIL PROTECTED] wrote:
symptom
===
modprobe e100
ifconfig eth0 ip netmask netmask
result:
===
SIOCADDRT: Network is unreachable
There were no such error in 2.6.13-rc2
odd, both e100 and
On Thu, Jul 14, 2005 at 01:04:26PM -0600, Ronald G. Minnich wrote:
On Thu, 14 Jul 2005, Andi Kleen wrote:
However you'll likely need ACPI for other reasons anyways, e.g. for
better power saving.
bummer. What the BIOS vendors are doing (to lock in proprietary BIOS, some
say) is
On 7/14/05, Christoph Hellwig [EMAIL PROTECTED] wrote:
+static inline void buf_check_size(struct cbuf *buf, int len)
+{
+ if (buf-p+len buf-ep) {
+ if (buf-p buf-ep) {
+ eprintk(KERN_ERR, buffer overflow\n);
+ buf-p = buf-ep +
Doh! Good catch, I'll fix and resubmit - same goes for the formating issues.
On 7/14/05, Christoph Hellwig [EMAIL PROTECTED] wrote:
@@ -383,9 +379,10 @@ v9fs_file_write(struct file *filp, const
return -ENOMEM;
ret = copy_from_user(buffer, data, count);
- if
On Thu, 2005-07-14 at 20:58 +0100, Alistair John Strachan wrote:
the responsiveness of our instrument to 300us which is low enough
for the real-time PCR industry
PCR, as in polymerase chain reaction? They can do that in realtime?
Impressive.
Lee
-
To unsubscribe from this list: send the
Greg KH [EMAIL PROTECTED] :
On Thu, Jul 14, 2005 at 07:10:14PM +0200, Francois Romieu wrote:
Adam Belay [EMAIL PROTECTED] :
[...]
Some nits + a suspect error branch. It seems nice otherwise.
If I'm correct, this patch only moves the code into different files, it
doesn't change any of
Nicholas Hans Simmonds [EMAIL PROTECTED] wrote:
[...]
Other than this, what are the general thoughts about this method as
opposed to just using a well defined byte order?
I'd prefer a defined byte order. That way it won't bite too hard if I
happen to move a filesystem (image) from PC to SPARC
On Thursday 14 Jul 2005 20:34, FyD wrote:
Dear All,
I have a problem with a program named Gaussian (http://www.gaussian.com)
(versions g98 or g03) and FC 4.0 (default kernel 2.6.11): I am used to take
Gaussian binaries compiled on the RedHat 9.0 version, and used them on FC
2.0 or FC 3.0. If
On Thu, Jul 14, 2005 Linus Torvalds wrote:
In other words, the _right_ way to do this is literally
unsigned long timeout = jiffies + HZ/2;
for (;;) {
if (ready())
return 0;
if (time_after(timeout, jiffies))
On Thu, 2005-07-14 at 11:23, Andi Kleen wrote:
That is exactly why I made this a separate patch, so that we
can test and find out where the problems are and work to fix
them.
That's pretty hard because there are a lot of block drivers.
And might not very nice for people's data.
On Thu, 14 Jul 2005, Linus Torvalds wrote:
So the _sane_ way to do timeouts is to define an _arbitrary_ clock that is
just an integer counter. None of this nanoseconds + full seconds crap.
None of this stupid confusion with real time. You select something that
is conceptually _clearly_
From: Nishanth Aravamudan [EMAIL PROTECTED]
Description: Add a jiffies_to_nsecs() helper function. Make consistent
the size of microseconds (unsigned long) throughout the conversion
functions.
Signed-off-by: Nishanth Aravamudan [EMAIL PROTECTED]
---
jiffies.h | 15 +--
1 files
From: Nishanth Aravamudan [EMAIL PROTECTED]
Description: The core revision to the soft-timer subsystem to divorce it
from the timer interrupt in software, i.e. jiffies. Instead, use
getnstimeofday() (via do_monotonic_clock()) as the basis for addition
and expiration of timers. Add a new unit, the
From: Nishanth Aravamudan [EMAIL PROTECTED]
Description: Add new human-time schedule_timeout() style functions,
along with the appropriate constants/prototypes.
Signed-off-by: Nishanth Aravamudan [EMAIL PROTECTED]
---
include/linux/sched.h |7 ++
include/linux/time.h |4 +
From: Nishanth Aravamudan [EMAIL PROTECTED]
Description: Add timespec and timeval conversion functions for
nanoseconds. Convert sys_nanosleep() to use schedule_timeout_nsecs().
Signed-off-by: Nishanth Aravamudan [EMAIL PROTECTED]
---
include/linux/time.h | 33
On 14.07.2005 [12:18:41 -0700], john stultz wrote:
snip
Nish has some code, which I hope he'll be sending out shortly that
does just this, converting the soft-timer subsystem to use absolute
time instead of ticks for expiration. I feel it both simplifies the
code and makes it easier to
On Thu, 2005-07-14 at 13:28 -0700, Nishanth Aravamudan wrote:
+static inline u64 jiffies_to_nsecs(const unsigned long j)
+{
+#if HZ = NSEC_PER_SEC !(NSEC_PER_SEC % HZ)
+ return (NSEC_PER_SEC / HZ) * (u64)j;
+#elif HZ NSEC_PER_SEC !(HZ % NSEC_PER_SEC)
+ return ((u64)j + (HZ /
On 14.07.2005 [13:54:47 -0700], Dave Hansen wrote:
On Thu, 2005-07-14 at 13:28 -0700, Nishanth Aravamudan wrote:
+static inline u64 jiffies_to_nsecs(const unsigned long j)
+{
+#if HZ = NSEC_PER_SEC !(NSEC_PER_SEC % HZ)
+ return (NSEC_PER_SEC / HZ) * (u64)j;
+#elif HZ NSEC_PER_SEC
Vojtech Pavlik [EMAIL PROTECTED] writes:
HPETs have a fixed frequency (usually 14.31818 MHz, but that depends
on the manufacturer).
- 64-bit match timer (i.e., a register in the counter which fires IRQ
when it matches the counter value)
That's implemented in the HPET hardware.
Hi!
Please use enter key every 70 chars or so...
This patch adds the Dell Systems Management Base driver.
You keep posting this driver without explaining/showing how it's used.
Could you perhaps give some more details here please?
Here's some more information on the driver
Fix formating errors and a memory leak that crept in the
previous round of revisions to v9fs. These will be reincorperated
into the patchset and resent to akpm.
Signed-off-by: Eric Van Hensbergen [EMAIL PROTECTED]
---
commit 22d785a22895513c6ab67dfa53c25b8b833fe235
tree
Of course using APIC internal timers is generally the best idea on SMP,
but they may have had reasons to avoid them (it's not an ISA interrupt,
so
it could have been simply out of question in the initial design).
Best? No.
Local APIC timers are based on a clock which on many processors will
Hi,
the following patch adds a post_setgid() security hook, and necessary dummy
funcs.
Signed-off-by: Jan Engelhardt [EMAIL PROTECTED]
diff -dpru linux-2.6.13-rc1-git3-20050706140055/include/linux/security.h
AS17/include/linux/security.h
---
401 - 500 of 615 matches
Mail list logo
