On Fri, Jan 29, 2010 at 8:59 PM, Mike Christie micha...@cs.wisc.edu wrote:
On 01/28/2010 09:25 AM, Erez Zilber wrote:
+struct iscsi_noop_info {
+ struct timeval tv;
Can you pass this between userspace and the kernel safely? The fields in
there are longs, and I thought those could be
On Sun, Dec 20, 2009 at 3:57 PM, Erez Zilber erezzi.l...@gmail.com wrote:
On Thu, Dec 17, 2009 at 5:01 AM, Mike Christie micha...@cs.wisc.edu wrote:
Erez Zilber wrote:
On Tue, Dec 15, 2009 at 10:34 AM, Mike Christie micha...@cs.wisc.edu
wrote:
Erez Zilber wrote:
Maintain a list of nop-out
Erez Zilber wrote:
On Tue, Dec 15, 2009 at 10:34 AM, Mike Christie micha...@cs.wisc.edu wrote:
Erez Zilber wrote:
Maintain a list of nop-out PDUs that almost timed out.
With this information, you can understand and debug the
whole system: you can check your target and see what caused
it to
Erez Zilber wrote:
Maintain a list of nop-out PDUs that almost timed out.
With this information, you can understand and debug the
whole system: you can check your target and see what caused
it to be so slow on that specific time, you can see if your
network was very busy during that time etc.
On Tue, Dec 15, 2009 at 10:34 AM, Mike Christie micha...@cs.wisc.edu wrote:
Erez Zilber wrote:
Maintain a list of nop-out PDUs that almost timed out.
With this information, you can understand and debug the
whole system: you can check your target and see what caused
it to be so slow on that
On 7 Dec 2009 at 11:20, Mike Christie wrote:
Ulrich Windl wrote:
On 1 Dec 2009 at 14:57, Erez Zilber wrote:
Maintain a list of nop-out PDUs that almost timed out.
With this information, you can understand and debug the
whole system: you can check your target and see what caused
it
Erez Zilber wrote:
Maintain a list of nop-out PDUs that almost timed out.
With this information, you can understand and debug the
whole system: you can check your target and see what caused
it to be so slow on that specific time, you can see if your
network was very busy during that time
Ulrich Windl wrote:
On 1 Dec 2009 at 14:57, Erez Zilber wrote:
Maintain a list of nop-out PDUs that almost timed out.
With this information, you can understand and debug the
whole system: you can check your target and see what caused
it to be so slow on that specific time, you can see if
On Tue, Dec 1, 2009 at 2:57 PM, Erez Zilber erezzi.l...@gmail.com wrote:
On Sun, Nov 22, 2009 at 11:24 PM, Erez Zilber erezzi.l...@gmail.com wrote:
On Sun, Nov 22, 2009 at 10:44 PM, Mike Christie micha...@cs.wisc.edu wrote:
Erez Zilber wrote:
On Thu, Nov 19, 2009 at 10:02 PM, Mike Christie
On 1 Dec 2009 at 14:57, Erez Zilber wrote:
Maintain a list of nop-out PDUs that almost timed out.
With this information, you can understand and debug the
whole system: you can check your target and see what caused
it to be so slow on that specific time, you can see if your
network was very
On Tue, Dec 1, 2009 at 3:16 PM, Ulrich Windl
ulrich.wi...@rz.uni-regensburg.de wrote:
On 1 Dec 2009 at 14:57, Erez Zilber wrote:
Maintain a list of nop-out PDUs that almost timed out.
With this information, you can understand and debug the
whole system: you can check your target and see what
11 matches
Mail list logo
