Search

Hrishikesh Keremane

from San Jose, CA
Age ~41
Get Report
Also known as:
Hrishkesh Keremane
Related to:
Adesh Keremane
Connected to:
Demetria Keremes, 81Valentina I Keremidarska, 53Wilson N Keremius, 59Philip D Keren, 65Bita P Kerendian, 51Parviz Kerendian, 88Sarah S Kerendian, 41Melissa A Kerens, 42Shaun P Kerens, 42Alison H Kerensky, 64

Hrishikesh Keremane Phones & Addresses

  • San Jose, CA
  • Sunnyvale, CA

Work

Company: Ibm Mar 2006 to Oct 2008 Position: Systems software engineer

Education

Degree: Master of Business Administration, Masters School / High School: The Wharton School 2018 to 2020

Skills

C • Data Structures • Operating Systems • Device Drivers • Linux Kernel • Debugging • Unix • Systems Programming • Distributed Systems • Kernel • Gnu Debugger • File Systems • Linux • Rtos • Shell Scripting • Agile Methodologies • Java • C++ • Perl • Software Development

Industries

Computer Software

Resumes

Resumes

Hrishikesh Keremane Photo 1

Senior Product Manager

View page
Location:
Sunnyvale, CA
Industry:
Computer Software
Work:
Ibm Mar 2006 - Oct 2008
Systems Software Engineer
Mindtree Sep 2004 - Mar 2006
Programmer Analyst
Netapp Sep 2004 - Mar 2006
Senior Product Manager
Education:
The Wharton School 2018 - 2020
Master of Business Administration, Masters Visvesvaraya Technological University 2000 - 2004
Bachelor of Engineering, Bachelors, Computer Science
Skills:
C
Data Structures
Operating Systems
Device Drivers
Linux Kernel
Debugging
Unix
Systems Programming
Distributed Systems
Kernel
Gnu Debugger
File Systems
Linux
Rtos
Shell Scripting
Agile Methodologies
Java
C++
Perl
Software Development

Publications

Us Patents

Non-Disruptive Controller Replacement In A Cross-Cluster Redundancy Configuration

View page
US Patent:
20170075783, Mar 16, 2017
Filed:
Nov 28, 2016
Appl. No.:
15/361625
Inventors:
- Sunnyvale CA, US
Chaitanya V. Patel - Orange CA, US
Hrishikesh Keremane - Sunnyvale CA, US
Pankti Vinay Majmudar - Sunnyvale CA, US
Santhosh Unnikrishnan - Kerala, IN
Sravan Kumar Elpula - Santa Clara CA, US
Susan M. Coatney - Cupertino CA, US
International Classification:
G06F 11/20
G06F 3/06
Abstract:
During a storage redundancy giveback from a first node to a second node following a storage redundancy takeover from the second node by the first node, the second node is initialized in part by receiving a node identification indicator from the second node. The node identification indicator is included in a node advertisement message sent by the second node during a giveback wait phase of the storage redundancy giveback. The node identification indicator includes an intra-cluster node connectivity identifier that is used by the first node to determine whether the second node is an intra-cluster takeover partner. In response to determining that the second node is an intra-cluster takeover partner, the first node completes the giveback of storage resources to the second node.

Interconnect Path Failover

View page
US Patent:
20160266989, Sep 15, 2016
Filed:
May 26, 2016
Appl. No.:
15/164971
Inventors:
- Sunnyvale CA, US
Rishabh Mittal - New Delhi, IN
Amarnath Jolad - Bangalore, IN
Hrishikesh Keremane - Sunnyvale CA, US
Harihara Kadayam - Fremont CA, US
International Classification:
G06F 11/20
G06F 11/22
G06F 12/02
G06F 11/30
Abstract:
One or more techniques and/or systems are provided for interconnect failover between a primary storage controller and a secondary storage controller. The secondary storage controller may be configured as a backup or failover storage controller for the primary storage controller in the event the primary storage controller fails. Data and/or metadata describing the data (e.g., data and/or metadata stored within a write cache) may be mirrored from the primary storage controller to the secondary storage controller over one or more interconnect paths. Responsive to identifying a failover trigger for a failed interconnect path, the secondary storage controller is instructed to fence (e.g., block) I/O operations from the failed interconnect path. Streams of data and/or metadata that were affected by the failure may be instructed to transmit such data and/or metadata over one or more non-failed interconnect paths to the secondary storage controller during failover of the failed interconnect path.

Non-Disruptive Controller Replacement In A Cross-Cluster Redundancy Configuration

View page
US Patent:
20160140003, May 19, 2016
Filed:
Nov 13, 2014
Appl. No.:
14/541119
Inventors:
- Sunnyvale CA, US
Chaitanya V. Patel - Orange CA, US
Hrishikesh Keremane - Sunnyvale CA, US
Pankti Vinay Majmudar - Sunnyvale CA, US
Santhosh Unnikrishnan - Kerala, IN
Sravan Kumar Elpula - Santa Clara CA, US
Susan M. Coatney - Cupertino CA, US
International Classification:
G06F 11/20
Abstract:
During a storage redundancy giveback from a first node to a second node following a storage redundancy takeover from the second node by the first node, the second node is initialized in part by receiving a node identification indicator from the second node. The node identification indicator is included in a node advertisement message sent by the second node during a giveback wait phase of the storage redundancy giveback. The node identification indicator includes an intra-cluster node connectivity identifier that is used by the first node to determine whether the second node is an intra-cluster takeover partner. In response to determining that the second node is an intra-cluster takeover partner, the first node completes the giveback of storage resources to the second node.

Interconnect Path Failover

View page
US Patent:
20150309892, Oct 29, 2015
Filed:
Apr 25, 2014
Appl. No.:
14/261556
Inventors:
- Sunnyvale CA, US
Rishabh Mittal - New Delhi, IN
Amarnath Jolad - Bangalore, IN
Hrishikesh Keremane - Sunnyvale CA, US
Harihara Kadayam - Fremont CA, US
Assignee:
NetApp Inc. - Sunnyvale CA
International Classification:
G06F 11/20
Abstract:
One or more techniques and/or systems are provided for interconnect failover between a primary storage controller and a secondary storage controller. The secondary storage controller may be configured as a backup or failover storage controller for the primary storage controller in the event the primary storage controller fails. Data and/or metadata describing the data (e.g., data and/or metadata stored within a write cache) may be mirrored from the primary storage controller to the secondary storage controller over one or more interconnect paths. Responsive to identifying a failover trigger for a failed interconnect path, the secondary storage controller is instructed to fence (e.g., block) I/O operations from the failed interconnect path. Streams of data and/or metadata that were affected by the failure may be instructed to transmit such data and/or metadata over one or more non-failed interconnect paths to the secondary storage controller during failover of the failed interconnect path.
Control profile
Hrishikesh Keremane from San Jose, CA, age ~41 Get Report