All of lore.kernel.org
 help / color / mirror / Atom feed
From: Todd, Allen <Allen.Todd@sig.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] [wc-discuss] Re: [Twg] Lustre and cross-platform portability
Date: Fri, 16 Mar 2012 15:06:04 +0000	[thread overview]
Message-ID: <097F86FD722A2445B248BC51CC5DB88D1702BC@xchmbbal504.ds.susq.com> (raw)
In-Reply-To: <4F6311CB.8040506@diamond.ac.uk>


On Friday, March 16, 2012 6:11 AM, Gregory Matthews wrote:
> why bother having a windows client if you lose the performance? We have
> windows based detectors and proprietary windows based analysis software
> that would definitely benefit from higher performance access to lustre
> file systems but replacing existing CIFS servers for no gain seems a bit
> pointless.

From the perspective of my firm, the benefit of a windows lustre client (native or fuse-based), even one that performs at 10% or 20% of the linux client, is the improved scalability that it offers.  Our current solution uses 4 samba gateways per hundred windows servers to achieve acceptable bandwidth, but that bandwidth can be cut to an unacceptable trickle if a large wave of native linux clients simultaneously accesses the filesystem.

We have repeatedly asked our Microsoft HPC contacts to intervene to either fund a native windows client or to get oracle to release the existing one, since scalable storage is a big hole in the Microsoft HPC toolkit.  Obviously, nothing has come out of that.  It seems Microsoft is banking on pNFS, eventually working in this space.

Allen Todd




________________________________

IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.

  parent reply	other threads:[~2012-03-16 15:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15  0:31 [Lustre-devel] Lustre and cross-platform portability Andreas Dilger
2012-03-15 18:45 ` [Lustre-devel] [Twg] " Ken Hornstein
2012-03-15 19:39   ` Andreas Dilger
2012-03-15 19:51     ` Joshua Walgenbach
2012-03-16 10:11       ` [Lustre-devel] [wc-discuss] " Gregory Matthews
2012-03-16 10:35         ` Alexey Lyashkov
2012-03-16 14:46           ` Ken Hornstein
2012-03-17 10:42             ` [Lustre-devel] [wc-discuss] " Alexey Lyashkov
2012-03-16 15:06         ` Todd, Allen [this message]
2012-03-21 18:29           ` [Lustre-devel] [wc-discuss] " Nathan Rutman
2012-03-16 14:38     ` [Lustre-devel] " Ken Hornstein
2012-03-16 16:03 ` [Lustre-devel] [EXTERNAL] " Ward, Lee
     [not found] ` <5A40CBC5-F91A-4F34-8209-0C216CCE8A5D@dilger.ca>
2012-04-27  2:23   ` [Lustre-devel] [wc-discuss] " tao.peng at emc.com
2012-04-27  3:54     ` Andreas Dilger
2012-04-27 10:15       ` tao.peng at emc.com
2012-04-27 10:25         ` [Lustre-devel] [Lustre-discuss] " Roman Grigoryev
2012-04-27 12:33           ` tao.peng at emc.com
2012-05-03  9:45             ` Roman Grigoryev
2012-05-03 10:03               ` tao.peng at emc.com
2012-05-03 10:45                 ` Roman Grigoryev
2012-05-03 15:08                   ` tao.peng at emc.com
2012-04-27 20:23         ` [Lustre-devel] " Andreas Dilger
2012-04-29  4:33           ` Peng Tao
2012-04-28  8:59   ` Liang Zhen

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=097F86FD722A2445B248BC51CC5DB88D1702BC@xchmbbal504.ds.susq.com \
    --to=allen.todd@sig.com \
    --cc=lustre-devel@lists.lustre.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.