, struct cifsTconInfo *tcon,
--
1.5.3.4
--
Thanks,
Steve
-
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/
processes scenario.
That is so you can walk the process table and or the bit in unconditionally.
All processes need to be auditable or you've got a security hole.
-Steve
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
then this model is probably ok.
For iWARP, it means TCP retransmit and slow start and all that, but if
its an infrequent event, then its ok if it helps the host better manage
memory.
Maybe... ;-)
Steve.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
it will resolve to one device and that
device cannot do loopback...
Steve.
--
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
RDMA/cxgb3: Fail loopback connections.
The cxgb3 HW and driver don't support loopback RDMA connections. So fail
any connection attempt where the destination address is local.
Signed-off-by: Steve Wise [EMAIL PROTECTED]
---
drivers/infiniband/hw/cxgb3/iwch_cm.c | 16
1
devices that can do this?
Chelsio's T3 HW doesn't support this.
Steve.
--
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
Roland Dreier wrote:
how can a static void function return 0?
good question... I've fixed the patch in my tree.
oops.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Roland Dreier wrote:
Steve, I had to update the patch adding an include and fixing the
function declaration (as below)... but how much testing have you done
with this??
Now I understand. I thought I'd fixed these! I fixed them locally in
the test tree on my victim and then tested
Steve Wise wrote:
Roland Dreier wrote:
Steve, I had to update the patch adding an include and fixing the
function declaration (as below)... but how much testing have you done
with this??
Now I understand. I thought I'd fixed these! I fixed them locally in
the test tree on my victim
uses a single PD).
Steve.
--
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/
Robin Holt wrote:
On Thu, Feb 14, 2008 at 09:09:08AM -0600, Steve Wise wrote:
Note that for T3, this involves suspending _all_ rdma connections that are
in the same PD as the MR being remapped. This is because the driver
doesn't know who the application advertised the rkey/stag to. So
You are right - this should have gone in 3.5.
Please remind me if you see an important patch not make linux-next (or
equivalently the cifs-2.6.git for-next branch). I get a big volume of
email.
On Sun, Sep 23, 2012 at 5:18 PM, Anton Altaparmakov ai...@cam.ac.uk wrote:
Hi Steve,
Hey, I sent
,
put_unaligned_le16(wchar_to, to[i]);
}
+success:
put_unaligned_le16(0, to[i]);
return i;
}
Looks reasonable...
Acked-by: Jeff Layton jlay...@redhat.com
Steve, could you consider my patch for inclusion into Linux?
Thanks,
Frediano
--
Thanks,
Steve
--
To unsubscribe from
On Mon, Oct 8, 2012 at 3:18 AM, Frediano Ziglio
frediano.zig...@citrix.com wrote:
On Wed, 2012-10-03 at 14:49 -0500, Steve French wrote:
Merged - but doesn't the reverse also have to be added in cifs_from_utf16?
ie
utf16s_to_utf8s(uni, ... );
Not strictly necessary, at least
Acked-by: Steve Wise sw...@opengridcomputing.com
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Acked-by: Steve Wise sw...@opengridcomputing.com
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
-name = info-FileName[0];
- /* one byte length, no endianess conversion */
+ /* one byte length, no endianness conversion */
de-namelen = info-FileNameLength;
de-resume_key = info-ResumeKey;
}
--
1.8.0.rc3.16.g8ead1bf
--
Thanks,
Steve
--
Thanks,
Steve
Evgeniy Polyakov wrote:
Hi Steve.
On Mon, Sep 17, 2007 at 10:25:04AM -0500, Steve Wise ([EMAIL PROTECTED]) wrote:
Does creating the whole new netdevice is a too big overhead, or is it
considered bad idea?
I think its too big overhead, and pretty invasive on the low level cxgb3
driver. I
Sean Hefty wrote:
The iWARP driver must translate all listens on address 0.0.0.0 to the
set of rdma-only ip addresses for the device in question. This prevents
incoming connect requests to the TCP ipaddresses from going up the
rdma stack.
I've only given this a high level review at this
already bound
to 0.0.0.0. This is done by maintaining a list of listening endpoints
off the device struct.
- The address list, the listening endpoint list, and each list of
stid/addrs in use per listening endpoint are all protected via a mutex
per iw_cxgb3 device.
Signed-off-by: Steve Wise [EMAIL
Rolan/Sean,
What do you all think?
Steve.
Steve Wise wrote:
iw_cxgb3: Support iwarp-only interfaces to avoid 4-tuple conflicts.
Version 3:
- don't use list_del_init() where list_del() is sufficient.
Version 2:
- added a per-device mutex for the address and listening endpoints lists
Sean Hefty wrote:
The sysadmin creates for iwarp use only alias interfaces of the form
devname:iw* where devname is the native interface name (eg eth0) for
the
iwarp netdev device. The alias label can be anything starting with iw.
The iw immediately after the ':' is the key used by the
, with this solution is that it FORCES the admins to
use 2 subnets when 1 is sufficient if the net maintainers would unify
the port space...
Steve.
Arkady Kanevsky email: [EMAIL PROTECTED]
Network Appliance Inc. phone: 781-768-5395
1601 Trapelo Rd. - Suite
addresses on every iwarp device...
Had we run this proposal by administrators?
There has been no other solution proposed that Dave Miller and Jeff
Garzik won't NAK...
Steve.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
by port number, to needlessly use a separate subnet for the rdma
service.
I'm at a loss as to how to proceed.
Any ideas?
Steve.
Roland Dreier wrote:
Since 2.6.23 still isn't out, and I've managed to reduce my patch
review backlog a bit, it's probably a good idea to give another update
about
either, but it avoids 2 separate
subnets...
Steve.
Arkady Kanevsky email: [EMAIL PROTECTED]
Network Appliance Inc. phone: 781-768-5395
1601 Trapelo Rd. - Suite 16.Fax: 781-895-1195
Waltham, MA 02451 central phone: 781-768-5300
David Miller wrote:
From: Sean Hefty [EMAIL PROTECTED]
Date: Thu, 09 Aug 2007 14:40:16 -0700
Steve Wise wrote:
Any more comments?
Does anyone have ideas on how to reserve the port space without using a
struct socket?
How about we just remove the RDMA stack altogether? I am not at all
is indeed valid.
So I think the changes wouldn't be small to enhance the design to add a
concept of an alias interface.
I'll look into this more though.
Steve.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo
Roland,
We'll work on upgrading you to T3B2 boards as well.
Stay tuned.
Steve.
Divy Le Ray wrote:
Roland Dreier wrote:
Looks OK to me but I would just roll up the second patch into the
first patch and let Jeff merge it as one commit. There's no point in
creating an intermediate tree
and UDP)...
Maybe you have something in mind here that I'm not thinking about?
Steve.
-
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
in 2.6.21.
Steve
-
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/
Ray [EMAIL PROTECTED]
ACK patches 9-14, but dropped, since they do not apply to #upstream
(probably due to fixes sent into 2.6.23-rc)
Hey Jeff,
I think 9-14 still need to be incorporated. I don't see them in your
upstream branch, and they aren't in linus' tree either.
Steve
Jeff Garzik wrote:
On Wed, Sep 05, 2007 at 09:00:04AM -0500, Steve Wise wrote:
Jeff Garzik wrote:
Divy Le Ray wrote:
From: Divy Le Ray [EMAIL PROTECTED]
Load microcode engine when the interface
is configured up.
Bump up version to 1.1.0.
Allow the driver to be and running with
older
to get one of these created.
To have the cxgb3 driver create something like 'iw0', I think it would
need to create a full net_device struct. This makes the change much
more complex. But perhaps its the right thing to do...
Steve.
-
To unsubscribe from this list: send the line unsubscribe
Steve Wise wrote:
Roland Dreier wrote:
What's wrong with my suggestion of having the iwarp driver create an
iwX interface to go with the normal ethX interface? It seems
simpler to me, and there's a somewhat similar precedent with how
mac80211 devices create both wlan0
ND, rdma address resolution fails in the presence of
dropped arp bcast packets.
Signed-off-by: Steve Wise [EMAIL PROTECTED]
---
drivers/infiniband/core/addr.c |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/drivers/infiniband/core/addr.c b/drivers/infiniband/core
,
Steve
-
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/
. Of course I may have missed something.
autofs4 some
OK, uid and gid aren't shown.
That should be straight forward to fix.
What's your time frame for this?
ASAP ;)
2.6.24 would be a nice, but it won't be easy...
Miklos
--
Thanks,
Steve
-
To unsubscribe from this list: send
This patch doesn't seem to have gone in yet
Steve.
David Miller wrote:
From: Divy Le Ray [EMAIL PROTECTED]
Date: Mon, 13 Aug 2007 12:33:04 -0700
From: Divy Le Ray [EMAIL PROTECTED]
cxgb3 used netdev_priv() and dev-priv for different purposes.
In 2.6.23, netdev_priv() == dev-priv, cxgb3
sandbox ;-)
For background reading (if you dare), see:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg05162.html
and
http://www.mail-archive.com/[EMAIL PROTECTED]/msg44312.html
Also: I'm on vacation starting tomorrow until Tuesday 9/4. I'll address
comments when I return...
Steve
));
} else {
- return -EIO;
+ rc = -EIO;
}
FreeXid(xid);
--
Thanks,
Steve
-
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
;
remain = seconds %
MIN_TZ_ADJ;
if (remain = (MIN_TZ_ADJ
/ 2))
--
--
Thanks,
Steve
-
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
@@ L:[EMAIL PROTECTED]
W: http://us1.samba.org/samba/Linux_CIFS_client.html
T: git kernel.org:/pub/scm/linux/kernel/git/sfrench/cifs-2.6.git
S: Supported
+F: fs/cifs/
CONFIGFS
P: Joel Becker
--
Thanks,
Steve
-
To unsubscribe from this list: send the line
. Is
samba-technical really the right list for cifs-vfs patches? Aside from
being CC'ed on such patches, I've never seen discussion of them on the
Samba mailing lists.
Steve: Shouldn't that be linux-cifs-client?
linux-cifs-client is mentioned on the L: entry immediately before the
samba-technical
David Miller wrote:
From: Sean Hefty [EMAIL PROTECTED]
Date: Thu, 09 Aug 2007 14:40:16 -0700
Steve Wise wrote:
Any more comments?
Does anyone have ideas on how to reserve the port space without using a
struct socket?
How about we just remove the RDMA stack altogether? I am not at all
Any feedback on my patch?
Anybody know what the msg_byte in include/scsi/scsi.h
is for?
scsi.h says:
* msg_byte= return status from host adapter itself.
So, it's ok to use the msg_byte for device specific error codes?
-- steve
-
To unsubscribe from this list: send the line
]/msg05162.html
Thanks,
Steve.
---
RDMA/CMA: Allocate PS_TCP ports from the host TCP port space.
This is needed for iwarp providers that support native and rdma
connections over the same interface.
Signed-off-by: Steve Wise [EMAIL PROTECTED]
---
drivers/infiniband/core/cma.c | 27
Evgeniy Polyakov wrote:
Hi Steve.
On Tue, Aug 07, 2007 at 09:37:41AM -0500, Steve Wise ([EMAIL PROTECTED]) wrote:
+static int cma_get_tcp_port(struct rdma_id_private *id_priv)
+{
+ int ret;
+ struct socket *sock;
+
+ ret = sock_create_kern(AF_INET, SOCK_STREAM, IPPROTO_TCP
Any more comments?
Steve Wise wrote:
Networking experts,
I'd like input on the patch below, and help in solving this bug
properly. iWARP devices that support both native stack TCP and iWARP
(aka RDMA over TCP/IP/Ethernet) connections on the same interface need
the fix below or some
Make the iw_cxgb3 module parameters writable.
Signed-off-by: Steve Wise [EMAIL PROTECTED]
---
drivers/infiniband/hw/cxgb3/iwch_cm.c | 16
1 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/infiniband/hw/cxgb3/iwch_cm.c
b/drivers/infiniband/hw/cxgb3
iw_cxgb3: Always call low level send function via cxgb3_ofld_send().
Avoids deadlocks.
Signed-off-by: Steve Wise [EMAIL PROTECTED]
---
drivers/infiniband/hw/cxgb3/iwch_cm.c | 16
1 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/infiniband/hw/cxgb3
On Sunday 29 July 2007 11:02:33 Adrian Bunk wrote:
They are still completely unused, but hopefully some of the theoretical
code that might use it will appear in the kernel in the near future...
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
Acked-by: Steve Grubb [EMAIL PROTECTED]
I am
be to get a suitable fix in
the current nfs-utils.
Please open up bugs on all three of these issues and
we'll see what can done...
steved.
commit 851ce1cb766cf295db85900aab804c0f82c12ab3
Author: Steve Dickson [EMAIL PROTECTED]
Date: Tue Jul 31 09:57:19 2007 -0400
Stop rpc.mound from crashing
at connection setup. So changing them is safe in that
existing connections aren't affected, and only subsequent connections
will utilize the new values.
Sorry for the terse changelog...
Steve.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
Satyam Sharma wrote:
Hi,
On Thu, 2 Aug 2007, Stefan Walter wrote:
Steve Dickson wrote:
Stefan Walter wrote:
We do this on a much larger scale though. The bug we ran into is
in line 96 in utils/mountd/auth.c. The strcpy can corrupt
memory when it copies the string returned
On Fri, 2007-04-20 at 15:32 -0700, Roland Dreier wrote:
Hook up mlx4_core and mlx4_ib drivers to Kconfig and Makefiles.
Signed-off-by: Roland Dreier [EMAIL PROTECTED]
---
infiniband/Kconfig |2 ++
infiniband/Makefile |1 +
infiniband/hw/mlx4/Kconfig |9
in this series because its required by the patch preceeding it
in the series.
Steve.
Shortlog:
Steve Wise:
Fix TERM codes.
Fail qp creation if the requested max_inline is too large.
Initialize cpu_idx field in cpl_close_listserv_req message.
Support for new abort logic
Fix TERM codes.
Fix TERMINATE layer, type, and ecode values based on
conformance testing.
Signed-off-by: Steve Wise [EMAIL PROTECTED]
---
drivers/infiniband/hw/cxgb3/iwch_qp.c | 69 ++---
1 files changed, 38 insertions(+), 31 deletions(-)
diff --git a/drivers
Initialize cpu_idx field in cpl_close_listserv_req message.
Signed-off-by: Steve Wise [EMAIL PROTECTED]
---
drivers/infiniband/hw/cxgb3/iwch_cm.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/infiniband/hw/cxgb3/iwch_cm.c
b/drivers/infiniband/hw/cxgb3
Support for new abort logic.
The HW now posts 2 ABORT_RPL and/or PEER_ABORT_REQ messages. We need
to handle them by silenty dropping the 1st but mark that we're ready
for the final message. This plugs some close races between the uP and HW.
Signed-off-by: Steve Wise [EMAIL PROTECTED
Update required firmware revision to 4.0.0.
Signed-off-by: Steve Wise [EMAIL PROTECTED]
---
drivers/net/cxgb3/version.h |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/cxgb3/version.h b/drivers/net/cxgb3/version.h
index 042e27e..b112317 100644
Fail qp creation if the requested max_inline is too large.
Signed-off-by: Steve Wise [EMAIL PROTECTED]
---
drivers/infiniband/hw/cxgb3/cxio_wr.h |1 +
drivers/infiniband/hw/cxgb3/iwch_provider.c |3 +++
2 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/drivers
Chelsio wants folks on this new firmware asap.
Steve.
-
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/
already mounted
(with Unix Extensions) to the same server (perhaps to a different
share). How important would it be to have two mounts to the same
server one with unix extensions and one without?
--
Thanks,
Steve
diff --git a/fs/cifs/CHANGES b/fs/cifs/CHANGES
index 301631c..62dcf63 100644
--- a/fs
smbfs displays the uid of the mounter in show_mounts (viewable in
/proc/mounts ) and this would allow a setuid unmount program to check
the uid of the mounter via /proc/mounts (there is also an ioctl which
does something similar).
Is this approach secure enough?
I slightly prefer an approach
Alexander Nyberg [EMAIL PROTECTED] wrote on 04/11/2005 03:26:14 PM:
Function names and return types on same line - conform to
established
fs/cifs/ style.
-void
-MD5Init(struct MD5Context *ctx)
+void MD5Init(struct MD5Context *ctx)
{
ctx-buf[0] = 0x67452301;
ctx-buf[1]
Francois Romieu wrote:
Btw nobody cared about fs/cifs/connect.c::CIFSNTLMSSPNegotiateSessSetup
(indentation from Mars + unchecked allocations before dereferences).
--
Ueimor
That routine is disabled by default (as with the SPNEGO one) so it has
not gotten much attention, it will probably go
On Mon, Apr 18, 2005 at 03:52:02AM +0200, Adrian Bunk wrote:
This patch removes cifs_kcalloc and replaces it with calls to
kcalloc(1, ...) .
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
As a followup patch you might want to check the return value
of all those calls before blindly deferencing
The recent changes in cifs have helped a lot with dbench performance.
Mounting cifs version 1.33 (current development tree of cifs) to current
Samba 3 (loopback on same host, to eliminate most network adapter
effects) showed about a tenfold improvement over older cifs -
Running dbench version
Roman, besides BK being closed source, how exactly is it lacking for
your needs? If what it lacks is a good idea and helps many, Larry and
crew might be willing to add whatever it is you need.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
at work,
but later this week I will post the latest patches for review.
I haven't been following Ray's manual page migration thread
but will get up-to-speed also, and see how it impacts my patchset
to mempolicy.
Steve
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
As I was trying to decipher the kernel keyring API this morning, I
noticed the gnome-keyring/gnom-keyring manager which I thought might
have already implemented a pam module to store logon info
(userid/password at a minimum) in the kernel keyring (could avoid the
need for prompting for the
Is there any argument against using the DNOTIFY/poll upcall approach
(against pseudo files e.g. in /proc or /sysfs) that e.g. nfs uses now to
get from kernel space to get data back from user space helper routines
(e.g. for idmapping and gssapi)? Since there could be security and
potential
I saw your patch referenced in
http://marc.theaimsgroup.com/?l=linux-kernelm=110859724430665w=2
At first glance there is one odd place in the proposed patch:
- cifs_ace-cifs_e_perm = (__u8)cpu_to_le16(local_ace-e_perm);
- cifs_ace-cifs_e_tag = (__u8)cpu_to_le16(local_ace-e_tag);
+
info would help.
Cheers,
Steve Wooding.
-
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/
It looks like a couple of exports and a key supporting function are
missing from the inotify patch that went into mainline yesterday.
I don't see an inode operation for registering inotify events in the fs
(there is a file operation for dir_notify to register its events). In
create_watch in
I don't see an inode operation for registering inotify events in the fs
(there is a file operation for dir_notify to register its events). In
create_watch in fs/inotify.c I expected to see something like:
Why not use the existing dir_notify method? No point in adding another.
I did not think
Is dir_notify suitable for inotify and your uses?
The six dir_notify flags obviously map better to the network protocol
which cifs can request (and which Samba server needs to respond to
various network filesystem clients) but the 11 IN_ flags do not seem
that different.
The problem with
On Thu, 2005-07-21 at 17:04, Jesper Juhl wrote:
On 7/21/05, Lasse Kärkkäinen / Tronic [EMAIL PROTECTED] wrote:
I mailed [EMAIL PROTECTED] (the guy who wrote the driver) about this a
month ago, but didn't get any reply. Is anyone working on that driver
anymore?
As far as I know Steve
2. Occassionally the transmission speeds go extremely low for no
apparent reason. While writing this, I am getting 0.39 Mo/s over a
gigabit network.
It would help to know whether you are doing mostly writing to or reading
from the server.
Forgot to mention that another thing that may help
only use
one processor of my SMP system (not ideal).
Maybe you could find time to squash this bug.
Cheers,
Steve Wooding.
-
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
I am seeing odd tcp characteristics on the loopback device.
In analyzing cifs read performance to samba, I see a fairly consistent
pattern.
TCP frame containing SMBRead request (asking for size 16K)
1st 16K of SMB Read Response (1 ms later or less) sent from samba
Samba's response is
On Fri, 2005-07-22 at 14:56, Steve French wrote:
I am seeing odd tcp characteristics on the loopback device.
Although probably not related ... I thought it worth mentioning that
ethereal claims bad tcp checksum on the 2nd of each pair of tcp response
frames (the smaller one) when run
Thanks Karsten,
That fixed it. Though now my bleeding edge InfiniBand driver is
complaining about SPIN_LOCK_UNLOCKED being undeclared. Could this be
caused by the preemt patch, as the IB driver compiles against an
unpatched kernel. I'll look into further.
Cheers,
Steve.
Karsten Wiese
I ran some quick tests with dbench to see the effects of various
performance improvements, and found the results interesting. Although
dbench is too write oriented, and not particularly favorable to a few
filesystems (who are otherwise good performers), dbench can still can be
useful.
System was
Xin Zhao wrote:
I compile kernel 2.6.11.10 and configure both nfs client and server as
kernel modules. But after I reboot the machine and did
/etc/init.d/nfs start, the nfsd module is inserted. But when I tried
to rmmod this module either with /etc/init.d/nfs stop or umount
/proc/fs/nfsd; rmmod
of the app
generating the events, but since we added the /var/chroot key, we can see
that it really came from the chroot dir.
Hope this helps...
-Steve Grubb
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
out the
user space access and that shouldn't be changing.
-Steve
-
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/
without the
other.
-Steve
-
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/
Here is an problem that was brought to my attention and I noticed
it was not fixed in any of the upstream kernels I looked at.
steved.
A trivial patch that allows the setting of NLM timeouts and grace periods
through the proc and sysclt interfaces on x86_64 architectures
Signed-off-by: Steve
,
Steve.
diff -u -r --exclude-from=linux-2.6.12/Documentation/dontdiff
linux-2.6.12/drivers/char/selection.c
linux-2.6.13-rc1-mm1-devel/drivers/char/selection.c
--- linux-2.6.12/drivers/char/selection.c 2005-06-17 13:48:29.0
-0600
+++ linux-2.6.13-rc1-mm1-devel/drivers/char
usually do not want to run a
debug kernel.
I would like to see relayfs merged.
--
Steve Rotolo
[EMAIL PROTECTED]
-
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
OK Steve. I'll give the latest patch a go.
I was using 51-27. Just to make sure I have not missed a step in the
patch process, I am just taking the vanilla 2.6.12 kernel and appling
the preempt patch.
I'll try the 51-27 patch tomorrow.
Cheers,
Steve.
PS Sorry about the config.
Steven
ChangeSet 1.1966.1.22, 2005/01/26 17:30:51-06:00,
snip
+/* The following three structures are needed only for
+ setting time to NT4 and some older servers via
+ the primitive DOS time format */
typedef struct {
- __u16 CreationDate;
- __u16 CreationTime;
- __u16
OK - the first of them is merged in to the cifs bk tree.
The second one looks like an improvement on structuring of the cifs open
logic but needs review. I may have a chance to test it later in the
week.
Thanks.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the
On Mon, 2005-03-14 at 09:36, Jesper Juhl wrote:
Would it be useful if I split the second patch into a few parts for you? I
could split some of the (non cifs_open related) whitespace changes into
one, the kfree related changes into another and then a third with the
cifs_open rework. Would
On Thursday 17 March 2005 12:57, Chris Wright wrote:
Steve, are you working on processing log data, do you have a preference?
Yes, I am working on a utility to process the data. I have 4 comments:
1) Fields that magically appear and dissappear are problematic for fast
parsing.
2) There should
Jesper Juhl wrote:
Here 's a version of my fs/cifs/file.c cleanup patch split into seven
chunks for easier review.
Please use these incremental patches instead of the big one I send you
earlier since I've made a few changes compared to that.
For your convenience the patches are also available
Jesper Juhl wrote:
Hi Steve,
Here's one more cleanup for a file in fs/cifs - readdir.c (i'm going to
follow the order you told me you'd prefer first, then do the remaining
files in arbitrary order).
I'm going to send the patches inline to make it easy for others to comment
if they so choose
for everyone to look over.
-Steve Grubb
-
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/
201 - 300 of 5727 matches
Mail list logo
