Lustre-devel archive on lore.kernel.org
 help / color / mirror / Atom feed
From: di wang <di.wang@sun.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Regarding Server Driven QOS for lustre
Date: Mon, 23 Mar 2009 21:56:29 -0400	[thread overview]
Message-ID: <49C83DCD.803@sun.com> (raw)
In-Reply-To: <89c400ad0903210049o489ba04ax38f9198d57543e9a@mail.gmail.com>

Hello,

The project has turned into NRS (network request scheduler). You can 
check this bug

https://bugzilla.lustre.org/show_bug.cgi?id=13634

Thanks
WangDi

Krishnakumar R wrote:
> Hi Folks,
>
> What is the current status of the LRS and EH implementation on Lustre
> (mentioned in the mail:
> http://groups.google.com/group/lustre-devel-list/msg/c921d5b7121c50eb)
> ?
> Any further documents/links on the server driven QOS on lustre ?
>
> --
> Thanks and Regards,
> KK.
> _______________________________________________
> Lustre-devel mailing list
> Lustre-devel at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-devel
>   

      reply	other threads:[~2009-03-24  1:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-21  7:49 [Lustre-devel] Regarding Server Driven QOS for lustre Krishnakumar R
2009-03-24  1:56 ` di wang [this message]

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=49C83DCD.803@sun.com \
    --to=di.wang@sun.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox