US 9,866,636 B2Granted

Server access processing system

AssigneeInternational Business Machines Corporation

InventorsAdekunle Bello, Radhika Chirra, Nikhil Hegde, Aruna Yedavilli

Life of this patent

Estimating the term…

Loading patent…

Abstract

A method, programmed medium and system are provided for preventing the denial of file system access to a plurality of clients accessing a NFS server. In one example, an NFS server is configured to listen on a server port. The server runs a separate daemon which “watches” client requests as they are received at the NFS server. The server processing system tracks the number of times a client sends consecutive TCP zero-window packets in response to a data packet from the server. If the number of zero-window packets crosses a user-defined threshold, then a routine is called to stop responding to that client using a backoff algorithm. When the server reaches a point where the number of available threads or any other relevant resource dips below a user-defined threshold, the server process starts terminating connections to the clients starting from the ones with the oldest entry in the table.

Claims17

Dependent claims

A computer program product for enabling server access processing in a Network File System (NFS) interconnection network including a server operable for transmitting data packets to a plurality of client devices connected to said server in response to data requests from said plurality of client devices to said server, the computer program product comprising a non-transitory computer readable medium comprising computer readable program code configured such that when such program code is read by said server, the server is operable for:

receiving data requests by said server from said client devices;
said server being operable in response to said computer readable program code for running a daemon program in the background, said daemon program being operable for monitoring said data requests from said client devices to said server on a designated port on a non-interfering basis with transactions between said client devices and said server, said daemon program being operable for determining when a data packet is sent from said server to a client device in response to a data request from said client device;
said client device being operable for sending zero window packets (ZWPs) from said client device to said server after receiving said data packet, said ZWPs being indicative that said client device is not ready to receive further data packets from said server;
said server being operable in response to said computer readable program code for receiving said ZWPs sent from said client device, said server daemon program being operable for counting a number of ZWPs received from said client device, said server daemon program being further operable to provide a ZWP count representative of said number of ZWPs received from said client device;
and
said daemon program being operable for using said ZWP count to control access to said server by said client device.

3 more elements

In a Network File System (NFS), a server having a processor enabled to manage server access requests from a client device, said processor being operable for transmitting data packets to said client device in response to data requests from said client device to said server, said server comprising:

means for receiving data requests by said server from said client device;
said server being operable for running a daemon program in the background, said daemon program being operable for monitoring said data requests from said client device to said server on a designated port on a non-interfering basis with transactions between said client device and said server, said daemon program being operable for determining when a data packet is sent from said server to said client device in response to a data request from said client device;
said client device being operable for sending zero window packets (ZWPs) from said client device to said server after receiving said data packet, said ZWPs being indicative that said client device is not ready to receive further data packets from said server;
said server being operable for receiving said ZWPs sent from said client device, said server daemon program being operable for counting a number of ZWPs received from said client device, said server daemon program being further operable to provide a ZWP count representative of said number of ZWPs received from said client device;
and
said daemon program being operable for using said ZWP count to control access to said server by said client device.

3 more elements

A Network File System (NFS) including a server and at least one client device accessing said server, said server being operable for transmitting data packets to said client device in response to data requests from said client device to said server, said server being enabled for managing access to said server by said client device, said server including:

means for receiving data requests by said server from said client device;
said server being operable for running a daemon program in the background, said daemon program being operable for monitoring said data requests from said client device to said server on a designated port on a non-interfering basis with transactions between said client device and said server, said daemon program being operable for determining when a data packet is sent from said server to said client device in response to a data request from said client device;
said client device being operable for sending zero window packets (ZWPs) from said client device to said server after receiving said data packet, said ZWPs being indicative that said client device is not ready to receive further data packets from said server;
said server being operable for receiving said ZWPs sent from said client device, said server daemon program being operable for counting a number of ZWPs received from said client device, said server daemon program being further operable to provide a ZWP count representative of said number of ZWPs received from said client device, said ZWP count including a total count of consecutive ZWPs received by said server;
means for disabling said server from responding to said client device for a first time period after said total count exceeds a first predetermined number;
means for enabling said server to respond to said client device after said first time period if no ZWPs are received by said server from said client device during said first time period;
means for determining a resource availability level of said server when said total count exceeds said first predetermined number;
means for disabling said server from responding to said client device for a second time period after said total count exceeds a second predetermined number at a completion of said first time period, said second time period being greater than said first time period;
means for enabling said server to respond to said client device after said second time period if no ZWPs are received by said server from said client device during said second time period;
and
means for disconnecting said client device from said server when said resource availability level is below a predetermined level and said total count exceeds said second predetermined number after said second time period.

8 more elements

Dependencies are inferred from the claim text.

Facts

Application: 15/331,330Filed 21 Oct 2016 · continuation
Priority: 9 Nov 2009
Published: US 2017/0054804 A123 Feb 2017
Granted: 9 Jan 2018
Term ends: Not estimatedThe source records don’t support an estimate.

Classification10 codes

H04L 67/1097
In which an application is distributed across nodes in the network: for distributed storage of data in networks, e.g. transport arrangements for…
H04L 43/16
Arrangements for monitoring or testing data switching networks: threshold monitoring
H04L 47/193
At layers above the network layer: at the transport layer, e.g. TCP related
H04L 47/27
Flow control; Congestion control: evaluation or update of window size, e.g. using information derived from acknowledged [ACK] packets

Family

Application12/614,511Parent of this continuation · filed 9 Nov 2009
Application13/459,160Parent of this continuation · filed 28 Apr 2012
US 2017/0054804 A1Pre-grant publication · published 23 Feb 2017
US 9,516,142 B2Parent of this continuation
US 2011/0113134 A1Published application
US 2012/0215916 A1Published application
US 9,866,636 B2This patent

From the US filing history. Foreign family members aren’t listed.