[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <515b4651c5aa3f5bc550b26fe708f65d@coraid.com>
Date: Wed, 2 Sep 2009 09:31:49 -0400
From: Ed Cashin <ecashin@...aid.com>
To: bonbons@...ux-vserver.org, ecashin@...aid.com, apw@...onical.com,
akpm@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/1] aoe: ensure we initialise the request_queue correctly
On Tue Sep 1 16:31:58 EDT 2009, bonbons@...ux-vserver.org wrote:
> On Tue, 01 September 2009 Ed Cashin <ecashin@...aid.com> wrote:
...
> > Thanks much for doing that. It makes sense that this change would
> > have caused it to suddenly matter whether the unused queue is
> > initialized.
> >
> > The patch looks fine to me.
>
> Would it make sense to fine-tune the values reported by sys-fs in the
> queue details so they match with the AoE device (as a separate
> enhancement patch)?
>
> Sure the queue itself won't use them, but some user-space tools might
> be interested in this data.
>
> I've not checked what information is provided by AoE protocol or can
> be deducted from interface MTU.
The AoE protocol does allow a storage target to say, "I can handle
this certain number of sectors in a single read or write command." But
the user space tools cannot really benefit from that information,
since they can send larger read/write operations with no loss of
efficiency.
So I suspect that it would not make much sense, but if you decide to
look into it further, see whether you can identify an extant user
space tool that benefits from the information.
--
Ed Cashin
http://noserose.net/e/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists