RE: [PATCH V3] SA Busy Handling

Mike Heinz
2010-12-03T21:50:08Z

The reason for preferring a BUSY response to simply having the SM throw the packets on the floor is that it makes it possible to differentiate between an overloaded SM and communications problems when debugging a fabric problem.

-----Original Message-----
From: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org [mailto:linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org] On Behalf Of Roland Dreier
Sent: Friday, December 03, 2010 4:44 PM
To: Mike Heinz
Cc: Hefty, Sean; Hal Rosenstock; linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH V3] SA Busy Handling

> If we don't want to use this, then we should just go all the way back
> to the original patch I submitted in the spring. That version does
> not have the user space hook or the module parameter.

I definitely feel we should not have the module parameter. The new
behavior is supposed to always be better, right? So why would anyone
ever want to mess with the module parameter?

However I think I would like to have at least some idea of what the
smarter way to handle "busy" responses will be. If we're always just
going to treat them like timeouts, then it seems the SA would be smarter
to avoid sending them in the first place.

- R.