All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Benny Halevy <bhalevy@panasas.com>,
	Trond Myklebust <Trond.Myklebust@netapp.com>,
	NFS list <linux-nfs@vger.kernel.org>
Subject: [PATCHS 0/3] Some more bugs in latest code + please help with last problem
Date: Tue, 24 May 2011 13:52:01 +0300	[thread overview]
Message-ID: <4DDB8DD1.20101@panasas.com> (raw)


I'm sending some more fixes.

After launch I will re-send all the fixes needed ontop of Benny's
last tree as SQUASHMEs. One SQUASHME for each patch in the set that
needs one. 

Last sent fixes will have conflicts with newest code. So these re-sent
will resolve that.

With this code, I'm able to use the global-device-cache the way It
was with the old one. Also including all the fixes I'm able to do
IO, and checkout a git tree!

*BUT*: Currently IO is very very slow, because wsize/rsize is set
       to default 64k which is just one strip_unit for default
       objects. I used to set server->w/rsize on .set_layoutdriver
       but Benny removed that. What do you guys want to do with this?
       I can see to options:
       1. Return the .set_layoutdriver where ld can set defaults
          the way it likes it.
       2. If pnfs is used set w/rsize to MAX_UINT and let pg_test
          cap the sizes as see fit.

       Please advise?

For now these:
	SQUSHME: pnfs: BUG in _deviceid_purge_client
	pnfs: layout_driver MUST set free_deviceid_node if using dev-cache
	SQUASHME: pnfs-obj: objlayout wants to cache devices until unmount

Thanks
Boaz


             reply	other threads:[~2011-05-24 10:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-24 10:52 Boaz Harrosh [this message]
2011-05-24 10:53 ` [PATCH 1/3] SQUSHME: pnfs: BUG in _deviceid_purge_client Boaz Harrosh
2011-05-24 10:54 ` [PATCH] pnfs: layout_driver MUST set .free_deviceid_node if using dev-cache Boaz Harrosh
2011-05-24 10:56 ` [PATCH 3/3] SQUASHME: pnfs-obj: objlayout wants to cache devices until unmount Boaz Harrosh

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=4DDB8DD1.20101@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=bhalevy@panasas.com \
    --cc=linux-nfs@vger.kernel.org \
    /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.