All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] GFS: update gfs-kernel HEAD to 2.6.20 (please review)
Date: Thu, 01 Feb 2007 11:31:00 -0600	[thread overview]
Message-ID: <45C223D4.6060304@redhat.com> (raw)

Hi Cluster Developers,

Attached is a patch for HEAD that allows it to compile and run on an
upstream kernel.  Currently, I'm using Linus' 2.6.20-rc7 kernel from git.
The biggest changes are to (1) ops_file.c regarding upstream changes to 
vfs's
aio operations, and (2) glock.c regarding upstream changes to how
workqueues work.  It also contains a couple little cleanups. 
Please review and send me comments.

Special note about the aio changes to ops_file.c:  Wendy Cheng added
some code for AIO a while back, and this patch deviates from that code
a little bit.  Namely, there was a place in function do_read_buf where the
aio path was waiting for async io to complete, and I took that out.  Let 
me know
if you think this needs to go back in.

I'd also like to hear your opinions on if/when we should make HEAD deviate
from RHEL5 and start tracking the upstream kernel rather than the RHEL5
kernel.

Regards,

Bob Peterson
Red Hat Cluster Suite

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: gronk
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20070201/d765e726/attachment.ksh>

             reply	other threads:[~2007-02-01 17:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-01 17:31 Robert Peterson [this message]
2007-02-01 17:44 ` [Cluster-devel] [PATCH] GFS: update gfs-kernel HEAD to 2.6.20 (please review) David Teigland

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45C223D4.6060304@redhat.com \
    --to=rpeterso@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.